Accessibility for Frontend Developers
Accessibility means building interfaces that people with disabilities can use, including keyboard-only and screen reader users. WCAG 2.2 sets the standard through principles such as perceivable and operable content. Practical work includes semantic HTML, sufficient colour contrast, visible focus, alt text and correct ARIA where native elements fall short.
Stage: Quality and Performance · Part of the Frontend Developer roadmap · Last reviewed 19 November 2026
What to learn in Accessibility
- Make every interactive element reachable and usable by keyboard
- Check colour contrast against the WCAG AA ratios
- Write useful alt text and decide when an image is decorative
- Add ARIA roles and states only when native HTML cannot do the job
- Run axe or Lighthouse and test with a screen reader
Accessibility interview questions
What is the first rule of ARIA?
If a native HTML element already has the behaviour and semantics you need, use it instead of adding ARIA to another element. A real button comes with keyboard support and roles, while a div with role button needs extra scripting to match.
How do you manage focus in a modal dialog?
Move focus into the dialog when it opens, keep Tab cycling within it, close on Escape, and return focus to the trigger when it closes. The native dialog element with showModal handles much of this, and background content should be inert.
Where Accessibility fits in the Frontend Developer roadmap
Accessibility belongs to the Quality and Performance stage (beginner level), which takes about 4 hours. Make it fast, accessible, secure and tested.
Other units in this stage
Back to the full Frontend Developer roadmap