Skip to content
alyn
Owl-Listener

Accessibility Audit skill

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).

$npx skills add Owl-Listener/designer-skills --skill accessibility-audit
View this skill on GitHubOwl-Listener/designer-skills/design-systems/skills/accessibility-audit/SKILL.md
Pack stars
3,314
Pack installs
237k
Alyn Score
60/99
Updated
2 months ago
License
MIT
– views – installs via Alyn

Owl-Listener

Accessibility Audit

Install Accessibility Audit

Pick your agent. Every command is ready to paste.

$npx skills add Owl-Listener/designer-skills --skill accessibility-audit

The open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.

01

Install it

Run the command above, or upload the folder in Claude.

02

Ask naturally

Describe the task. Your agent loads accessibility-audit when the request matches its description.

03

Name it if needed

If it does not trigger, say “use the accessibility-audit skill”. In Codex, type $accessibility-audit.

The skill itself

SKILL.md

FolderGitHub

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

Tips for Accessibility Audit

  • • Start a fresh session after installing so your agent picks up the new skill.
  • • It is part of a pack with 30 skills. Install only the ones you need with --skill to keep triggers precise.
  • • If two skills overlap, mention the one you want by name.

Questions about Accessibility Audit

What does the Accessibility Audit skill do?

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).

How do I install Accessibility Audit?

Run "npx skills add Owl-Listener/designer-skills --skill accessibility-audit" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.

Does Accessibility Audit work in Cursor and Codex?

Yes. Accessibility Audit uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.

Is Accessibility Audit free?

Accessibility Audit is open source on GitHub under the MIT license. It is free to install; check the license before commercial use.

Who made Accessibility Audit?

Accessibility Audit is published by Owl-Listener in the Owl-Listener/designer-skills repository, together with 29 other skills.

Similar skills. From other creators.