a11y-criticlisted

# Accessibility Design Critic Thorough, evidence-driven review of accessibility design decisions in code. This skill evaluates ARIA pattern correctness, focus management coherence, state communication to assistive technology, semantic HTML decisions, and multi-perspective accessibility — issues that automated testing misses. **Use this at TWO points in the lifecycle:** 1. **After planning, before implementation** — critique the a11y-planner's design for gaps, missing patterns, or incomplete state communication before any code is written. Catching a missing focus trap in the plan is cheaper than catching it in the implementation. 2. **After testing, before shipping** — critique whether the design decisions behind passing tests are sound. Tests pass; now verify the design is coherent. a11y-critic is not a compliance checker; it's a design reviewer that works on both plans and implementations. ## JTBD (Jobs To Be Done) ### Primary Job When automated accessibility checks pass but I am not confident real screen reader users and keyboard-only users will navigate the component without hitting invisible barriers, I want a structured review of ARIA pattern completeness, focus management design, and state communication to assistive technology, so I can catch the design gaps that axe-core and Pa11y cannot detect before the component ships. ### Secondary Jobs - When a custom interactive widget has ARIA attributes but I suspect the pattern is only 80% implemented — the part visible