technical
Accessibility interviews are now standard for senior frontend, design-systems, and platform roles. Practice WCAG 2.2 criteria, ARIA usage and misuse, semantic HTML, screen-reader testing, and the legal context (ADA, EAA) behind a11y requirements.
Sample questions
These are the kinds of questions you'll drill. Real mock rounds will generate many more — tailored to the exact JD you paste in.
Walk me through how a screen reader announces a modal dialog — what HTML and ARIA do you need?
Why is "ARIA: bad ARIA is worse than no ARIA" a common saying? Give an example.
How would you make a custom autocomplete component accessible? Step through the keyboard and screen-reader behaviour.
Explain colour-contrast requirements in WCAG 2.2 AA, and how you'd audit a design system against them.
What's the EAA, and how does it change accessibility requirements for EU-facing products in 2025?
Reading Web Accessibility (a11y) questions isn't the same as answering them live. You need the rep — the pause, the clarifying question, the moment where you realize you forgot the framework. We put you in that exact spot, then show you what a strong answer would have looked like.
Related topics
React
Hooks, rendering, and real-world patterns.
System Design
Scale, trade-offs, and clear reasoning.
SQL
Joins, indexes, and query plans.
Data Structures & Algorithms
Arrays, graphs, trees, and the classics.
Behavioural
STAR answers that actually land.
Leadership
Influence without authority, grown-up feedback.
Paste the JD, pick your topics, and go. Full session, full feedback, no fluff.
Start now