Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 4 REVIEW 3 FIX

Mobile Keyboard & Autofill

Action

3/3 eligible field(s) missing autocomplete or inputmode

FIX

3/3 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email" name="email">

2 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: search, email.

Got: <input type="search" name="q">, <input type="email" name="email">

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Form Accessibility

3 of 3 controls have issues

REVIEW

3 of 3 controls have issues

3 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="search" name="q">; <input type="text" name="q">; <input type="email" name="email">

3 controls

0 labeled

3 placeholder only

0 unlabeled

Control	Type	Label	Method
q	search	(Search skills...)	placeholder only
q	text	(Search for skills (e.g. 'search', 'python', 'pdf'))	placeholder only
email	email	(Email...)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Mobile-Readable Font Sizes

95% of visible text renders at >= 12 CSS px (15 below threshold)

REVIEW

95% of visible text renders at >= 12 CSS px (15 below threshold)

15 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <p> 11.0px ("What it is"); <p> 11.0px ("When to use it"); <p> 11.0px ("What it is"); <p> 11.0px ("When to use it"); <p> 11.0px ("What it is").

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color #111827 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

A+

Heading Hierarchy

74 headings

PASS

74 headings

Single H1 present

H1 AI Agent Skills Directory
H2 ✨ Editor's Choice
H3 cloud
H3 apple-hig
H3 image-generation
H3 vitest
H3 fsharp-testing
H3 fix
H2 🆕 New Arrivals
H3 composio
H3 gdpr-compliant
H3 grok-delegate
H3 gsap-frameworks
H3 gsap-performance
H3 gsap-plugins
H3 emilkowalski-motion
H3 gsap-utils
H3 tao-train-nvpanoptix3d
H2 What is an AI Agent Skill?
H3 Skills vs nearby concepts
H4 AI Agent Skill
H4 MCP server
H4 Slash command
H2 🔥 Trending This Week
H3 git-guardrails-claude-code
H3 ponytail
H3 orca-per-workspace-env
H3 diagram-design
H3 dogfood
H3 writing-skills
H3 managed-pentesting-with-strix
H3 karpathy-guidelines
H3 karpathy-guidelines
H2 Browse by Category
H3 Agent Workflows
H3 Prompting & Reasoning
H3 Research & Knowledge
H3 Browser & Web
H3 Writing & Content
H3 Design & UI
H3 Marketing & SEO
H3 Productivity
H3 Code Generation
H3 Frontend
H3 Backend & API
H3 Database
H2 Power your workflows
H3 Content Creation
H3 Automation
H3 Data Analysis
H2 Built with open-source maintainers
H2 How to install a skill
H3 Find a skill
H3 Copy command
H3 Paste & run
H2 Built by the Community
H2 Frequently Asked Questions
H3 What is the difference between Skills and MCP?
H3 Are these skills safe to use?
H3 How are skills added to the directory?
H3 Is this service free?
H3 What is a Claude skills marketplace?
H3 How do I find Claude code templates?
H3 Can I use multiple skills together?
H3 Where can I inspect a skill's source code?
H3 How do skills differ from slash commands?
H3 How often are skills updated?
H3 What is marketplace.json?
H3 Is this website affiliated with Anthropic or OpenAI?
H3 Discover
H3 Company
H3 Friend Links
H3 Get Updates
H2 Directories

A+

Heading Text Quality

All 74 heading(s) have substantive, well-formed text

PASS

All 74 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 58 images OK

PASS

All 58 images OK

9 decorative image(s) correctly marked

49 image(s) with good alt text

58 images 49 good alt text 9 decorative

All images have appropriate alt text.

Link & Button Quality

108 links, 3 buttons — all OK

PASS

108 links, 3 buttons — all OK

22 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://code.claude.com/docs/en/skills; https://github.com/affaan-m; https://github.com/github; https://github.com/nvidia; https://github.com/nexu-io; https://github.com/forcedotcom; https://github.com/nomadamas; https://github.com/bbwdadfg/ai-agent-skills-index; https://github.com/bbwdadfg/ai-agent-skills-index; https://github.com/bbwdadfg/ai-agent-skills-index (+12 more)

86 link(s) with descriptive text

108 links

0 empty

0 generic text

22 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://code.claude.com/docs/en/skills	Anthropic — Extend Claude wi…	new tab	Add '(opens in new tab)' to text
https://github.com/affaan-m	AFaffaan-m480 released skills	new tab	Add '(opens in new tab)' to text
https://github.com/github	GIgithub241 released skills	new tab	Add '(opens in new tab)' to text
https://github.com/nvidia	NVnvidia171 released skills	new tab	Add '(opens in new tab)' to text
https://github.com/nexu-io	NEnexu-io138 released skills	new tab	Add '(opens in new tab)' to text
https://github.com/forcedotcom	FOforcedotcom123 released skil…	new tab	Add '(opens in new tab)' to text
https://github.com/nomadamas	NOnomadamas98 released skills	new tab	Add '(opens in new tab)' to text
https://github.com/bbwdadfg/ai-agent-ski…	Public skill index on GitHub �…	new tab	Add '(opens in new tab)' to text
https://github.com/bbwdadfg/ai-agent-ski…	View Skill Index	new tab	Add '(opens in new tab)' to text
https://github.com/bbwdadfg/ai-agent-ski…	GitHub	new tab	Add '(opens in new tab)' to text
https://seedaud.io/	Seed Audio AI	new tab	Add '(opens in new tab)' to text
https://productshotai.app/	Product Shot AI	new tab	Add '(opens in new tab)' to text
https://m3u8-player.net/	M3U8 Player	new tab	Add '(opens in new tab)' to text
https://www.freeai.run/product/ai-agent-…	Featured on FreeAI	new tab	Add '(opens in new tab)' to text
https://tooldirs.com/product/ai-agent-sk…	Featured on ToolDirs	new tab	Add '(opens in new tab)' to text
https://www.toolpilot.ai	Featured on ToolPilot	new tab	Add '(opens in new tab)' to text
https://www.startupfa.st/projects/ai-age…	Powered by Startup Fast	new tab	Add '(opens in new tab)' to text
https://deeplaunch.io/product/ai-agent-s…	Featured on DeepLaunch.io	new tab	Add '(opens in new tab)' to text
https://firstlook.tools/product/ai-agent…	Featured on First Look	new tab	Add '(opens in new tab)' to text
https://turbo0.com/item/ai-agent-skills	Listed on Turbo0	new tab	Add '(opens in new tab)' to text
https://toolrain.com/item/ai-agent-skill…	Listed on ToolRain	new tab	Add '(opens in new tab)' to text
https://navfolders.com/item/ai-agent-ski…	NavFolders	new tab	Add '(opens in new tab)' to text

89 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://code.claude.com/docs/en/skills; https://github.com/affaan-m; https://github.com/github; https://github.com/nvidia; https://github.com/nexu-io; https://github.com/forcedotcom; https://github.com/nomadamas; https://github.com/bbwdadfg/ai-agent-skills-index; https://github.com/bbwdadfg/ai-agent-skills-index; https://github.com/bbwdadfg/ai-agent-skills-index (+12 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "q" should use type="search" (currently type="text")

Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

3 form control(s) checked, no input-semantic issues

PASS

3 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

Favicon & Branding

5 icon(s) detected

PASS

5 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: AI Agent Skills

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name AI Agent Skills ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name AI Agent Skills Display Mode standalone Theme Color #111827 Background Color #ffffff Icons 2 icon(s)

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 AI Agent	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h2 ✨ Editor's Choice	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h2 🆕 New Arrivals	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h2 What is an AI Agent …	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h2 🔥 Trending This W…	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h2 Browse by Category	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h2 Power your workflows	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h2 Built with open-sour…	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h2 How to install a ski…	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h2 Built by the Communi…	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h2 Frequently Asked Que…	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h2 Directories	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h3 cloud	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h3 apple-hig	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h3 image-generation	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h3 vitest	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h3 fsharp-testing	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h3 fix	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h3 composio	5.09:1	3.0:1	#000000	#7C7D7E	Pass
h3 gdpr-compliant	5.09:1	3.0:1	#000000	#7C7D7E	Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 21 passed

PASS

100

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○Links have a discernible name

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.