accessibility-audit · owl-listener — Claude Code skill: WCAG audits
Audits an existing interface against WCAG and reports issues with severity, impact, and remediation steps.
npx skills add Owl-Listener/designer-skills --skill accessibility-audit -a claude-codeWhat accessibility-audit does
This skill audits an existing design or implementation against WCAG 2.2. It looks for barriers related to perception, keyboard access, predictable behaviour, semantic markup, and ARIA.
Each finding includes a description, interface location, WCAG criterion, severity, impact, remediation steps, and code examples. Issues use the Critical, Major, Minor, and Enhancement ratings.
Check static and interactive states across devices and browsers, then test with assistive technologies. This skill is the wrong choice for planning future sessions with disabled users; use accessibility-test-plan instead.
What it helps with
- find access barriers in an existing interface
- rate the severity of WCAG issues
- link an issue to its WCAG criterion
- prepare remediation steps with code examples
- review interface states for assistive technology
Example prompts for the agent
- Run accessibility-audit on the current interface and list WCAG issues.
- Use accessibility-audit on this form, including severity and remediation steps.
- Audit the page's interactive states with accessibility-audit.
How to install accessibility-audit
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill accessibility-audit -a claude-code2Manually: put the files in place
~/.claude/skills/accessibility-audit/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/accessibility-audit/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill accessibility-audit -a codex2Manually: put the files in place
.agents/skills/accessibility-audit/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill accessibility-audit -a cursor2Manually: put the files in place
.cursor/skills/accessibility-audit/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Owl-Listener/designer-skills accessibility-audit2Manually: put the files in place
.github/skills/accessibility-audit/SKILL.md1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill accessibility-audit -a gemini-cli2Platform CLI
gemini skills install https://github.com/Owl-Listener/designer-skills --path design-systems/skills/accessibility-auditManually: put the files in place
.devin/skills/accessibility-audit/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill accessibility-audit -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about accessibility-audit
How do I install accessibility-audit in Claude Code?
Run npx skills add Owl-Listener/designer-skills --skill accessibility-audit -a claude-code, then run npx skills add Owl-Listener/designer-skills --skill accessibility-audit -a claude-code again. The skill file is at ~/.claude/skills/accessibility-audit/SKILL.md.
What does accessibility-audit do?
It audits an existing interface against WCAG 2.2. The report includes issue details, impact, severity, remediation steps, and code examples.
Is accessibility-audit for planning assistive-technology research sessions?
No. Use accessibility-test-plan when planning future sessions with disabled users.
Source text
SKILL.md · MIT
--- name: accessibility-audit description: Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing). --- # Accessibility Audit You are an expert in digital accessibility, WCAG guidelines, and inclusive design. ## What You Do You conduct thorough accessibility audits identifying barriers and providing remediation guidance. ## WCAG 2.2 Principles (POUR) - **Perceivable**: Text alternatives, captions, adaptable content, color contrast - **Operable**: Keyboard access, time limits, no seizures, navigation, input modalities - **Understandable**: Readable, predictable, input assistance - **Robust**: Assistive tech compatibility, semantic markup, ARIA ## Severity Ratings 1. Critical — blocks access entirely 2. Major — significant difficulty 3. Minor — inconvenience with workarounds 4. Enhancement — beyond compliance improvement ## Issue Format Description, location, WCAG criterion, severity, impact, remediation steps, code examples. ## Best Practices - Test with real assistive technologies - Include users with disabilities when possible - Audit across devices and browsers - Check static and interactive states - Prioritize by severity and user impact
© Owl-Listener · MIT · Owl-Listener/designer-skills
Similar skills
Everything for Frontend and UI →accessibility-audit by other authors comes first.