react-doctor/prefer-tag-over-role

Replace role with the semantic HTML element when one exists.

Validation prompt

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

Fires only on a generic <div> or <span> (after JSX-element-type resolution) that carries a static role string which maps to at least one built-in HTML element with that implicit ARIA role: e.g. <div role="button">, <span role="navigation">, <div role="list">. Roles with no semantic equivalent (role="unknown", role="tablist") and roles applied to non-generic tags (<header role="banner">, <ul role="list">) never fire. False positive / non-trigger: a dynamically computed role like role={someVar} or role={cond ? "button" : "link"} is skipped because the static check can't read a non-literal value, so don't expect those to be flagged.

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.

Swap the generic element for the native tag that carries the role implicitly and drop the now-redundant role: <div role="button"> becomes <button>, <span role="navigation"> becomes <nav>. When a role maps to multiple tags the rule suggests only the first match in its internal table, so <div role="list"> becomes <menu> (not <ul>): review the suggestion and substitute the contextually correct element if another fits better. Native elements bring built-in keyboard, focus, and semantics that a role alone does not, so reach for the real element rather than reintroducing ARIA. See https://oxc.rs/docs/guide/usage/linter/rules/jsx_a11y/prefer-tag-over-role

Repository-wide copy prompt

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