react-doctor/no-noninteractive-element-interactions

Move the interaction to a semantic interactive element, or add an interactive role plus keyboard support.

Validation prompt

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

Fires on a JSX element whose resolved tag is a semantic non-interactive HTML element (img, li, ul, ol, article, section, figure, form, label, headings, etc.: not the generic div/span) that carries a mouse or keyboard handler: onClick, onMouseDown, onMouseUp, onKeyDown, onKeyPress, or onKeyUp (case-insensitive). It is suppressed only when a role prop resolves to a static interactive-role string (button, link, menuitem, checkbox, tab, slider, etc.).

Suppress when: a role whose value comes from a dynamic expression (role={isLink ? 'link' : 'button'}) can't be statically read, so the element is flagged even though it is correctly interactive at runtime.

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.

Move the handler onto a semantic interactive element instead of the content element: replace <li onClick={open}>…</li> with <li><button onClick={open}>…</button></li>, or use an <a> for navigation. If the element must stay non-interactive in markup, give it a literal interactive role plus keyboard support and focusability (role="button" tabIndex={0} onKeyDown={…}) so assistive tech can operate it. When role is already interactive but set via an expression, hoist it to a static string literal so the rule can verify it. See https://oxc.rs/docs/guide/usage/linter/rules/jsx_a11y/no-noninteractive-element-interactions

Repository-wide copy prompt

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