react-doctor/role-supports-aria-props

Use only aria-* props that are supported by the element's explicit or implicit ARIA role.

Validation prompt

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

Fires when a JSX element carries a real aria-* property that is not supported by its statically resolved explicit or implicit role. An explicit role wins; otherwise the detector infers from the tag and a few literal attributes. It cannot see roles, href/type values, or aria properties supplied by spreads, and custom components need jsx-a11y component mapping. Before editing, verify the intended semantic owner: an unsupported property may belong on a parent group or controlling element rather than being replaceable on the reported node.

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.

Remove or move the unsupported property without substituting a different meaning merely because the role allows it. For a required custom radio group, put aria-required on the owning radiogroup and keep aria-checked={selected} on each radio because checked state is independently required; aria-checked does not replace aria-required. Move disclosure state to the button that controls the disclosed content, or rely on native <details>/<summary> semantics. Change the role only when the element truly performs the new role's complete interaction contract. See https://oxc.rs/docs/guide/usage/linter/rules/jsx_a11y/role-supports-aria-props

Repository-wide copy prompt

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