Ambiguous Link Text
What is this issue?
Ambiguous link text refers to links whose text does not describe their destination or purpose. Common examples include "Click here", "Read more", "Learn more", "More", "Here", and "This". WCAG Success Criterion 2.4.4 (Level A) requires that the purpose of each link can be determined from the link text alone, or from the link text together with its programmatically determined context.
When a page contains five "Read more" links, a sighted user can glance at the surrounding content to understand what each link refers to. But a screen reader user who pulls up a list of all links on the page -- a common navigation strategy -- sees five identical "Read more" entries with no way to distinguish them. This defeats one of the most efficient navigation methods available to assistive technology users.
The problem extends to links that use URLs as their text ("Visit https://example.com/page/12345"), icon-only links without accessible names, and links whose text describes the mechanics of clicking rather than the destination ("Click here to download the annual report" instead of simply "Download the annual report").
Impact on users
Screen reader users frequently navigate by pulling up a list of all links on a page. NVDA and JAWS both provide this feature, and it allows users to quickly scan available actions and destinations. When every link says "Read more" or "Click here", this list becomes useless -- the user must visit each link's surrounding context individually, a slow and tedious process.
Voice control users are also affected. To activate a link by voice, they need to speak its text. If multiple links share the same text, the voice control software must present a disambiguation dialog, adding friction to every interaction.
Ambiguous link text also hurts SEO. Search engines use link text (anchor text) to understand the content of the linked page. "Click here" provides no information about the destination, while descriptive link text like "View our accessibility audit pricing" directly boosts the linked page's relevance for those keywords.
Code example
<p>We offer accessibility audits.
<a href="/audits">Click here</a></p>
<article>
<h3>WCAG 2.1 Compliance Guide</h3>
<p>Everything you need to know...</p>
<a href="/blog/wcag-guide">Read more</a>
</article>
<a href="/report.pdf">
<img src="/icons/download.svg">
</a><p>We offer
<a href="/audits">accessibility audit services</a>.</p>
<article>
<h3>WCAG 2.1 Compliance Guide</h3>
<p>Everything you need to know...</p>
<a href="/blog/wcag-guide">
Read the full WCAG 2.1 compliance guide
</a>
</article>
<a href="/report.pdf"
aria-label="Download accessibility report (PDF)">
<img src="/icons/download.svg" alt="">
</a>How Scrutia detects this issue
Scrutia scans every link on your site and flags those whose text matches known ambiguous patterns such as "Click here", "Read more", "Learn more", and "More". It also detects duplicate link text pointing to different destinations, links with no accessible name (icon-only links without aria-label), and links whose text is a raw URL. Each finding includes the link location and a suggested descriptive replacement.
Check your site for this issue
Scrutia audits your site against WCAG criteria in minutes.
Frequently Asked Questions
Is "Learn more" always bad link text?
How do I fix icon-only links?
Can I use aria-label to fix ambiguous link text?
Does link text affect SEO?
Does your site have this issue?
Scrutia scans your pages against WCAG success criteria and delivers actionable fixes. Results in 5 minutes.
Run a free audit