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

.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

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.

<!-- 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 food delivery app's restaurant menu, this barrier is gone for keyboard and screen-reader users who follow focus rather than the pointer — they get the same result as anyone else here.

Who is affected