← ClaudeAtlas

accessibility-reviewlisted

Use as a REVIEW LENS when judging another agent's UI diff for accessibility defects against WCAG 2.2 AA — missing labels and names, keyboard traps or unreachable controls, focus not managed or obscured, colour-only meaning, insufficient contrast, small targets, drag-only interactions, unannounced dynamic changes — before recommending approval. Invoke on every review of a ticket that adds or changes user interface; it complements review-ticket and frontend-a11y (the builder's skill), it does not replace them.
tmj-90/gaffer · ★ 1 · AI & Automation · score 70
Install: claude install-skill tmj-90/gaffer
# Accessibility review lens Inaccessible UI is a correctness defect: a control a keyboard cannot reach does not work for that user. Judge the rendered result, not the intent — read the markup the component produces, trace keyboard and focus behaviour through the code, and use the automated audit the repo already has. Each finding names the control, the WCAG 2.2 success criterion (SC) it fails, and the fix. Only Level A and AA failures on UI the ticket added or changed can block. ## Steps 1. **Identify the UI the diff adds or changes** and how a user operates it: controls, forms, dialogs, menus, tabs, live regions, media, drag interactions. If the diff has no UI, write "no UI — n/a" and stop. Call `search_lore` for the repo's a11y conventions and shared components (a shared accessible `Dialog` or `Button` is usually the fix). 2. **Use the automated audit the repo provides** (jest-axe / vitest-axe in component tests, `@axe-core/playwright` in browser tests, eslint-plugin-jsx-a11y). Its findings are findings; its silence proves little — automated rules cover only part of WCAG (focus order, names that make sense, announcements need reading). Do not install tools; run an existing command at most once. 3. **Trace the keyboard path** through the code: Tab order follows visual order (no positive `tabindex`); every interactive element is focusable and operable (Enter/Space on buttons, arrows inside menus, tabs and listboxes per the ARIA Authoring Practices