accessibility-reviewlisted

# Accessibility Review Review a UI change (or a whole view) for accessibility and return prioritized, concrete fixes mapped to WCAG. Design-and-review companion to `frontend-ui-engineering` and `ui-ux-design`. **Risk tier:** low–medium (raise to high if it gates a legally-required compliance surface — see `.claude/rules/risk-classification.md`). ## When to use - Reviewing any frontend/UI change, or auditing an existing view before release. - The `responsive-and-accessibility.md` rule sets the standards; this skill is the review procedure. ## Who should use it Frontend engineers, the `ui-designer` agent, QA. Designers/PMs can run it for a first pass. ## Required inputs The component/view (file paths or a running URL) and which states matter (loading, empty, error, modal). ## Ordered questions to ask 1. Is everything **operable by keyboard** (tab order, visible focus, no traps, Esc closes overlays)? 2. Is the **semantics** right (native elements over `div` soup, headings in order, landmarks, labels for every control, `alt` for images)? 3. Do interactive states expose **name/role/value** to assistive tech (ARIA only where native won't do)? 4. Does **color contrast** meet WCAG AA (text ≥ 4.5:1, large text/UI ≥ 3:1) and is color not the only signal? 5. Are **touch targets** ≥ 44×44px and is motion reduced under `prefers-reduced-motion`? 6. Are **dynamic updates** announced (live regions) and **forms** clear (labels, errors tied to inputs)? ## Agents to delegate to `ui