Design accessibility review
Checks on design files before build, so barriers never reach code. Fixing in Figma costs far less than fixing in production.
What a review checks
-
Contrast and type
Text contrast, font sizes and spacing against WCAG 2.2, measured on the actual palette.
-
Focus and flow
Focus order, visible focus states and keyboard paths drawn across each flow.
-
Structure and names
Headings, landmarks and accessible names for controls, before developers guess them.
-
Components and states
Buttons, forms, errors and empty states, with the specs developers need.
Design review questions
What files do you review?
Design files from tools such as Figma, including flows, components and variants. Share view access and we annotate findings on the screens themselves.
Can a review replace testing the built product?
No. A review catches what is visible in static files. Code behaviour still needs testing after build.
What does the design team receive?
Annotated findings on each screen, with the criterion and a fix. Plus a checklist your designers reuse on the next screens.
Book your free call
Show us your files in 30 minutes. We tell you what a review would catch.