Accessibility audit
PublicBringing an existing product up to WCAG without stopping the roadmap.
How this workflow works
Audit
Hotjar — Automated + manual scan
An automated scan catches the easy contrast and alt-text misses first, then a manual keyboard-only pass finds what the scanner can't.
Prioritize
Linear — Severity triage
Every finding gets a severity rating — blocks a screen reader entirely vs a minor contrast nit — so fixes land in the order that matters most.
Fix
Figma + Storybook — Fix components
Fixes land at the component level, not the page level, so one repaired button fixes every screen that uses it.
Verify
Storybook — Screen-reader pass
Every fixed component gets tested with an actual screen reader, not just eyeballed — reading order and focus state have to work, not just look right.
Sustain
Zeroheight — A11y guidelines
The rules that keep the fix from regressing — contrast minimums, focus order, alt-text conventions — documented next to the components they govern.
Questions
Ask about the reasoning, not just the tools. The author gets notified here.
No questions yet.