What problem does it solve? Web interfaces often ship with accessibility failures — keyboard traps, missing labels, low contrast, ARIA misuse — that block users relying on assistive technology. This Skill provides a structured WCAG 2.2 audit workflow that catches these issues before launch and maps every finding to a specific WCAG criterion with a concrete fix. ## Core Features & Use Cases - Automated checks first: Runs axe-core CLI and ripgrep patterns to detect missing alt text, unlabeled inputs, positive tabindex, and aria-hidden focusable elements. - Manual keyboard and screen reader protocol: Tests tab order, focus traps in modals, focus-visible indicators, and accessible names against WCAG 2.1.1, 2.4.3, and 4.1.2. - Severity-ranked report: Classifies findings as Blocker, Major, Minor, or Pass with file:line references, WCAG success criterion numbers, and fixes. - Use Case: Before releasing a checkout flow, run the audit to verify keyboard operability, form label associations, error announcements via aria-describedby, and 4.5:1 text contrast, then hand developers a prioritized fix list. ## Quick Start Audit the login page and checkout components for WCAG 2.2 AA compliance and report all blockers with fixes.