WCAG 2.4.4 Link Purpose (In Context)
Updated October 14, 2026 · 3 min read
- Level
- A · WCAG 2.0
- EN 301 549
- 9.2.4.4
- What the checker tests
- Partly automated: Clickable areas of an image have no description, Some links do not say where they go
- Official text
- Understanding 2.4.4 Link Purpose (In Context) (W3C, in English)
Success criterion 2.4.4 helps people decide whether to follow a link without guessing. Screen reader users often pull up a list of all links on a page, and keyboard users move from link to link; a list of ten "Click here" links tells them nothing. It is level A and part of EN 301 549 (clause 9.2.4.4).
What the criterion requires
The purpose of each link can be determined from:
- the link text alone, or
- the link text together with its programmatically determined link context —
except where the purpose of the link would be ambiguous to users in general.
Link context is information assistive technology can connect to the link: the same sentence, paragraph, list item or table cell, the table header of that cell, or text referenced with aria-describedby. The accessible name of a link also counts — for an image link, that is the image's alt text.
The exception covers links whose purpose cannot be worked out from the page by anyone, for example a link in a puzzle; then no extra context is required.
Typical failures on an online shop
- icon-only links (cart, account, wishlist, social media) with no text and no
aria-label; - product image links where the image has no alt text, so the link has no name at all;
- several "Read more", "Shop now" or "Details" links in a grid with no relationship to the product name;
- a linked image map area (
<area>) with noalt; - links whose text is a bare URL or a tracking code.
How to check it
Automated: our checker reports links without discernible text (link name rule) and image map areas without alternative text. It cannot judge whether a name like "More" is clear in context, so ambiguous link text needs a manual check.
By hand: use a screen reader's links list (or a browser extension that lists links) and read each link out of context. If a link is unclear, check whether its sentence, list item, table cell or heading makes it clear. Check icon links and image links especially.
How to fix it
- Write link text that says where it goes: "View shipping costs" instead of "Click here".
- In product cards, make the product name the link, or add context to repeated links:
Shop now<span class="visually-hidden"> – Linen shirt</span>. - Give icon links an accessible name with visible text, visually hidden text or
aria-label. - Write alt text for linked images that describes the destination, not only the picture.
- Add
altto every<area>in an image map.
Related criteria
- 2.5.3 Label in Name — the accessible name must contain the visible text.
- 2.4.6 Headings and Labels — headings and labels must be descriptive.
- 1.1.1 Non-text Content — images need text alternatives.
Frequently asked questions
Are "Read more" links allowed under WCAG 2.4.4?
Yes, if their purpose is clear from the programmatically determined context, for example the same sentence, paragraph, list item or table cell, or the heading the link sits under. Link text that makes sense on its own is still better.
What is programmatically determined link context?
Information that assistive technology can relate to the link, such as the surrounding sentence, paragraph, list item or table cell, or text tied to the link with aria-describedby or aria-labelledby.
Do icon links fail 2.4.4?
An icon link with no accessible name, such as a cart or social media icon without text or aria-label, has no purpose that can be determined. Give it a name like "Cart" or "Instagram".