Accessibility Interview Questions

Do not let the screen reader announce the answer token by token. Keep the streaming text out of an active live region, and use a separate, visually hidden polite status region to announce short lifecycle messages such as "Generating response" and "Response complete". Keep focus in the input, give each message a clear structure the user can navigate, and test with real screen readers because live region support varies.

Design a full theming system: semantic tokens, prefers-color-scheme defaults, a manual override attribute, no-flash hydration, and color-scheme for native UI.

Learn the three arguments of clamp(), how the preferred value produces continuous scaling, and the accessibility rule for using it with type.

Compare absolute and relative CSS units by what they resolve against, and learn the accessibility and compounding consequences of each choice.

Three focus pseudo-classes with three different jobs, and the accessibility reason :focus-visible exists at all.

One selects existing elements in a particular state, the other creates a sub-part that is not in the DOM. Learn the syntax, specificity, and limits of each.

Render a controlled radio group from an array using map(). Understand the name attribute for grouping, checked from state, and accessibility with fieldset and legend.

Create a global modal manager with stacking, portal rendering, focus trapping, ESC handling, and dynamic modal types.