Performance
The accessibility audit playbook: WCAG 2.2 AA in 5 days
An accessibility audit does not have to take weeks. Here is the 5-day playbook we use to ship WCAG 2.2 AA on every public page.
An accessibility audit does not have to take weeks. Here is the 5-day playbook we use to ship WCAG 2.2 AA on every public page.
Day 1: scan
Run axe-core in CI on every public page. Triage critical and serious issues. Build the fix list.
Day 2: keyboard
Test every page with the keyboard only. Can you reach every interactive element? Is the focus order logical? Is the focus ring visible?
Day 3: screen reader
Test the top 5 user journeys with a screen reader (VoiceOver on Mac, NVDA on Windows). Are headings, landmarks and form labels announced correctly?
Day 4: contrast
Test every text-on-background combination. Body text: 4.5 to 1. Large text and UI controls: 3 to 1.
Day 5: fix
Apply the fixes. Re-run axe-core. Re-test the journeys. Document the audit and the fixes.
The deliverable
A 5 to 10 page audit report with: - The issues found (with severity). - The fixes applied. - The remaining issues (with justification). - The ongoing monitoring plan.
The ongoing work
Accessibility is not a one-off. We run axe-core in CI on every PR. We manually test keyboard and screen reader on key flows every quarter.
Keep reading
Related posts.
Questions
Frequently asked questions
Common questions about the accessibility audit playbook: wcag 2.2 aa in 5 days, answered plainly.
Was this helpful?
One tap. No email, no signup.