Interview answer guide · 03
Lead with accessibility
How do keyboard behavior, focus management, contrast, and WCAG guide implementation decisions?
A clear answer
What I would say in an interview.
I treat accessibility as part of the interaction design, not a final audit. I prefer native elements because they bring reliable keyboard behavior and semantics. When a component opens or changes context, I define where focus goes, keep the focus order meaningful, provide a visible focus indicator, and make sure focus can leave the component. I check text contrast against its actual background, not just a palette token. WCAG gives me measurable criteria—such as keyboard operation, focus order, and contrast—while manual keyboard and screen-reader checks reveal how the experience feels in practice.
Key points
Details worth backing up.
- 01
Every mouse action should have a keyboard path; do not create a keyboard trap.
- 02
When sequential navigation matters, focus order must preserve meaning and operability.
- 03
Keep focus visible, including in custom controls and high-contrast themes.
- 04
For normal text, WCAG AA requires at least a 4.5:1 contrast ratio; large text has a 3:1 threshold.
References