WCAG 2.4.4 — Link Purpose (In Context), explained with examples

Why this criterion exists

Screen readers can list every link on a page. "Click here", "Read more", and "Learn more" become identical entries with no distinguishing information.

If you only remember one thing: the purpose of every link must be clear from its link text, or from its text combined with the surrounding context. Everything else on this page is detail.

Who feels it when this fails

Accessibility criteria sometimes feel abstract until you see who pays the cost when a site ignores them. Link Purpose (In Context) affects:

• Screen reader users navigating by link list

• Voice control users selecting links by text

How sites typically fail it

These are the patterns we see week after week. None are intentional — they are accidents of how teams build interfaces under deadline. Knowing the failure modes is the fastest path to writing them out of your component library.

• "Click here" / "Read more" without context

• Icon-only links without aria-label

• Different links sharing the same text but different destinations

How to test for it

• List all links with a screen reader; each should make sense in isolation.

A code fix you can copy

Move the meaningful text into the link, or extend it visually-hidden text for the screen reader.

<p>Read about our pricing. <a href="/pricing">Read more</a>.</p>

<p><a href="/pricing">Read about our pricing</a>.</p>
<!-- Or, when "Read more" must remain visually: -->
<a href="/pricing">Read more <span class="sr-only">about pricing</span></a>

Other Operable criteria