A11y audit
Audit accessibility compliance in frontend code. Use when user asks to "check accessibility", "/a11y-audit", "audit a11y", "check WCAG", or wants to find accessibility issues. Don't use for backend code, non-UI files, or projects without HTML/JSX output.From its SKILL.md
npx -y skills add helderberto/agent-skills --skill a11y-auditAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 1 command, including `npx @axe-core/cli@4 http://localhost:3000`.
- fetches URLsInstructs the agent to fetch 1 URL, including http://localhost:3000.
SKILL.md
1.1 KB, 193 tokens by cl100k_base, as published. Nobody here has run it
Accessibility Audit
Workflow
- Detect framework from
package.json(React, Vue, Svelte) - Run static analysis -- grep JSX/TSX/HTML files for violations
- If dev server is running, optionally run axe-core CLI:
npx @axe-core/cli@4 http://localhost:3000 - Report findings grouped by severity
Output format
Group by WCAG criterion:
- Critical (A) -- blocks assistive technology users
- Serious (AA) -- significantly impacts usability
- Suggestions -- best practice improvements
Use file:line references. Include the fix for each finding. Prioritize keyboard navigation and screen reader issues; never auto-fix -- show what to change and why.
Error Handling
- Framework undetected -- scan all
.html,.jsx,.tsx,.vuefiles
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most audit compliance skills give in 193 tokens
Counted across 960 of the 1,589 authors here whose files we hold, read 2026-09-06
- Read product marketing context before asking questionsin 29 of 960, across 11 files
- Rank findings by severityin 29 of 960, across 22 files
- Generate audit reportin 22 of 960
- Run the audit scriptin 20 of 960, across 19 files
- Generate a prioritized action plan reportin 19 of 960, across 11 files
- Ensure one H1 per pagein 15 of 960, across 5 files
- Ensure sitemap exists and is accessiblein 14 of 960, across 4 files
- Verify alt text on all imagesin 12 of 960, across 3 files
- Determine the audit scope before startingin 12 of 960, across 4 files
- Verify important pages allowed in robots.txtin 11 of 960, across 2 files
- Detect business type from homepage signalsin 11 of 960, across 7 files
- Delegate specialized tasks to subagentsin 11 of 960, across 7 files
Said here and by no other author read
- Detect framework from package.json
- Run static analysis for violations
- Use file line references
- Prioritize keyboard navigation and screen reader issues
- Scan all UI files if framework undetected
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.