Consider Figma’s documented accessible-prototype guidance when reviewing interaction flows.
Start with the finished task
Define the user task, failure state and keyboard path before using AI to draft layout or copy. Check the design in a prototype and then in the implemented product.
- 1Write the happy path and
Write the happy path and one failure path.
- 2Review labels, focus order and
Review labels, focus order and recovery instructions before visual polish.
- 3Build a prototype to discuss
Build a prototype to discuss the flow, then test the actual implementation for keyboard behavior and announcements.
- 4Record findings rather than giving
Record findings rather than giving the design a blanket pass.
Choose a workflow that fits
Treat generated layouts as draft artifacts. Avoid claiming accessibility compliance from a screenshot or automated suggestion.
| Tool | Source evidence | Confirm before buying |
|---|---|---|
| Figma ↗ | Figma documents accessibility considerations for prototypes. | Prototype behavior and implemented keyboard and assistive-technology support. |
| Manual or conventional route | Use direct prototyping when the flow is already defined and needs interaction review. | Editorial workflow advice; this is not a measured comparison or vendor performance claim. |
The correction in our worked example
The revised specification adds information and an explicit verification task; it does not claim a tested accessible implementation.
Fictional checkout: the address is invalid; the screen shows only a red border.
The form is clear because the red outline indicates the error.
Specification: show “Enter a postcode” beside the field, associate the message with it and preserve the entered address. Verify focus and announcement in implementation.
Build and inspect the handoff
Write the happy path and one failure path. Review labels, focus order and recovery instructions before visual polish. Build a prototype to discuss the flow, then test the actual implementation for keyboard behavior and announcements. Record findings rather than giving the design a blanket pass.
Review the error recovery
A useful error message tells the user what to fix and keeps their entered information. Check focus and announcement in the working interface; a static visual cannot establish either behavior. Use direct prototyping when the flow is already defined and needs interaction review.
Compare the full cost
Include prototyping and implementation review time in the budget. More screens generated per credit do not establish better task completion.
Workflows questions
Can an AI mockup prove accessibility?
No. Inspect semantics and interaction in the working implementation, including keyboard and assistive-technology behavior.
When is a simpler workflow a better choice?
Use direct prototyping when the flow is already defined and needs interaction review.
THE RESEARCH DESK
Sources & methodology
Official documentation was consulted on 2026-10-07. The worked example uses fictional inputs and was edited for this guide. No vendor application benchmark or outcome test was performed. Prices and allowances should be confirmed before purchase.
help.figma.com · 7810391964695-Accessible-prototypes-in-Figma↗Put this guide to work
Your decision criteria: Prototype behavior and implemented keyboard and assistive-technology support.
- Fictional checkout: the address is invalid; the screen shows only a red border.
- A useful error message tells the user what to fix and keeps their entered information. Check focus and announcement in the working interface; a static visual cannot establish either behavior.
- Prototype behavior and implemented keyboard and assistive-technology support.
AI tools for HR: build a checked onboarding handoff →
AI tools for LinkedIn: improve a profile without inventing a career →