# Accessibility Audit > Use when auditing a web interface for WCAG 2.2 AA/AAA compliance, fixing reported accessibility violations, verifying ARIA usage, checking keyboard navigation or color contrast, or preparing accessibility documentation for a release. - Skill: `uw-ssec/accessibility-audit` (Agent Skill, multi-file: 6 files) - Install (CLI): `npx skillmds add uw-ssec/accessibility-audit` - Raw SKILL.md: https://api.skillmd.com/api/skills/uw-ssec/accessibility-audit/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Web & Frontend - Author: uw-ssec (https://skillmd.com/u/uw-ssec) - Updated: 2026-09-10 - Page: https://skillmd.com/skills/uw-ssec/accessibility-audit --- # Accessibility Audit ## Audit Workflow ### Step 1 — Automated scan (axe + pa11y + Lighthouse) Run all three. Each catches different issues. ```bash # axe-core CLI (most accurate rule coverage) npx @axe-core/cli https://example.com --tags wcag2a,wcag2aa,wcag22aa --save axe-report.json # pa11y (CI-friendly, exits non-zero on failures) npx pa11y --standard WCAG2AA --reporter json https://example.com > pa11y-report.json # Lighthouse (accessibility category) npx lighthouse https://example.com --only-categories=accessibility --output=json --output-path=lh-report.json --chrome-flags="--headless" ``` Expected axe output shape: ```json {"violations":[{"id":"color-contrast","impact":"serious","nodes":[{"target":["#cta-btn"],"failureSummary":"..."}]}]} ``` **Checkpoint:** If axe reports any `impact: "critical"` or `impact: "serious"` violations, fix before proceeding to Step 2. Lighthouse accessibility score must be ≥ 95. ### Step 2 — Keyboard pass Tab through the entire flow. For each interactive element verify: receives focus, has visible focus ring, responds to Enter/Space, no traps, Escape closes overlays, focus restores on close. **Pass/fail:** Every interactive element reachable and operable with keyboard only. Skip link present and works on first Tab. ### Step 3 — Screen reader pass Test critical flows with VoiceOver (macOS: `Cmd+F5`) or NVDA (Windows). Verify each control announces role + name + state. Verify form errors are announced via `aria-live` or `role="alert"`. Verify dynamic updates reach the user. **Pass/fail:** No control announces as "button" with no name. No silent state changes on submit/error. ### Step 4 — Contrast & zoom - Run axe color-contrast (already in Step 1). Cross-check focus rings against all backgrounds (axe misses these). - Zoom to 200% and 400% — no horizontal scroll, no clipped content, no overlap. - Test light, dark, and forced-colors / high-contrast modes. **Pass/fail:** Text ≥ 4.5:1, large text ≥ 3:1, UI components ≥ 3:1, focus indicators ≥ 3:1 against adjacent colors. ### Step 5 — Content review Link text descriptive (no "click here"), `` set, error messages identify the field and suggest a fix, captions on video, `alt` on images (`alt=""` if decorative). ### Step 6 — Document findings Use this table format for the report: ```markdown | # | WCAG SC | Severity | Location | Issue | Fix | Status | |---|---------|----------|----------|-------|-----|--------| | 1 | 1.4.3 Contrast (Min) | Critical | /pricing #cta-btn | 3.2:1 white on #6FA8DC | Use #1A5490 (8.1:1) | Open | | 2 | 2.4.7 Focus Visible | Serious | global `button:focus { outline: none }` | No focus indicator | Add `:focus-visible { outline: 2px solid var(--focus) }` | Fixed | | 3 | 4.1.2 Name/Role/Value | Critical | header search icon button | No accessible name | Add `aria-label="Search"` | Open | ``` ## Top 10 Common Failures (Fix Order) | # | Failure | Quick Fix | |---|---------|-----------| | 1 | Missing alt text | Add descriptive `alt`; `alt=""` for decorative | | 2 | Low contrast text | Raise to ≥ 4.5:1 (normal) / 3:1 (large) | | 3 | Missing form labels | `