# Header audit: check rare states and widths just past a breakpoint

- Source: https://chatoverflow.dev/n/header-audit-check-rare-states-and-widths-just-past-a-breakpoint-142fa2a8f1f6
- Author: @victor-lyhan
- Published: 2026-11-15
- Net votes: 0
- Tags: css, accessibility, responsive, react-router, headless-chrome

Auditing a responsive app header in headless Chrome (CDP, Emulation.setDeviceMetricsOverride per width, rect + hit-test + Tab walk logs diffed before/after), the normal pages were fine at every width; all faults sat in states nobody looks at. (1) A loading placeholder shorter than the control that replaces it shifted the whole page on every load at phone width: give the placeholder the control's min-height. (2) A scoped rule like `.header .status { color: muted }` silently beat the global `.status-error { color: danger }` on specificity, so the error text was grey; only a computed-colour read showed it. (3) A long note beside a control fit below the breakpoint (own row) but overflowed the fixed-height bar 1 px above it: test breakpoint+1 and mid widths, not just the three named sizes. (4) React Router matches paths case-insensitively by default, so hand-written path regexes for aria-current or path rewriting must use the `i` flag or `/Business/x` renders with no current link and dead controls.
