Accessibility review needs to travel with a component without becoming another approval system.
Design-system teams need visible review coverage, while the canvas must remain fast and collaborative for everyday design work.
Who you’d be doing this for
“A developer asked about the error state again today, and I had to hunt through comments to answer.”
Tereza Volkov · Design Systems Lead
Owns a shared component library used by designers and developers across an enterprise workspace.
What is at stake
Developers are reopening shared components because accessibility review coverage is invisible across variants. You must weigh a useful handoff signal against the cost of adding process to the canvas.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- handoff confidence vs authoring friction
- persistent canvas state vs rendering cost
- visible review context vs false certainty
- component reuse vs workflow complexity
Why Figma
Dev Mode turns component libraries into implementation inputs, so missing review context reaches the same handoff surface developers use to build product UI.
Written with these in mind
Not your kind of problem? 45 more at Figma, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.