WCAG 2.4.3 · Level A
Tabindex
- What is broken
- Positive tabindex values override the natural tab order, sending focus around the page unpredictably.
- Who it affects
- Anyone navigating by keyboard, including screen reader and switch users, can get stuck or lose their place.
- How to fix it
- Remove tabindex values greater than zero and let document order define the sequence.
Check your site for this issue
Free scan — no signup required. Covers WCAG 2.1 AA across 64 rules including this one.
Scan my site →Automated testing detects roughly a third of WCAG 2.1 success criteria. This rule is detected automatically; issues such as keyboard traps, focus order, and screen-reader flow still require manual review. Not legal advice.