`react-doctor/no-inert-pointer-affordance`

Pointer cursor has no interaction

Category: Accessibility
Severity: warn
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: tailwind
Tags: design, test-noise, react-jsx-only
Default: Disabled until configured

Validate the diagnostic

Confirm the reported code matches this rule before you edit it.

Confirm the reported code matches react-doctor/no-inert-pointer-affordance. Compare it with the Before example and verify the same API, framework, and execution context. Treat it as a false positive only when one of those conditions differs.

Compare the code

The corrected pattern shows a focused way to address the diagnostic.

Reported pattern

<div className="cursor-pointer">Project summary</div>

Corrected pattern

<button type="button" onClick={openSummary}>Project summary</button>

How to fix

Use the corrected pattern as a reference. Preserve behavior that the rule does not require you to change.

Copyable fix prompt

Copy this self-contained prompt into your coding agent after you confirm the diagnostic.

Fix every confirmed react-doctor/no-inert-pointer-affordance diagnostic in the current repository. Required change: - Remove the pointer cursor or put the affordance on the control that actually handles the interaction.

Reference transformation:Before:

<div className="cursor-pointer">Project summary</div>

After:

<button type="button" onClick={openSummary}>Project summary</button>

Constraints: - Confirm the reported code matches the Before pattern. - Make the smallest change that fixes the root cause. - Preserve behavior and interfaces unrelated to this diagnostic. - Reuse existing project components, utilities, and conventions. - Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations. - Use existing brand assets, product facts, content, and design tokens. - Do not invent claims, customer data, typefaces, or artwork. - Preserve accessible names, focus order, keyboard behavior, and touch access not targeted by this rule. - Adapt identifiers and framework details instead of copying blindly. - Do not disable the rule or suppress matching code. - Confirm this rule is enabled for the project: tailwind. Verification: - Run focused tests for the changed behavior. - Run React Doctor and confirm this diagnostic no longer appears. - Report the files changed and any checks you could not run.

More Accessibility rules from the rules reference:

react-doctor/no-interactive-element-to-noninteractive-role: Don't override an interactive element's semantics with a non-interactive role.
react-doctor/no-invalid-progress-range: Progress value falls outside its range
react-doctor/no-invisible-focus-control: Invisible native control lacks keyboard focus treatment
react-doctor/no-justified-text: Use `text-align: left` for body text, or add `hyphens: auto` and `overflow-wrap: break-word` if you must justify
react-doctor/no-low-contrast-inline-style: Low-contrast text in inline style

react-doctor/no-inert-pointer-affordance