Published November 12, 2026

WCAG 2.4.3 Focus Order, Level A

Does WCAG require keyboard focus to follow visual order?

Yes at Level A when sequential navigation affects meaning or operation. Success criterion 2.4.3 Focus Order requires that focusable components receive focus in an order that preserves meaning and operability. On a typical left-to-right page, that is the same order a person reads: left to right, then top to bottom. The text is in the W3C WCAG 2.2 Recommendation.

What does focus order require?

If a person can move through the page with Tab, the sequence of those stops has to still make sense. A name field, then an email field, then Submit matches how the form is laid out. Tab that jumps from First name to Submit, then back to Email, does not. The W3C explanation is in Understanding Success Criterion 2.4.3. HTML technique H4 and CSS technique C27 both put the interactive elements in an order that follows the sequences in the content, usually by matching DOM order to visual order. Reaching each control from the keyboard is a separate Level A check on the keyboard access page. Seeing which control has focus is a separate Level AA check on the focus visible page.

When does tabindex or CSS order fail 2.4.3?

A positive tabindex value inserts that control into a separate tab sequence before anything at 0. Using those values to force a path that does not match meaning or operability is failure F44. CSS Flexbox or Grid order, floats, and positioning can also put the visual layout out of line with the DOM. If the reading sequence and the tab sequence then diverge, that is failure F85. A skip link that is first in the tab order and then moves focus into the main region still preserves meaning; that pattern is covered on the skip links page. A dialog that holds focus while it is open is 2.1.2, not 2.4.3, and is covered with keyboard traps on the keyboard access page.

How is 2.4.3 different from focus visible and focus not obscured?

2.4.3 is the sequence. 2.4.7 is whether the focused control has a visible indicator. WCAG 2.2 adds 2.4.11 Focus Not Obscured, which is whether a sticky header or cookie banner covers that control entirely. A page can tab in a meaningful order, show a clear ring, and still fail 2.4.11 if a sticky bar hides the focused field. That later criterion is on the focus not obscured page. Title II names WCAG 2.1 Level AA, so it includes 2.4.3 and 2.4.7 and does not include 2.4.11.

Does the Title II web rule include focus order?

Yes. The Department of Justice rule for state and local government websites names WCAG 2.1 Level AA. That level includes Level A criterion 2.4.3. Governments with a population of 50,000 or more have until April 26, 2027. Smaller governments and special districts have until April 26, 2028. Who must comply is on the Title II web rule page. A scanner can flag a positive tabindex. It often cannot tell whether CSS order, a two-column form, or a custom widget sends Tab in a sequence that still makes sense. A person checks that, which is why a passing score is not conformance, as covered on the scanner page. The fix belongs in the templates, which is remediation. To have a specific page reviewed, use the contact form.