Same Form, Three CSS Builds: How One Line Silently Breaks Keyboard Navigation
A web development essay demonstrates how two visually identical interface implementations can behave very differently for keyboard users. Using a simple preferences form with unchanged HTML markup, the author rebuilds the same UI three times, altering only the CSS each time. The default browser version provides full keyboard focus indicators, while a common CSS reset that includes 'outline: none' silently removes them, leaving keyboard users unable to track their position. A third pass restores accessibility by replacing the blanket focus removal with a 'focus-visible' rule that shows focus rings for keyboard input without affecting mouse users. The piece argues that standard visual QA cannot detect such accessibility failures because it only evaluates appearance, not functional communication.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in