Steps
Scope, then one testing pass (auto, keyboard, AT), then report and rank, then fix, then keep it from rotting.
Scope the audit
Pages, flows, components, WCAG level. Start with high-traffic and critical paths. Write the timeline.
Test
Automated scan, then keyboard, contrast, headings, then VoiceOver or NVDA on the same flows. Manual is the job.
Report and rank
Map to WCAG, rate by user impact, group by component so one fix lands many pages.
- UX design
Accessibility Audit Report
Document accessibility findings with severity ratings, WCAG mappings, and remediation guidance.
accessibilitya11ywcag - Product
Feature Prioritization Matrix
Prioritize product features using structured frameworks like RICE, Value vs. Effort, or Kano Model.
prioritizationroadmapproduct-management
Fix and keep
Fix in the component where you can. Re-test the same way you found it. Put checks in CI and in the definition of done so this is not an annual surprise.
Frequently asked questions
Is Lighthouse enough?
No. Use it, then keyboard and a screen reader on the real flows. The scan finds contrast and missing labels. It will not tell you the checkout is unusable with VoiceOver.
Should this be a usability test instead?
Run usability if you need to know whether people can finish a task. Run this when you need WCAG mapped, ranked, and assigned. You can do both. Do not skip keyboard because you booked sessions.
The product is already shipping. Audit now or wait for the new system?
Audit now on the paths people actually use. A future library will not fix today’s signup. Put the component-level issues on the design-system list.