Top 3 Aria Interview Questions
Browse 3 real-world technical and behavioral interview questions about Aria. Review scenarios, edge cases, and architectural best practices.
A modal passed design and QA review, but keyboard users report they can tab out of it into the page behind, and once they do they cannot get back or close it. Diagnose it and tell me what a correct dialog does.
The dialog was built as a styled div, so nothing marks the rest of the page inert. Focus was never moved in, never constrained, never restored on close, and Escape was never wired. A correct dialog moves focus in, keeps it in, restores it, marks background inert and is labelled - which native dialog with showModal gives you almost for free.
A toast pops up saying the changes were saved, and a screen reader user hears nothing. Why, and what do you change?
Toast notifications are announced to screen readers only when the message is inserted into an existing live region with the right politeness and without hiding it from the accessibility tree.
Design rejected the native control, so you are building a custom one. How do you make it accessible?
An accessible custom interactive component should start from the nearest native element, preserve keyboard and focus behavior, and use ARIA only for state that HTML cannot express.