Accessibility Audit Template for User Research

Level A is the minimum. It covers requirements that block access entirely (keyboard traps, missing alt text, seizure-inducing flashes). Level AA adds requirements that affect a wider range of disabilities (contrast ratios, reflow, focus visibility). Level AA is the standard most organizations target and what most regulations require. Level AAA is aspirational and covers enhanced requirements (7:1 contrast, sign language for video). Few products achieve full AAA conformance.

A focused audit of one page or flow takes 3-5 hours (1 hour automated scanning, 2-4 hours manual testing). A full product audit for a medium-sized SaaS application typically takes 2-4 weeks of dedicated effort. Start with the highest-traffic pages and the most critical user flows.

No. Automated scanners catch approximately 30-40% of WCAG issues (missing alt text, contrast failures, ARIA errors). They cannot test whether alt text is meaningful, whether keyboard interaction is logical, whether screen reader announcements make sense in context, or whether the visual reading order matches the DOM order. Always supplement automated scans with keyboard and screen reader testing.

Everyone. Designers own contrast, focus states, and semantic structure in mockups. Engineers own implementation (HTML semantics, ARIA attributes, keyboard handling). PMs own the requirement that accessibility is part of the [definition of done](/glossary/acceptance-criteria). QA owns testing with assistive technologies. An accessibility audit is a team deliverable, not one person's job.

WCAG applies to web content, but the principles translate directly. iOS uses the Accessibility API (VoiceOver, Dynamic Type, Reduce Motion). Android uses TalkBack and the Accessibility Scanner. The [mobile app design checklist](/templates) covers platform-specific accessibility requirements alongside general UX patterns. ---