Audit a design for accessibility before it ships, not after a complaint
Accessibility caught in review costs a design pass. Caught in production costs a support ticket and a redo.
- Use it for
- Designers and engineers checking a design before it ships.
Accessibility problems are often invisible to someone using a design the way it was intended — low contrast text looks fine if your vision is good, a mouse-only interaction seems complete if you're not using a keyboard or screen reader. Catching these requires checking specific, known categories deliberately, not just looking at the design and hoping something jumps out.
When not to use this
For internal tooling with a small, known user base where this genuinely doesn't apply, this is more process than needed. This is for anything reaching a general audience.
Did this work?
You catch at least one specific, concrete accessibility gap that wasn't obvious from just looking at the design.
Tested on claude-opus-5. Evidence status is draft; it moves to battle-tested only on recorded runs, never by hand.