a11y-auditlisted

Use when auditing accessibility compliance of a feature or codebase. Covers WCAG 2.2 AA conformance, screen reader compatibility, keyboard navigation, focus management, color contrast, reduced motion, and ARIA usage. Do not use for general UX review (use journey-mapping) or component interaction specs (use interaction-design).
dtsong/my-claude-setup · ★ 5 · AI & Automation · score 76

Install: claude install-skill dtsong/my-claude-setup

# A11y Audit ## Purpose Evaluate accessibility compliance against WCAG 2.2 AA criteria across perceivable, operable, understandable, and robust principles. Identify barriers for users of assistive technologies and provide actionable remediation steps. ## Scope Constraints Reads source code, templates, styles, and component markup for accessibility analysis. Does not modify files or execute code. Does not perform automated accessibility scans (recommend tooling where appropriate). ## Inputs - Feature description or codebase path to audit - Target WCAG conformance level (default: AA) - Known assistive technologies in scope (screen readers, switch devices, etc.) - Any existing accessibility testing results or known issues ## Input Sanitization No user-provided values are used in commands or file paths. All inputs are treated as read-only analysis targets. ## Procedure ### Progress Checklist - [ ] Step 1: Audit keyboard navigation and focus management - [ ] Step 2: Evaluate screen reader compatibility - [ ] Step 3: Check color contrast and visual accessibility - [ ] Step 4: Review ARIA usage and semantic markup - [ ] Step 5: Assess motion and animation accessibility - [ ] Step 6: Verify form and error handling accessibility ### Step 1: Audit Keyboard Navigation and Focus Management - Verify all interactive elements are reachable via Tab/Shift+Tab. - Check focus order matches visual reading order. - Confirm visible focus indicators on all interactive elements (`:focus-