2.4.4 Link Purpose (In Context)

What this rule means

WCAG 2.4.4 requires that the purpose of each link can be understood from the link text itself, or from the link text combined with its surrounding context — such as the enclosing paragraph, list item, table cell, or heading. Users must be able to determine where a link will take them before activating it.

This means that link text like "click here", "read more", or "learn more" fails when the surrounding context does not clarify the destination. The purpose must be unambiguous either from the link text alone or with the help of its programmatic context.

Why it matters

Screen reader users frequently navigate by pulling up a list of all links on a page. When every link says "click here" or "read more", that list becomes useless — the user cannot distinguish between links or determine which one to follow. This forces them to navigate to each link individually and read the surrounding text for context, which is extremely time-consuming.

Descriptive link text also benefits sighted users who scan pages visually, users with cognitive disabilities who need clear cues, and search engines that use link text as a ranking signal.

Related axe-core rules

• link-name — Ensures every link has discernible text that describes its purpose.

How to test

1. Use a screen reader to generate a list of links (e.g., NVDA: Insert+F7, VoiceOver: Rotor > Links). Review whether each link's purpose is clear out of context.
2. Run axe-core and check for link-name violations (links without accessible names).
3. Manually review all links with generic text ("click here", "read more", "here", "more") and check whether the programmatic context clarifies their purpose.
4. Check that image links have alt text that describes the link destination, not just the image.

• Verify that links using aria-label or aria-labelledby accurately describe the destination.

How to fix

Write link text that clearly describes the destination or action. When surrounding context is needed, ensure it is programmatically associated.

Descriptive link text

<!-- Bad: Generic link text -->
<p>We published our annual report. <a href="/report">Click here</a>.</p>
<p>Read our accessibility guide. <a href="/guide">Read more</a></p>

<!-- Good: Self-descriptive link text -->
<p><a href="/report">Download the 2025 annual report</a></p>
<p><a href="/guide">Read our complete accessibility guide</a></p>

<!-- Good: Context from enclosing element -->
<li>
  <h3>Accessibility Audit Service</h3>
  <p>We test your site against WCAG 2.2 criteria.
    <a href="/services/audit">Learn more about our audit service</a>
  </p>
</li>

Image links

<!-- Bad: Image link with no alt text -->
<a href="/home"><img src="logo.png"></a>

<!-- Bad: Alt describes image, not link purpose -->
<a href="/home"><img src="logo.png" alt="Company logo"></a>

<!-- Good: Alt describes link destination -->
<a href="/home"><img src="logo.png" alt="Inculva home page"></a>

Using aria-label for enhanced context

<!-- When visual design requires short text like "Read more" -->
<article>
  <h3>WCAG 2.4.4 Explained</h3>
  <p>Understanding link purpose requirements...</p>
  <a href="/articles/244" aria-label="Read more about WCAG 2.4.4 Explained">
    Read more
  </a>
</article>

Common mistakes

• Using "click here", "here", "read more", "learn more", or "more" as the sole link text without additional context.
• Using the raw URL as link text (e.g., "https://www.example.com/report.pdf") instead of a descriptive label.
• Having multiple links on the same page with identical text that lead to different destinations.
• Wrapping an entire paragraph or large block of text in an <a> tag, making the link text overly verbose.
• Image links where the alt text describes the image instead of the link destination.
• Using title attribute as the only means of providing link purpose — title tooltips are inaccessible on touch devices and not consistently read by screen readers.