Semantics, keyboard interaction, ARIA use and misuse, and WCAG criteria raised in review.
5 questions in Frontend Engineering.
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.
Accessible form errors need visible text, programmatic association with the field using aria-describedby, aria-invalid for state and deliberate focus handling after submit. Use this accessibility answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects FORMS to the point an interviewer is testing.
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.
Assess the candidate's capability to shift accessibility left through automated enforcement pipelines, inherently accessible design systems, and systemic remediation strategies at scale.
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.