eslint jsx-a11y tabindex-no-positive failed positive tabindex

eslint jsx-a11y tabindex-no-positive failed positive tabindex - how to fix it

TL;DR

Replace every positive tabindex with 0, -1, or a DOM reorder: positive values hijack the tab order into an explicit sequence that breaks the moment markup changes. One line of why: tab order should follow DOM order, and positive tabindex creates a fragile parallel order that assistive tech and keyboards experience differently.

The error, verbatim

/app/src/components/Modal.jsx
  30:9  error  Avoid positive integer values for tabIndex  jsx-a11y/tabindex-no-positive

Fix it step by step

Step 1: Reproduce on one file

npx eslint src/components/Modal.jsx --rule '{"jsx-a11y/tabindex-no-positive": "error"}'

Expected: ESLint prints the tabindex-no-positive error.

Step 2: Find every positive tabindex

npx eslint src | rg 'tabindex-no-positive' | head -20

Expected: Full list of positive tabIndex usages.

Step 3: Convert each one

rg -n 'tabIndex=.?[1-9]|tabindex=.?[1-9]' src --glob '*.{jsx,tsx,vue,html}' | head -20

Expected: Shows the exact lines to change to 0, -1, or a DOM reorder.

Step 4: Fix and re-lint

npx eslint src | rg -c 'tabindex-no-positive' || echo 0

Expected: Prints 0. Tab order now follows the DOM, which matches the visual order.

Step 5: Enforce it in CI

npx eslint src --max-warnings 0 | tail -3

Expected: Clean output; add the lint command to CI with max-warnings 0 so the violation cannot come back.

When to use this skill

• Your linter output names this exact jsx-a11y / a11y rule
• You want the violation fixed at author time so it never reaches axe or CI
• You are adding the rule to a shared eslint config and need the fix pattern

When NOT to use this skill

• The failure comes from axe-core or lighthouse at runtime, not from lint
• You plan to disable the rule project-wide, this skill shows the fix, not the escape hatch

Compatibility

eslint-plugin-jsx-a11y 6.7+ with eslint 8 or 9. Zero config needed, the rule is a simple ban. Pin the tool version in the lockfile so scans stay reproducible across machines.

Variant phrasings

avoid positive integer values for tabindex

The default message, same fix.

jsx-a11y tabindex 1 2 3

The classic anti-pattern: tabIndex 1, 2, 3 sprinkled to force an order.

the rule fires in the editor too

With the eslint extension installed, the same error appears inline while typing; the fix is identical.

Why it happens

Authors use positive tabindex to force a tab order instead of fixing the DOM order, usually tabIndex 1 on the primary action. It works until anyone adds, removes, or reorders elements, and then the explicit sequence silently diverges from the visual layout. The rule is a flat ban: no positive integers, ever. tabIndex 0 (in natural order) and -1 (focusable programmatically only) cover every legitimate need. Linter rules catch the violation at author time, which is cheaper than any runtime fix. When this rule fires across many files, fix the shared component and mention it in team onboarding so new code does not reintroduce it.

Edge cases

• tabIndex={-1} is for programmatic focus (modals, error summaries), not for removing things from tab order permanently.
• Do not use tabIndex 0 to make a div focusable as a substitute for a button, that trips other rules.
• Third-party widgets with positive tabindex need a post-render cleanup or a vendor fix.
• After fixing, run the whole lint suite once; a11y rules interact and one fix can surface the next violation.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstMnXPpgtkHgDh4fawdKuZA