An accessibility review checks that tokens, components, patterns, and templates meet accessibility standards. Use this to catch issues early so they can be fixed once in the system rather than repeated across products. Reviews build confidence that the system supports inclusive design and reduce the risk of accessibility bugs in production.
Accessibility Review
How to
-
Set your scope
Decide if you are Auditing tokens, patterns, templates, or the full system. Start small if needed.
-
Review standards
Check against guidelines such as WCAG. Focus on colour contrast, scale, spacing, motion, and interactive states.
-
Audit for context
- Tokens: review typography for readability, colour palettes for contrast, and spacing for touch targets.
- Patterns: check interactive elements for focus states, keyboard navigation, and screen reader support.
- Use vision tools to quickly scan for obvious contrast issues and touch target sizes
-
Capture findings
Document issues, group by severity, and share results with the system team.
-
Translate into updates
Feed fixes back into tokens, patterns, or documentation so improvements scale everywhere.
First pass only: AI catches technical issues like contrast ratios and sizes but can't replace manual testing with assistive tech or real users with disabilities. Use it for initial scans only.