WCAG 2.4.4 Link Purpose: How to Fix Ambiguous Link Text

Last updated: 2026-03-22

Level A Operable WCAG 2.4.4

What This Criterion Requires

WCAG 2.4.4 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 link context (such as the surrounding paragraph, list item, table cell, or heading). Generic link text like 'click here', 'read more', or 'learn more' fails this criterion when the context does not make the destination clear. Screen reader users often navigate by pulling up a list of all links on a page, and in that context, multiple 'Read more' links are indistinguishable from one another. Links should describe their destination or purpose clearly. When brevity is needed, aria-label or aria-labelledby can provide an expanded accessible name while keeping the visible text concise. Image links must derive their purpose from the image's alt text. This criterion applies to all anchor elements, area elements in image maps, and any element with a link role.

Why It Matters

Links are the primary navigation mechanism on the web, and their text communicates critical wayfinding information. Screen reader users frequently use a shortcut to list all links on a page, which strips away all surrounding visual context. In this view, a page with five 'Read more' links is completely unusable because there is no way to tell which article each link refers to. Ambiguous link text also affects people with cognitive disabilities who may struggle to infer meaning from context, voice control users who need to speak the link text to activate it, and anyone scanning a page quickly for relevant content. Clear, descriptive link text benefits everyone by reducing the cognitive effort needed to decide whether to follow a link. It also improves SEO because search engines use link text as a relevance signal for the destination page. Writing good link text is low effort, requires no technical skill, and dramatically improves the experience for assistive technology users.

Common Failures and How to Fix Them

Generic 'Read more' or 'Click here' link text

Multiple links on a page use identical generic text like 'Read more' or 'Click here' without programmatic context to differentiate them. Screen reader link lists become a wall of identical, meaningless items.

Inaccessible 
<article>
  <h3>Accessibility in Healthcare</h3>
  <p>Healthcare websites must be accessible...</p>
  <a href="/blog/healthcare-a11y">Read more</a>
</article>
<article>
  <h3>E-commerce Accessibility</h3>
  <p>Online stores need to be accessible...</p>
  <a href="/blog/ecommerce-a11y">Read more</a>
</article>
Accessible 
<article>
  <h3>Accessibility in Healthcare</h3>
  <p>Healthcare websites must be accessible...</p>
  <a href="/blog/healthcare-a11y">Read more<span class="sr-only"> about Accessibility in Healthcare</span></a>
</article>
<article>
  <h3>E-commerce Accessibility</h3>
  <p>Online stores need to be accessible...</p>
  <a href="/blog/ecommerce-a11y">Read more<span class="sr-only"> about E-commerce Accessibility</span></a>
</article>

Image link with missing or empty alt text

A linked image has no alt text, so the link has no accessible name. Screen readers may announce the URL or filename, which is not helpful.

Inaccessible 
<a href="/products/widget">
  <img src="/images/widget-thumbnail.jpg">
</a>
Accessible 
<a href="/products/widget">
  <img src="/images/widget-thumbnail.jpg" alt="Widget Pro - View product details">
</a>

URL used as link text

The raw URL is used as the link text, which is difficult to parse and unhelpful for understanding the link's purpose.

Inaccessible 
<a href="https://www.example.com/resources/guides/web-accessibility-compliance-2025">
  https://www.example.com/resources/guides/web-accessibility-compliance-2025
</a>
Accessible 
<a href="https://www.example.com/resources/guides/web-accessibility-compliance-2025">
  Web Accessibility Compliance Guide 2025
</a>

How to Test

  1. Use a screen reader to pull up the links list (Insert+F7 in JAWS, NVDA+F7 in NVDA, VO+U in VoiceOver) and verify that every link's purpose is clear without surrounding context.
  2. Search the page for common generic phrases ('click here', 'read more', 'learn more', 'more', 'here') and verify each instance has sufficient programmatic context.
  3. Check that all image links have descriptive alt text that communicates the link destination.
  4. Run axe DevTools or WAVE which flag empty links, links with generic text, and image links without alt text.

CMS-Specific Guidance

This criterion commonly causes issues on these platforms:

Further Reading

Related WCAG Criteria