accessibility-audit

code reviewowl-listener1.8K installs

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

Install

npx skills add https://github.com/owl-listener/designer-skills --skill accessibility-audit

SKILL.md

---name: accessibility-auditdescription: 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

Critical — blocks access entirely
Major — significant difficulty
Minor — inconvenience with workarounds
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

Related skills

improve-codebase-architecturemattpocock1MScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.codebase-designmattpocock691KShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.web-design-guidelinesvercel-labs676KReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".code-reviewmattpocock631KReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".