axe-core rule: tabindex
Elements force a custom keyboard tab order
What it is
Elements use tabindex values greater than zero, which overrides the natural tab order and forces keyboard focus to jump around the page unpredictably.
Who it blocks
Keyboard-only users and screen reader users, for whom focus jumps to unexpected places, skipping content or visiting it out of reading order.
How to fix it
Remove positive tabindex values. Use tabindex="0" to make a custom element focusable in natural order and tabindex="-1" for programmatic focus only. If the visual order is wrong, fix the DOM order instead.
Example fix
<!-- Before -->
<input tabindex="3" name="email">
<input tabindex="1" name="name">
<!-- After: order the DOM correctly and drop tabindex -->
<input name="name">
<input name="email">This is one of the barrier types BarrierScan checks for on every scan. Request a free accessibility scan to see whether it appears on your site, alongside the rest of the automated findings.