- Success Criterion 2.4.3
- Conformance level A
Expanded Content That Never Receives Keyboard Focus
2.4.3 — Focus Order
Scenario
Setting
A food delivery app's restaurant menu
What’s wrong
Focus not moved to revealed content (accordion/inline edit) when operation depends on sequence.
Example
Picture a food delivery app's restaurant menu: focus not moved to revealed content (accordion/inline edit) when operation depends on sequence.
Why it matters
Keyboard and screen-reader users who follow focus rather than the pointer. On a food delivery app's restaurant menu, this barrier means they can't complete the task using a keyboard alone.
How to test
Trigger content that reveals more content (accordion expand, inline edit): check whether focus moves to the newly revealed content when the interaction depends on continuing there.
How to fix
Move focus to the revealed content when the interaction depends on continuing there.
Outcome
Corrected, a food delivery app's restaurant menu now lets a visitor complete the task using only the keyboard, specifically for the “Expanded Content That Never Receives Keyboard Focus” issue on a food delivery app's restaurant menu.
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
- Hidden Navigation Items That Are Still Reachable by Tab