Operable
WCAG 2.4.3
Focus Order
Tab order must follow a logical reading sequence — typically left-to-right, top-to-bottom. Avoid positive tabindex values. CSS layout changes (order, flex-direction) can break focus order.
In plain terms
Pressing Tab should move through the page in a sensible reading order, not jump around unpredictably.
Why this matters
Keyboard and screen-reader users move through a page in code order. If that order jumps around, they can reach a footer before a form, or tab into a closed menu — confusing and disorienting.
How to detect
Quick check
Tab through the page and watch the focus ring. Does it follow the visual reading order, top to bottom? Watch for spots where it leaps unexpectedly — often caused by CSS reordering or positive tabindex.