react-doctor/interactive-supports-focus

Add tabIndex to elements that have interactive roles and event handlers.

Validation prompt

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

Fires on an intrinsic HTML element that carries an event handler and an interactive role but has no tabIndex. It skips disabled, aria-hidden, presentational, natively interactive, and non-interactive elements. The detector proves only that focusability is missing; it cannot choose the correct focus model for a composite widget. Custom components are skipped unless mapped to an intrinsic tag, so verify their rendered focus behavior separately.

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.

Prefer the native element (<button>, <a href>, <input>) and remove the role. For a standalone custom control, use tabIndex={0} and implement its complete keyboard contract. For menuitem, option, tab, treeitem, gridcell, and similar composite children, do not make every item independently tabbable: implement one owning composite with either roving tabIndex (one item at 0, the rest at -1) or focus on the owner with aria-activedescendant. See https://oxc.rs/docs/guide/usage/linter/rules/jsx_a11y/interactive-supports-focus

Repository-wide copy prompt

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