W3C WCAG 2.4.3 Focus Order (Level A)
Focusable components must receive focus in an order that preserves meaning and operability when navigated sequentially
Where this comes from
Provision: 2.4.3 Focus Order (Level A)
Instrument: W3C Web Content Accessibility Guidelines (WCAG) 2.2
Citation: W3C, Web Content Accessibility Guidelines (WCAG) 2.2, Success Criterion 2.4.3 Focus Order, Level A, W3C Recommendation 05 October 2023
Text version: WCAG 2.2
Who it applies to
It applies when all of these are true:
- Service type — any answer
- Service is likely to be accessed by children under 18
What engineering work it implies
Sample acceptance criteria Landfall generates for this obligation:
- Interactive elements are keyboard-operable and have visible focus
- Content and controls expose correct names/roles/values to assistive tech (ARIA where needed)
- Color contrast and text alternatives meet the referenced criterion
- Errors are identified in text and programmatically associated with their input
- Automated accessibility scan (axe/Lighthouse) passes for the changed views
Questions people ask
- Does W3C WCAG 2.4.3 Focus Order (Level A) apply to my service?
- It applies when Service type — any answer; Service is likely to be accessed by children under 18.
- From when does this apply?
- W3C WCAG 2.4.3 Focus Order (Level A) applies from 5 October 2023. Its current status is: in force.
Find out whether this one lands on you
Landfall's pre-scan answers the applicability question above for your product in minutes, then turns every obligation that applies into traceable engineering tickets with a citation chain your auditors can follow.
Not legal advice. Landfall maps regulatory obligations to engineering work for planning purposes. Its verdicts are not legal advice and create no attorney-client relationship — verify with qualified counsel before relying on them.