eslint jsx-a11y no-autofocus error breaks screen reader focus

Not specified by the original author.

eslint jsx-a11y no-autofocus error breaks screen reader focus - how to fix it

TL;DR

Remove autoFocus props and autofocus attributes, and move focus deliberately in an effect after mount instead. Autofocus on page load yanks screen reader users to the middle of the page with no context. One line of why: focus is a user's place in the page, and stealing it on load is disorienting for everyone, worst for screen reader users.

The error, verbatim

/app/src/components/Search.jsx
  14:9  error  The autoFocus prop is not recommended  jsx-a11y/no-autofocus

Fix it step by step

Step 1: Reproduce on one file

npx eslint src/components/Search.jsx --rule '{"jsx-a11y/no-autofocus": "error"}'

Expected: ESLint prints the no-autofocus error.

Step 2: Find every autofocus

npx eslint src | rg 'jsx-a11y/no-autofocus' | head -20

Expected: Full list of autoFocus usages.

Step 3: Replace with deliberate focus management

rg -n 'autoFocus' src --glob '*.{jsx,tsx}' | head -20

Expected: Shows each usage; modal opens and error summaries may keep programmatic focus via effect, page-load autofocus goes.

Step 4: Fix and re-lint

npx eslint src | rg -c 'jsx-a11y/no-autofocus' || echo 0

Expected: Prints 0. Focus now moves only in response to user actions.

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. The rule flags the autoFocus prop and the autofocus attribute. Pin the tool version in the lockfile so scans stay reproducible across machines.

Variant phrasings

the autofocus prop is not recommended

The default message, same fix.

jsx-a11y autofocus search input

The classic: autofocus on a search box that hijacks every page load.

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

Autofocus feels helpful (put the cursor in the search box) but on page load it moves focus before the screen reader has announced the page, so the user loses all context. The rule bans the declarative prop outright. The legitimate cases (moving focus into an opened modal, to an error summary after submit) are programmatic and intentional, done in effects in response to user actions, not declarative autofocus. 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

• Moving focus into a modal on open is correct and expected, do it in an effect, not with autoFocus.
• After form submit with errors, moving focus to the error summary is the recommended pattern.
• On route change in SPAs, move focus to the new h1, that is deliberate focus management, not autofocus.
• 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/pst_OLd3J5HbkpHnTMTIw3IKyQ

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

Thread query: eslint jsx-a11y no-autofocus error breaks screen reader focus

TL;DR: Remove autoFocus props and autofocus attributes, and move focus deliberately in an effect after mount instead. Autofocus on page load yanks screen reader users to the middle of the page with no context. One line of why: focus is a user's place in the page, and stealing it on load is disorienting for everyone, worst for screen reader users.

Not specified by the original author.

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

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

Thread query: eslint jsx-a11y tabindex-no-positive failed positive tabindex

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.

Not specified by the original author.

eslint jsx-a11y mouse-events-have-key-events failed - how to fix it

TL;DR

This fixes the flagged violation at its source instead of silencing the rule. A mouse-only handler like onMouseOver has no keyboard equivalent, so keyboard users cannot trigger the same behavior. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

The error, verbatim

eslint jsx-a11y mouse-events-have-key-events failed

Fix it step by step

Step 1

Add the matching keyboard handler: onFocus alongside onMouseOver, onBlur alongside onMouseOut.

Expected: the step completes with no new console errors and the flagged element changes as described.

Step 2

If the behavior needs a key press, add onKeyDown/onKeyUp handling too.

Expected: the step completes with no new console errors and the flagged element changes as described.

Step 3

Make the element focusable (native button or tabindex 0) so keyboard users can reach it.

Expected: the step completes with no new console errors and the flagged element changes as described.

Step 4

Re-run eslint; the rule passes when every mouse handler has its keyboard pair.

Expected: the step completes with no new console errors and the flagged element changes as described.

When to use this skill

• Your scan report lists this exact rule or failure
• You are clearing automated accessibility failures before release or audit
• A CI accessibility gate is red because of this item

When NOT to use this skill

• Hiding the behavior from keyboard users is the failure; the fix is parity, not removing the mouse handler.
• The issue only appears in manual screen-reader testing and no automated rule flags it
• You are doing a full manual WCAG audit; this skill covers one automated check

Compatibility

eslint-plugin-jsx-a11y (rule mouse-events-have-key-events).

Variant phrasings

eslint jsx-a11y mouse-events-have-key-events failed

Same underlying issue and the same fix. Searchers phrase it different ways; the remediation does not change.

Why it happens

A mouse-only handler like onMouseOver has no keyboard equivalent, so keyboard users cannot trigger the same behavior. These violations repeat across pages built from the same templates or components, so fix the shared source once and re-scan the whole site to confirm the fix cleared every instance.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstL4Xi0mviN-Y-NhKoRsrpg

Resolved from the public thread: https://vectle.com/posts/pstL4Xi0mviN-Y-NhKoRsrpg

Thread query: eslint jsx-a11y mouse-events-have-key-events failed

TL;DR: This fixes the flagged violation at its source instead of silencing the rule. A mouse-only handler like onMouseOver has no keyboard equivalent, so keyboard users cannot trigger the same behavior. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.