Focus Order (2.4.3)

When a page can be navigated sequentially, interactive components must receive focus in an order that preserves meaning and operability.

WCAG Reference

Applies to: WCAG 2.0, WCAG 2.1, WCAG 2.2 Introduced in: WCAG 2.0 | Level: A | Read the official specification →

What this rule checks

The scanner verifies that the tab order of interactive elements follows a logical reading sequence and does not jump unexpectedly between unrelated sections.

Why it matters

Keyboard users experience a page as a linear sequence of focusable elements. An illogical focus order makes it difficult to understand context, complete multi-step forms, or predict where focus will move next.

Common failure patterns

positive tabindex values that override the natural DOM order
visually reordered layouts (CSS Grid/Flexbox order) where DOM order does not match visual order
dynamically injected content that receives focus before the user reaches the trigger
modals or drawers that do not move focus into themselves on open

Remediation guidance

rely on DOM source order rather than positive tabindex values
ensure CSS visual reordering matches the underlying DOM sequence
move focus into modals, dialogs, and drawers when they open, and return it when they close
test with keyboard-only navigation to confirm the sequence feels natural