react-doctor/anchor-ambiguous-text

Describe a link's destination: avoid bare 'click here' / 'learn more' / 'link' as the only link text.

Validation prompt

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

Fires when an element resolving to tag a has an accessible name that, after lowercasing, stripping ,.?¿!‽¡;:, and collapsing whitespace, EXACTLY equals one of the ambiguous phrases: by default "click here", "here", "link", "a link", "learn more" (configurable via the words setting). The detector prefers aria-label, then a child image alt, then visible child text. False-negative boundary: a descriptive aria-label suppresses the diagnostic even when it omits the visible words, which can violate Label in Name and break speech targeting; matching is also exact, so "click here for details" never fires.

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 replacing the visible phrase with text that names the destination, e.g. <a href="/pricing">View pricing details</a> instead of <a href="/pricing">click here</a>. If product requirements keep the generic visible words, make the accessible name include them, such as <a aria-label="Learn more about the setup guide">Learn more</a>; do not replace a visible label with an unrelated aria-label. See https://oxc.rs/docs/guide/usage/linter/rules/jsx_a11y/anchor-ambiguous-text

Repository-wide copy prompt

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