accessibility-audit

1# Accessibility Audit
2 
3Run a thorough accessibility audit and produce a remediation plan. Stack-agnostic. Anchored to WCAG 2.1 AA, with notes on AAA where relevant.
4 
5This skill goes deeper than the accessibility checks in `qa-testing` and `design-standards`. Use this when accessibility itself is the goal.
6 
7---
8 
9## When to use
10 
11- Pre-launch accessibility verification
12- Compliance preparation (ADA, EN 301 549, AODA, Section 508)
13- Remediation after an audit finding or complaint
14- Annual or quarterly accessibility health check
15- Onboarding accessibility into a team that hasn't prioritized it before
16 
17## When NOT to use
18 
19- General QA after deploys (use `qa-testing`)
20- Component-level accessibility implementation (use `frontend-component-build`)
21- Color contrast for design tokens (use `design-standards` or `brand-identity`)
22 
23---
24 
25## Required inputs
26 
27- The site or product under audit
28- The scope (full site, specific section, specific user flow)
29- The target standard (WCAG 2.1 AA is most common)
30- Any specific concerns or known issues
31- Tools available (automated scanners, screen readers, manual testing)
32 
33---
34 
35## The framework: WCAG's 4 principles
36 
37WCAG organizes accessibility around four principles. The audit covers each in depth.
38 
39### 1. Perceivable
40 
41Information and UI must be presentable in ways users can perceive.
42 
43**Audit checks:**
44…