- Success Criterion 2.4.3
- Conformance level A
Toolbar With a Broken Roving Tabindex Pattern
2.4.3 — Focus Order
Scenario
Setting
A photo-sharing app's upload screen
What’s wrong
Toolbars where roving tabindex (a toolbar keyboard pattern) is broken, scattering stops.
Example
.field-3 { order: 1; } .field-1 { order: 3; } /* tab order scrambled by CSS */Why it matters
Keyboard and screen-reader users who follow focus rather than the pointer.
How to test
Tab through a toolbar: if the roving tabindex pattern is broken (each button is its own tab stop instead of one stop with arrow-key navigation inside), it fails.
How to fix
Fix the roving tabindex (a toolbar keyboard pattern) so the toolbar is one stop with arrow-key movement inside.
<!-- Reorder the actual DOM nodes to match the intended focus sequence -->Focus order should follow a sequence that preserves meaning, matching how the content is meant to be read.
Outcome
On a photo-sharing app's upload screen, this barrier is gone for keyboard and screen-reader users who follow focus rather than the pointer — they no longer have to work around this.
Who is affected
Keyboard and screen-reader users who follow focus rather than the pointer.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Tab Order That Jumps Around the Page Illogically
- Dialog That Opens Far From the Button That Triggered It
- Visual Layout Order That Doesn’t Match the Keyboard Tab Order
- Modal That Opens Without Moving Keyboard Focus Into It
- Modal That Closes Without Returning Focus to Its Trigger
- Expanded Content That Never Receives Keyboard Focus