foundation

Accessibility basics

Keyboard navigation, focus order, native semantics, accessible names, and ARIA as a last resort.

HTML accessibility interviews test keyboard operability, focus management, and native semantics before ARIA overlays. The goal is equivalent experience: sighted mouse users, keyboard users, and screen reader users should understand state and complete tasks.

Subtopics: keyboard navigation and visible focus; native semantics and when ARIA is appropriate.

On interviews: describe testing with keyboard only and what you check in the accessibility tree.

Common pitfalls: removing focus outlines; click-only handlers; positive `tabindex` as a layout hack.

Checklist:

Keyboard path for every action.
Visible focus indicators.
Native elements before ARIA.
Errors and state exposed to assistive tech.