New
Introducing React Bench, see how different models perform on React code

react-doctor/no-aria-hidden-on-focusable

Remove `aria-hidden` from focusable elements (or remove the focusability).

Status
Active
Category
Accessibility
Assessment
Evidence-required risk
Required evidence
source code, rendered UI, accessibility audit
Default configuration
Enabled
Default severity
warn
Show technical metadata
Scope
All supported frameworks
Active when
always
Requirements
react
Tags
react-jsx-only
Priority
46 (P3)
Source
oxlint-plugin-react-doctor
Rule set
oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
On this page

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

Reports a bare or statically true aria-hidden on an element the detector considers focusable. Dynamic values are skipped. Spreads and click-only noninteractive elements can escape the static check, so verify actual reachability and hidden state in the rendered interface.

Evidence boundary

The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

Record one outcome:

  • Confirmed failure: The required evidence establishes the violation.
  • Rejected: A documented exception or false-positive predicate applies.
  • Needs evidence: Named evidence can still be collected.
  • Unavailable: Required evidence cannot be collected in this run.
  • Waived with evidence: An authorized, scoped exception applies to an established failure.
  • Observation: The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.

Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

If the control stays reachable, remove aria-hidden. If the owning subtree is inactive, unmount it or use hidden or inert; disabled may fit a form control. Do not use tabIndex={-1} as the sole fix because pointer and programmatic focus can remain.

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.

Show repository-wide prompt

Fix every confirmed react-doctor/no-aria-hidden-on-focusable diagnostic in the current repository.

Required change:

  • If the control stays reachable, remove aria-hidden. If the owning subtree is inactive, unmount it or use hidden or inert; disabled may fit a form control. Do not use tabIndex={-1} as the sole fix because pointer and programmatic focus can remain.

Validation before editing:

Reports a bare or statically true aria-hidden on an element the detector considers focusable. Dynamic values are skipped. Spreads and click-only noninteractive elements can escape the static check, so verify actual reachability and hidden state in the rendered interface.

Constraints:

  • Make the smallest change that fixes the root cause.
  • Preserve behavior and interfaces unrelated to this diagnostic.
  • Reuse existing project components, utilities, and conventions.
  • Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations.
  • Preserve accessible names, focus order, keyboard behavior, and touch access not targeted by this rule.
  • Adapt identifiers and framework details instead of copying blindly.
  • Do not disable the rule or suppress matching code.

Assessment:

  • Record detector evidence, applicability facts, assumptions, missing evidence, and the rule class for this occurrence.
  • Return one outcome: Confirmed failure, Rejected, Needs evidence, Unavailable, Waived with evidence, or Observation.
  • A waiver records the established failure, scope, authority, evidence, and review or expiry condition. It is not a pass or false positive.

Verification:

  • Run focused tests for the changed behavior.
  • Run React Doctor and confirm this diagnostic no longer appears from changed code.
  • Run an unfiltered scan of the affected scope before claiming no cross-category regression.
  • Report the files changed and any checks you could not run.