New
Introducing React Bench, see how different models perform on React code

react-doctor/control-has-associated-label

Give every interactive control an accessible label via visible text, aria-label, aria-labelledby, or an associated label.

Status
Active
Category
Accessibility
Assessment
Evidence-required risk
Required evidence
source code, rendered UI, accessibility audit
Default configuration
Enabled
Default severity
warn
Show technical metadata
Scope
All supported frameworks
Active when
always
Requirements
react
Tags
react-jsx-only
Priority
54 (P2)
Source
oxlint-plugin-react-doctor
Rule set
oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
On this page

Validation prompt

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

Fires on interactive elements except the detector's non-operable set (td, th, tr, option, datalist, audio, and video), plus elements with static interactive roles and configured control components. Static label signals include a native title, supported placeholder, labelling prop or spread, visible or expression child, wrapping label, or matching htmlFor and id. These signals do not prove a good accessible name; verify the rendered accessibility tree.

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.

Give the control a persistent accessible name. Prefer visible text or an associated <label>; use aria-label for a truly icon-only control. A native title may satisfy this detector but is a weak sole name. Verify name, role, state, and value in the rendered accessibility tree.

Repository-wide copy prompt

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

Show repository-wide prompt

Fix every confirmed react-doctor/control-has-associated-label diagnostic in the current repository.

Required change:

  • Give the control a persistent accessible name. Prefer visible text or an associated <label>; use aria-label for a truly icon-only control. A native title may satisfy this detector but is a weak sole name. Verify name, role, state, and value in the rendered accessibility tree.

Validation before editing:

Fires on interactive elements except the detector's non-operable set (td, th, tr, option, datalist, audio, and video), plus elements with static interactive roles and configured control components. Static label signals include a native title, supported placeholder, labelling prop or spread, visible or expression child, wrapping label, or matching htmlFor and id. These signals do not prove a good accessible name; verify the rendered accessibility tree.

Constraints:

  • 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.
  • 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.

Assessment:

  • Record detector evidence, applicability facts, assumptions, missing evidence, and the rule class for this occurrence.
  • Return one outcome: Confirmed failure, Rejected, Needs evidence, Unavailable, Waived with evidence, or Observation.
  • A waiver records the established failure, scope, authority, evidence, and review or expiry condition. It is not a pass or false positive.

Verification:

  • Run focused tests for the changed behavior.
  • Run React Doctor and confirm this diagnostic no longer appears from changed code.
  • Run an unfiltered scan of the affected scope before claiming no cross-category regression.
  • Report the files changed and any checks you could not run.