2.4.3 Focus Order

What this criterion requires

If a page can be navigated sequentially, focusable components receive focus in an order that preserves meaning and operability.

Who it helps

Keyboard and screen reader users following the tab sequence.

Example: fails vs passes

<input tabindex="3"> <input tabindex="1"> <button tabindex="2">

<!-- no positive tabindex; DOM order carries the sequence -->
    <input> <input> <button>

Positive tabindex values create jumping focus. Manage dialog focus in JS: in on open, back to trigger on close.

How to meet and fix it

• Keep DOM order logical; avoid positive tabindex values entirely
• On opening a dialog move focus into it; on closing, return focus to the trigger

Common failures auditors find

• Focus jumping to the footer after a form field
• Modals that leave focus behind the overlay

Automated scanning catches a share of these instantly - run a free check - and a manual audit covers the judgement calls a tool cannot make.

Last updated 12 August 2026. Reviewed by the EqualWeb accessibility team.