- Level
- A
- Since
- WCAG 2.0
- Entries
- 106 / 193
2.4.4 Link Purpose (In Context)
A link has to say where it goes. Read on its own, click here says nothing.
/ What it requires
Screen reader users often move through a page link by link, or open a list of all links to find the one they want. In both cases they hear the link text with little or nothing around it. A link that says only more, here or details, or an icon link with no text at all, tells them nothing. Voice control users also need a name to speak, and everyone scanning a page benefits from links that say where they lead.
The purpose must be clear from the link text alone, or from the text together with its programmatically determined context: the same sentence, paragraph, list item or table cell with its headers, or an aria-label or aria-labelledby on the link. Read more at the end of a paragraph about one topic can pass on context. It fails when nothing nearby explains it. The criterion excepts links whose purpose would be ambiguous to users in general.
/ How pages fail it
- A link contains only an icon or an image with no alt text, so it has no name and a screen reader falls back to reading the URL.
- A row of news teasers each ends with Read more, and the link sits in its own element apart from the headline it belongs to.
- A social media icon is drawn as a CSS background or an SVG and the link around it has no accessible name.
- The link text is a raw URL or a file name such as doc_final_v3.pdf.
- Several links with the same words, for example Download, lead to different files.
/ How to check it yourself
- Tab through the page and read only the text of each link as it receives focus. Ask whether you know where it goes.
- Open a list of links: in the free screen reader NVDA press Insert+F7, in VoiceOver use the rotor. Read the list from top to bottom. Vague and repeated names stand out.
- For each vague link, check whether its own sentence, paragraph, list item or table cell supplies the missing part.
- Inspect icon-only links in DevTools, where the Accessibility pane shows the computed name. An empty name is a failure.
- Run a free checker such as WAVE or axe DevTools to list links with no text.
/ How to fix it
- Write the destination into the link text: Annual report (PDF) instead of click here.
- For image links, put the destination in the alt attribute of the img. For SVG icon links, add aria-label to the a element or a visually hidden span with text inside it.
- Keep a repeated Read more but extend its name with a visually hidden span that holds the article title, or with aria-labelledby that points at the link and at the headline.
- Or make the headline itself the link and drop the separate Read more.
- Where the visible text stays short, make sure the accessible name still contains the visible words, so that voice control users can speak what they see.
/ What our scanner checks
Four checks map here. On the HTML source, link_text_missing counts links and buttons with no text, aria-label, title or image alt, and link_text_generic counts those whose whole text is one of a short list of English phrases such as click here. On the rendered page, ambiguous-link-text reports identical names leading to different destinations, and the axe-core rule link-name reports links without a name. None reads the surrounding sentence.
/ Who fails it, in our own measurements
One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.
/ Questions about this criterion
Is Read more always a WCAG failure?
No. At level A the purpose may come from the link text together with its context, so Read more inside the paragraph or list item that names the topic can pass. It fails when the context is not programmatically connected, for instance when the link sits in a separate container. The stricter AAA criterion 2.4.9 requires the link text to work alone.
Should I use aria-label or visually hidden text on a link?
Both give the link an accessible name. Visually hidden text sits in the content, so it is maintained along with it. An aria-label overrides whatever text is inside the link for assistive technology, so it has to repeat the visible words and be updated when they change. For icon-only links either works. For links with visible text, added hidden text is the safer choice.
Is identical link text a problem?
It is when the links lead to different places, because in a list of links nothing tells them apart. Links that go to the same destination can and should share the same text. A separate criterion, 3.2.4 Consistent Identification, asks that components with the same function are identified consistently across a set of pages.
