react-doctor/anchor-has-content
Add visible or aria-labelled text inside every `<a>`.
- 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
- 42 (P3)
- Source
- oxlint-plugin-react-doctor
- Rule set
- oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
- Documentation
- Official documentation
Validation prompt
Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.
Fires on an <a> element (or a component mapped to a via the jsx-a11y components setting) that has no non-empty text child, non-hidden JSX-element child, dangerouslySetInnerHTML/children prop, title, or aria-label. Expression children that are literally null or undefined do not count, and a child whose only element is aria-hidden is treated as absent. Detector limitation: title passes even though it is not a reliable sole accessible name, while a valid aria-labelledby reference is still reported despite providing an accessible name.
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.
Prefer visible link text (<a href="/docs">Documentation</a>). For an icon-only link, use a stable accessible name such as <a href="/settings" aria-label="Open settings"><Icon aria-hidden /></a>. Do not use title as the sole name. If a valid aria-labelledby already names the link, preserve that relationship rather than changing the accessible name merely to satisfy this detector; update the detector or its configuration to recognize the valid pattern. See https://oxc.rs/docs/guide/usage/linter/rules/jsx_a11y/anchor-has-content
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/anchor-has-content diagnostic in the current repository.
Required change:
- Prefer visible link text (
<a href="/docs">Documentation</a>). For an icon-only link, use a stable accessible name such as<a href="/settings" aria-label="Open settings"><Icon aria-hidden /></a>. Do not usetitleas the sole name. If a validaria-labelledbyalready names the link, preserve that relationship rather than changing the accessible name merely to satisfy this detector; update the detector or its configuration to recognize the valid pattern. See https://oxc.rs/docs/guide/usage/linter/rules/jsx_a11y/anchor-has-content.
Validation before editing:
Fires on an <a> element (or a component mapped to a via the jsx-a11y components setting) that has no non-empty text child, non-hidden JSX-element child, dangerouslySetInnerHTML/children prop, title, or aria-label. Expression children that are literally null or undefined do not count, and a child whose only element is aria-hidden is treated as absent. Detector limitation: title passes even though it is not a reliable sole accessible name, while a valid aria-labelledby reference is still reported despite providing an accessible name.
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.