Accessibility for Design Systems
Accessibility in a design system means building components that people with disabilities can use, following WCAG guidelines. It covers semantic HTML, keyboard operation, visible focus, sufficient colour contrast, screen reader names and roles through ARIA where needed, and testing with assistive technology, so every product inherits good behaviour by default.
Stage: Quality · Part of the Design System roadmap · Last reviewed 19 November 2026
What to learn in Accessibility
- Check text and component colour contrast against WCAG ratios
- Make a custom dropdown fully operable with the keyboard
- Manage focus in a modal dialog and return it on close
- Use native elements first and ARIA only when required
- Test a component with a screen reader such as NVDA or VoiceOver
- Support reduced motion and zoom without breaking layout
Accessibility interview questions
When should you use ARIA attributes?
Use ARIA only when native HTML cannot express the role, state or relationship, such as a custom tab widget. Native elements like button and select already provide keyboard and screen reader behaviour, and wrong ARIA can make accessibility worse.
What is the minimum contrast ratio for body text under WCAG AA?
WCAG 2.x AA requires a contrast ratio of at least 4.5 to 1 for normal text and 3 to 1 for large text and for key user interface components. Verify with a contrast checker in every theme.
Where Accessibility fits in the Design System roadmap
Accessibility belongs to the Quality stage (intermediate level). Accessible by default.
Other units in this stage
Back to the full Design System roadmap