`react-doctor/no-invisible-focus-control`

Invisible native control lacks keyboard focus treatment

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-invisible-focus-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

<label className="relative">
  <select className="absolute inset-0 opacity-0">
    <option>UTC</option>
  </select>
  <span>UTC</span>
</label>

Corrected pattern

<label className="relative focus-within:ring-2">
  <select className="absolute inset-0 opacity-0">
    <option>UTC</option>
  </select>
  <span>UTC</span>
</label>

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-invisible-focus-control diagnostic in the current repository. Required change: - Reveal the native control on focus or add a visible focus-within ring to the proxy surface around it.

Reference transformation:Before:

<label className="relative">
  <select className="absolute inset-0 opacity-0">
    <option>UTC</option>
  </select>
  <span>UTC</span>
</label>

After:

<label className="relative focus-within:ring-2">
  <select className="absolute inset-0 opacity-0">
    <option>UTC</option>
  </select>
  <span>UTC</span>
</label>

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-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-multiple-main-landmarks: View contains multiple main landmarks
react-doctor/no-multiple-unlabeled-navigation-landmarks: Repeated navigation landmarks need unique names
react-doctor/no-noninteractive-element-interactions: Move the interaction to a semantic interactive element, or add an interactive role plus keyboard support.

react-doctor/no-invisible-focus-control