All WCAG criteria
WCAG 2.4.3 · OperableLevel A

2.4.3Focus Order

Focusable components receive focus in an order that preserves meaning and operability.

Common failures

Patterns that fail this criterion.

  • 01Custom `tabindex="2"`, `tabindex="3"` etc. that scramble the order
  • 02Modal dialogs that do not move focus into the dialog on open
  • 03Hidden but focusable elements (off-screen but still in tab order)
How to test

Testing approach: manual.

Manual — Tab through the page; confirm order is logical (matches visual order, completes form fields top-to-bottom, etc.).

How to fix

Remediation steps.

  1. 1

    No positive tabindex

    `tabindex="0"` or `tabindex="-1"` only. Anything ≥1 is almost always wrong.

  2. 2

    Manage focus on dynamic content

    Open modal: move focus inside. Close modal: return focus to trigger. Open new view: move focus to heading.

  3. 3

    Hide off-screen content properly

    Off-screen but focusable = trap. Use `display: none`, `visibility: hidden`, or `inert` attribute.

Scan for WCAG 2.4.3 on your site

Find every violation in 42 seconds.

AccessProof runs axe-core 4.9.1 against your site and flags every WCAG criterion with the offending element selector. WCAG 2.4.3 is one of 49 criteria we check on every scan.

Start free auditTry free scanner — no signup
Related criteria

Often appears with…

WCAG 2.4.7 · Level AA

Focus Visible

WCAG 2.1.2 · Level A

No Keyboard Trap

All 50 WCAG 2.1 Level A + AA success criteria explained.

View the full checklist