Accessibility Wiki

Link text should describe its destination

Rule link-generic-text · Links & buttons · impact minor · Static + live

↩ Back to the rules index · WCAG cross-reference

Why it matters

Screen-reader users often pull up a list of links out of context. Generic text ("click here", "read more") gives that list no meaning. 2.4.4 is Link Purpose (In Context): a generic link whose list item, table cell, or paragraph carries a heading or other text is programmatically disambiguated and conforms — only context-less generic links are flagged.

How to fix

Make the link text describe the destination, or extend it with visually-hidden text / aria-label. Alternatively, place the link in a list item/cell/paragraph whose heading or text identifies the destination.

Example

✕ Fails
<a href="/pricing">click here</a>
✓ Passes
<a href="/pricing">See our pricing</a>

Example

✕ Fails
<a href="/post">Read more »</a>
✓ Passes
<a href="/post">Read more about pricing »</a>

Example

✕ Fails
<p><a href="/post">Read more »</a></p>
✓ Passes
<li><h3>Pricing</h3><p>Plans start at $5/month.</p><a href="/pricing">Read more</a></li>

The list item's heading is the link's programmatic context (2.4.4 In Context), so the generic text is disambiguated.

WCAG success criteria

The purpose of each link should be clear from its text (or its programmatically-associated context).

Understanding 2.4.4

Standards

This rule contributes to the following standards:

WCAG A EN 301 549

Standard Criteria
EN 301 549 9.2.4.4

References