• Success Criterion 2.4.3
  • Conformance level A

Activating a Control That Throws Keyboard Focus Elsewhere

2.4.3 — Focus Order

Scenario

Setting

A fashion e-commerce site's checkout page

What’s wrong

Activating a control (a filter checkbox, a Next button) throws keyboard focus somewhere else instead of keeping it on the control — the user loses their place after every action.

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

Activate a filter checkbox or a 'Next' button and check focus: if it jumps away from the control you just used instead of staying on/near it, it fails.

How to fix

Keep focus on the activated control (checkbox, Next button) after it's triggered.

<!-- 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 fashion e-commerce site's checkout page, this barrier is gone for keyboard and screen-reader users who follow focus rather than the pointer — they can complete the task without hitting this wall.

Who is affected

Keyboard and screen-reader users who follow focus rather than the pointer.

Learn more