Accessibility Interview Questions

Semantic HTML uses elements according to meaning, such as button, nav, main, h1, label, and table. It gives browsers and assistive technologies reliable roles, names, and structure.

Normal text needs at least 4.5:1 for WCAG AA. Large text needs at least 3:1.

Alt text is a text alternative for meaningful images. It should describe the image purpose. Decorative images should usually use empty alt text.

A label gives the input an accessible name, makes the field easier to understand, and can increase the clickable area for mouse and touch users.

Use Tab, Shift+Tab, Enter, Space, Escape, and arrow keys where appropriate.

Use aria-label when a control needs an accessible name and there is no visible text that can label it. Prefer visible text or aria-labelledby when possible.

Confirm all interactive controls are reachable, the focus order is logical, focus is visible, activation works with keyboard, Escape works where expected, and there are no keyboard traps.

Use alert for urgent messages that need immediate attention, such as validation failures. Use status for polite non-urgent updates, such as saved or copied messages.

It connects an element to additional descriptive text such as help text, error messages, or format instructions.

Placeholder text disappears or becomes less useful after typing, often has low contrast, and may not provide a reliable accessible name.

A useful link name describes the destination or action in context, such as "View June accessibility report" instead of "Click here".

Automated tools cannot fully judge meaning, usability, expected announcements, custom workflows, keyboard traps, screen reader quality, or whether text alternatives are useful.

It has a clear accessible name, moves focus inside when opened, keeps focus inside while open, restores focus when closed, supports Escape, and prevents background content from being reached.

Menu roles create application-style keyboard expectations. Normal site navigation should usually use nav, lists, and links so users get familiar browser and assistive technology behavior.

Check that typing, arrow keys, selection, Escape, focus behavior, aria-expanded, active option, selected value, and screen reader announcements all match the visual behavior.

It removes content from the accessibility tree. If it hides focusable or meaningful content, screen reader users may lose access to controls or context.

Start with native elements, document component keyboard behavior, add ARIA only for missing semantics or state, test with assistive technology, and prevent teams from overriding semantics incorrectly.