By name: a11y-audit description: Audit a UI or design against WCAG 2.2 AA/AAA and ARIA patterns, returning criterion-referenced findings with severity and specific fixes. Use when the user wants an accessibility check, contrast verification, keyboard/screen-reader review, or wants to confirm a component meets POUR.
Skill: Accessibility Audit
Evaluate against WCAG 2.2 and the project's ARIA patterns.
Steps
- Read
accessibility/wcag-checklist.md(POUR-organized, P0/P1/P2) andaccessibility/aria-patterns.md. - Check the mandatory P0 set per component: keyboard navigable, focus visible (≥3:1), screen-reader name/role/state, contrast (4.5:1 text / 3:1 UI), target size ≥24×24, no color-only signaling.
- Verify WCAG 2.2 additions: Focus Not Obscured (2.4.11), Target Size (2.5.8), Accessible Authentication (3.3.8).
- Contrast — measure, don't eyeball. For rendered HTML, RUN the real-render gates and report their actual output (CLAUDE.md → Verification Protocol):
node scripts/measure_render.mjs <file> [--dark](every text element) ANDnode scripts/verify_states.mjs <file> [--dark](every interactive element in default/hover/focus — catches hover-state failures). For loose color pairs,python3 scripts/contrast.py "<fg>" "<bg>". Never state a ratio you did not measure. - Check reduced-motion handling (
taste/motion-choreography.md).
Output
A findings table: WCAG criterion (e.g. 1.4.3) · severity (P0/P1/P2) · what fails · specific fix. Confirm passes explicitly. Accessibility may never be traded for aesthetics.