What problem does it solve? Visually polished interfaces can still trap keyboard users in modals, hide focus behind sticky UI, make form errors unrecoverable, or announce the wrong content to screen readers. This Skill turns a feature's user flow into explicit accessibility requirements before code is written, and structures evidence gathering so an automated scan is never mistaken for a WCAG conformance verdict. ## Core Features & Use Cases - Requirements-First Workflow: Define acceptance criteria covering keyboard, focus, forms, motion, and target browser/AT environments before implementation begins. - Pattern Decision Rules: Choose native HTML controls first, apply WAI-ARIA 1.2 only when native semantics fall short, and document full interaction contracts for composite widgets like tabs, comboboxes, and dialogs. - Hybrid Testing & Evidence: Combine bounded automated checks with manual keyboard protocols, accessibility-tree inspection, and screen-reader task completion, recording pass/fail/blocked results per criterion. - Use Case: Ask your agent to design an accessible profile editor modal, and it will produce keyboard, focus restoration, form recovery, and browser/AT verification requirements plus a release evidence record. ## Quick Start Ask your agent to turn a feature flow into accessibility acceptance criteria, for example: design an accessible profile editor modal with keyboard, focus, form recovery, and browser/AT verification requirements before writing code.
