Goal
Make link text meaningful so users know where links go.
Success Criterion · WCAG 2.4.4
Link Purpose (In Context)
The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.
Level AWCAG 2.0Operable2.4 · Navigable
Copy button ready
What to do
Write link text that clearly describes its destination or purpose from surrounding context.
Why it matters
Screen reader users often navigate by links; vague links like “Click here” are confusing out of context.
Success criterion
What WCAG 2.4.4 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.
Intent
Why WCAG created this requirement
- Users should be able to predict link destination before activating it.
- Link lists in screen readers require meaningful labels.
- Context can be used, but it must be programmatically determinable.
Benefits
Who gains when you pass
- Screen reader users can navigate by links efficiently.
- Users with cognitive disabilities understand navigation options more easily.
- 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 due to ambiguous text.
Link lists become unusable when many links are labeled “Read more.”
Overview
Link text must communicate the purpose/destination either by itself or with adjacent context that is programmatically associated. Avoid ambiguous link labels (e.g., “More,” “Read more,” “Click here”) unless context is clearly available.
- Use descriptive link text: “Download invoice PDF,” “Read the VPAT guide.”
- If using “Read more,” ensure the context is programmatically associated (e.g., in the same sentence or via `aria-labelledby`).
- For icon-only links, provide an accessible name.
Reference: All summaries and highlights originate from Understanding WCAG 2.4.4 and the W3C quick reference.
Fast facts
- Conformance level
- Level A
- 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.
Article cards
Pass
Link says “Read more: Building accessible forms”.
Fail
Every card link says “Read more”.
Icon link
Pass
Icon link has `aria-label="Download report"`.
Fail
Icon link has no text or accessible name.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Create a content guideline for link text conventions.
- Maintain examples of good link text patterns for components.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Understanding 2.4.4
Official W3C interpretation, techniques, and intent for Link Purpose (In Context).
Quick Reference 2.4.4
Filterable list of sufficient techniques and failures.
Technique H30
Providing link text that describes the purpose of a link.
Failure F63
Failure due to providing link text that does not describe purpose.
Implementation checklist
Capture progress and blockers
- Audit link text across pages, including buttons styled as links.
- Replace vague labels (“Click here,” “More”) with descriptive text.
- Ensure icon-only links have accessible names (`aria-label` or labeled by nearby text).
- For repeated “Read more,” include the topic in the link text or associate context programmatically.
Testing ideas
Prove conformance with evidence
- Use a screen reader to list all links on a page and verify each is understandable.
- Inspect icon-only links for accessible names.
- Check repeated patterns (“Read more”) and ensure each can be distinguished.
Related success criteria
More from Navigable (2.4)
WCAG 2.4.1Bypass BlocksLevel AWCAG 2.4.2Page TitledLevel AWCAG 2.4.3Focus OrderLevel AWCAG 2.4.5Multiple WaysLevel AAWCAG 2.4.6Headings and LabelsLevel AAWCAG 2.4.7Focus VisibleLevel AAWCAG 2.4.8LocationLevel AAAWCAG 2.4.9Link Purpose (Link Only)Level AAAWCAG 2.4.10Section HeadingsLevel AAAWCAG 2.4.11Focus Not Obscured (Minimum)Level AAWCAG 2.4.12Focus Not Obscured (Enhanced)Level AAAWCAG 2.4.13Focus AppearanceLevel AAA