react-doctor/no-access-key

Don't use `accessKey`: it conflicts with assistive-technology shortcuts.

Validation prompt

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

Fires on any JSX element carrying an accessKey attribute (matched case-insensitively, so accesskey and acCesSKeY count) whose value is a string literal (accessKey="h"), a non-empty expression container (accessKey={accessKey}, accessKey={"y"}), or any template literal: even one that only interpolates undefined like accessKey={${undefined}} . The only carve-outs are the bare undefined identifier (accessKey={undefined}), an empty expression container {}, and a value-less attribute.

Suppress when: there is essentially none: every value-bearing accessKey genuinely creates the conflict, so confirm unless the value provably resolves to undefined at runtime, which the static check can't see through a variable.

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 the accessKey attribute entirely: <button accessKey="s">Save</button> becomes <button>Save</button>. Author-assigned access keys collide with screen-reader and OS-level keyboard shortcuts, so there is no safe value to keep; if a keyboard shortcut is genuinely required, implement it with a documented, user-discoverable handler instead of accessKey. See https://oxc.rs/docs/guide/usage/linter/rules/jsx_a11y/no-access-key

Repository-wide copy prompt

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