Agent skill · data analytics · owl-listener

accessibility-audit

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

Why this skill is useful

Provides detailed remediation steps and severity ratings for accessibility issues that the AI wouldn't reliably generate on its own.

What it needs

About 1k tokens when loaded. Last updated 2026-06-14. 1,982 stars on the source repository.

What this skill does

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

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills owl-listener/accessibility-audit

View the source on GitHub

Browse the @skills marketplace