react-doctor/no-pointer-disabled-enabled-control
Enabled control ignores pointer input
- Category: Accessibility
- Severity: warn
- Source:
oxlint-plugin-react-doctor - Framework: global
- Enabled when: always
- Tags: design
- 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-pointer-disabled-enabled-control. 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
<button className="pointer-events-none" onClick={save}>Save</button>Corrected pattern
<button onClick={save}>Save</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
Reference transformation:Before:react-doctor/no-pointer-disabled-enabled-control diagnostic in the current repository.
Required change:
- Remove pointer-events: none from enabled controls so mouse and touch users can operate them, or mark the control unavailable with native disabled semantics.<button className="pointer-events-none" onClick={save}>Save</button><button onClick={save}>Save</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.
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.
Related rules
More Accessibility rules from the rules reference:
react-doctor/no-presentation-role-conflict: Presentational element exposes conflicting semanticsreact-doctor/no-reduced-motion-content-removal: Reduced motion removes meaningful contentreact-doctor/no-redundant-roles: Disallow role attributes that duplicate an element's implicit ARIA role, like <button role='button'>.react-doctor/no-responsive-hidden-accessible-name: Responsive styles hide a control's accessible namereact-doctor/no-server-side-image-map: Server-side image map