What problem does it solve? Keyboard users often encounter unreachable controls, illogical tab order, invisible focus indicators, focus traps, and pointer-only interactions that block task completion. This Skill produces evidence-based findings that separate source-confirmed defects from behavior requiring runtime verification, mapped to applicable WCAG success criteria. ## Core Features & Use Cases - Comprehensive Keyboard Coverage: Audits tab order, focus visibility, focus movement and restoration, dialogs and overlays, custom composite widgets, keyboard shortcuts, disabled states, and pointer-only interactions. - Dual Evidence Model: Combines deterministic source-code inspection with manual keyboard testing in a running interface, assigning statuses like confirmed, provisional, or needs-validation. - WCAG 2.2 Mapping: Maps confirmed findings to specific success criteria (2.1.1 Keyboard, 2.4.3 Focus Order, 2.4.7 Focus Visible, and more) with per-finding rationale, without claiming full conformance. - Use Case: A QA team reviewing a design-system dialog component can run this audit to verify focus containment, Escape behavior, and focus restoration, receiving a structured report with severity, user impact, and retest steps. ## Quick Start Audit the checkout flow in this repository for keyboard accessibility and focus management issues, and report confirmed findings with WCAG mappings.
