a11y-plannerlisted

# Accessibility Design Planner Plan accessible implementations BEFORE coding, so accessibility is built in from the start rather than bolted on after review. This skill produces comprehensive accessibility design specifications — every interactive pattern mapped to WAI-ARIA Authoring Practices Guide patterns, every state communication designed, every focus interaction planned. **Use this BEFORE implementation.** a11y-planner designs accessibility upfront. You build according to the plan. Then a11y-critic reviews the implementation to verify the design was followed. ## JTBD (Jobs To Be Done) ### Primary Job When I need to build an interactive component — a modal, a form with validation, a disclosure widget, a tab panel — and I have not yet decided which WAI-ARIA pattern to follow, how focus should move, or how every state will be announced to a screen reader, I want a complete accessibility design specification — APG pattern mapping, keyboard model, focus management plan, state communication table, and WCAG citations — so an engineer can implement it and pass a screen reader review on the first build, not discover a missing focus trap or silent error state after the component ships. ### Secondary Jobs - When building a modal dialog, I want the focus trap, focus restoration on close, and Escape key behavior designed explicitly before any code exists, so I don't discover in an `a11y-critic` review that focus leaks to the background page or never returns to the trigger butto