Audit template
accessibility
Audit your product against WCAG 2.2 AA with evidence and a conformance verdict.
Maps to: WCAG 2.2 · EAA · ADA/508
How this audit works
A swarm of specialists each own one slice of the disability experience — keyboard, screen reader, focus, contrast, forms, zoom and reflow, target size, motion, and cognitive load. Every finding cites a concrete artifact (a DOM selector, a computed accessible name, a contrast ratio with both hex values, a keyboard sequence) and maps to a specific WCAG Success Criterion and level. It runs automated scanners and manual checks, then produces a VPAT-ready conformance table that names what automation can't catch.
Use it when
EU Accessibility Act deadline
The EAA is in force and you need a conformance verdict for the Accessibility Statement, not a vague to-do list. This audit produces a WCAG 2.2 AA pass/partial/fail verdict with a VPAT-ready conformance table and names your concrete legal exposure under the EAA, ADA, and EN 301 549.
Design-system component review
One shared button or modal that fails on accessibility breaks every page that uses it. The audit deduplicates to the root component instead of filing the same issue 40 times, and flags compound barriers — like a missing focus indicator combined with SPA route-change focus loss — that strand keyboard and screen-reader users.
Keyboard-only and screen-reader paths
Your app looks fine with a mouse, but you've never walked it with the keyboard or a screen reader. This audit verifies tab order against visual order, catches keyboard traps and unlabeled controls, checks that focus moves and restores in modals and on route changes, and confirms async updates and errors are actually announced.
What you get
A conformance verdict and VPAT-ready WCAG 2.2 table, a per-dimension scorecard, and priority-sorted GitHub issues — each mapped to its Success Criterion with a before/after fix and re-audit criterion.