Builders & Flows

Accessibility audit

Public

Bringing an existing product up to WCAG without stopping the roadmap.

Shun Leeby Shun LeePublished 25 Jul 2026, 02:04 · 9 views
0.0s / 0.0s

How this workflow works

Audit

HotjarAutomated + 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

LinearSeverity 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 + StorybookFix components

Fixes land at the component level, not the page level, so one repaired button fixes every screen that uses it.

Verify

StorybookScreen-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

ZeroheightA11y 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.