Skip to main content
Ihr Browser ist zu alt, um diese Website korrekt anzuzeigen. Bitte aktualisieren Sie auf die neueste Version von Chrome, Edge, Firefox oder Safari.
Back to WCAG Database
Level AAAWCAG 2.0

2.4.9 Link Purpose (Link Only)

A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose would be ambiguous to users in general.

Last reviewed: September 9, 2026

Understanding 2.4.9

This is a stricter version of 2.4.4: instead of allowing surrounding context to supply meaning, the link's own accessible text must be enough on its own. This matters most for screen reader users who use the 'links list' feature to jump directly between links without reading surrounding content, and for braille display or switch-access users who may only ever encounter the link text in isolation.

How to Meet It

Write link text (including any visually hidden text or `aria-label` that forms part of the accessible name) that fully identifies the link's destination or purpose without depending on the surrounding paragraph, list, or table. Visually hidden supplementary text is an acceptable technique here because it becomes part of the link's accessible name, and therefore part of the 'link text' the criterion refers to, even though sighted users only see the shorter visible portion.

Code Examples

INCORRECT
<p>Our Q3 earnings report is now available.</p>
<a href="/reports/q3-2026.pdf">Read more</a>
CORRECT
<a href="/reports/q3-2026.pdf">Download the Q3 2026 earnings report (PDF, 2.1MB)</a>

Frequently Asked Questions

If I already satisfy 2.4.4 using surrounding context, do I automatically satisfy 2.4.9 too?

Not necessarily. 2.4.4 allows the accessible name plus programmatic context (like the enclosing paragraph) to jointly convey purpose; 2.4.9 requires the accessible name alone to do so. A 'Read more' link that only makes sense next to its article summary passes 2.4.4 but fails 2.4.9 unless you also add link-specific text via visually hidden content or aria-label.

Does adding a visually-hidden span inside the link count as 'link text alone' for this AAA criterion?

Yes. The criterion is concerned with the programmatically determined link text, i.e. the accessible name, which includes visually hidden text nested inside the link or supplied via aria-label/aria-labelledby. It does not require the visible text alone to be sufficient, only the full accessible name.

Related Success Criteria

2.4.1 Bypass Blocks2.4.2 Page Titled2.4.3 Focus Order2.4.4 Link Purpose (In Context)

Quick Facts

  • Criterion2.4.9
  • LevelAAA
  • IntroducedWCAG 2.0

Automate Compliance

AccessiSight automatically scans and identifies 2.4.9 issues in your codebase.

Try Scanner Free