Loading Developer Playground

Loading ...

Skip to main content

Success Criterion · WCAG 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 of the link would be ambiguous to users in general.

Level AAAWCAG 2.0Operable2.4 · Navigable
Copy button ready

Goal

Make every link’s purpose clear from the link text alone.

What to do

Ensure each link’s text is sufficient to identify its destination/purpose without surrounding context.

Why it matters

Screen reader users often navigate by link lists, where surrounding context is not available.

Success criterion

What WCAG 2.4.9 requires

Summarized directly from the official Understanding document so teams can quote the requirement accurately.

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

Intent

Why WCAG created this requirement

  • Link lists must be usable without needing page context.
  • Link text should be unique and descriptive.
  • Icon-only links need accessible names that are descriptive.

Benefits

Who gains when you pass

  • Screen reader users can choose links from a list confidently.
  • Users with cognitive disabilities benefit from explicit, self-contained link labels.
  • All users benefit from clearer calls-to-action.

Why it matters

User impact when this criterion fails

Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.

Users may activate the wrong link when labels are ambiguous.

Link lists become unusable if many links share the same generic text.

Overview

This AAA criterion is stronger than 2.4.4. Link text itself must identify destination/purpose without relying on nearby context. Avoid repeated “Read more” links; include the topic in each link label.

  • Include key context in the link itself: “Read VPAT guide” not “Read more.”
  • If multiple similar actions exist, include the item name: “Edit invoice #1234.”
  • Ensure accessible name matches visual label where possible.

Reference: All summaries and highlights originate from Understanding WCAG 2.4.9 and the W3C quick reference.

Fast facts

Conformance level
Level AAA
WCAG version introduced
WCAG 2.0
Principle
Operable
Guideline
2.4 · Navigable

Examples

Make success tangible for teams

Share pass/fail snapshots to coach designers, engineers, QA, and content authors.

Blog list

Pass

Links are “Read: Building accessible forms” and “Read: CSS grid vs flexbox”.

Fail

Each card has a link labeled “Read more”.

Action list

Pass

“View invoice #1042” and “Download invoice #1042 PDF”.

Fail

Multiple “View” links with no distinguishing text.

Evidence to keep

Document conformance decisions

Capture artifacts for VPATs, procurement reviews, and regression testing.

  • Set a content standard: links must be meaningful out of context for AAA.
  • Provide component patterns for “Read more” links that include titles.

Official resources

Deep dives and supporting material

Keep these links handy when writing acceptance criteria or responding to audits.

Implementation checklist

Capture progress and blockers

  • Audit all links (including buttons styled as links) for self-contained meaning.
  • Replace generic labels with descriptive text.
  • For repeated links, include the target title in each link label.
  • Ensure icon-only links have descriptive accessible names.

Testing ideas

Prove conformance with evidence

  • Use a screen reader “links list” view and verify each link is understandable on its own.
  • Verify repeated actions (Edit/View/Read more) include specific object names.
  • Inspect accessible names for icon-only links.

Related success criteria

More from Navigable (2.4)

View all criteria