WCAG 2.4.4 Link Purpose (In Context): what it means and how to fix it
Short answer: Every link must have text (or an accessible name) that tells people where it goes. Icon links with no name, and vague "click here" links, fail.
What it requires
The purpose of each link must be clear from its text, or from the link text together with its surrounding context. A link with no text at all, such as an image or icon link without alt text or a label, fails outright.
Who it affects
Screen reader users, who often pull up a list of all links on a page. "Link, link, click here, read more" is useless out of context.
How it shows up in ADA website claims
Empty links, usually social media icons, cart icons, and linked logos without alt text, are among the most common automated findings cited in complaints.
How to check your site
- An automated scan flags links with no accessible name.
- Check icon links in the header and footer especially.
- Read the link text alone: would you know where it goes?
How to fix it
<!-- Fails: empty link -->
<a href="https://instagram.com/brand"><i class="icon-instagram"></i></a>
<!-- Passes -->
<a href="https://instagram.com/brand" aria-label="Instagram"><i class="icon-instagram" aria-hidden="true"></i></a>
<!-- Better than "Read more" -->
<a href="/guides/returns">Read more about returns</a>
Frequently asked questions
Is "Read more" always a failure?
Not under 2.4.4 if the surrounding sentence or card heading makes the destination clear. It is still better practice to make the link text descriptive on its own.
What makes a link empty?
An a element whose only content is an icon font, an SVG without a title, or an image without alt text, and which has no aria-label.
Do links that open a new tab need a warning?
It is recommended, for example "(opens in new tab)", but not a strict requirement of 2.4.4.
Automated rules that test this (axe-core): link-name. Our scanner runs these checks.
Other commonly cited criteria
- 1.1.1 Non-text Content
- 1.2.2 Captions (Prerecorded)
- 1.3.1 Info and Relationships
- 1.4.3 Contrast (Minimum)
- 1.4.4 Resize Text
- 2.1.1 Keyboard
- 2.4.1 Bypass Blocks
- 2.4.2 Page Titled
- 2.4.7 Focus Visible
- 3.1.1 Language of Page
- 3.3.2 Labels or Instructions
- 4.1.2 Name, Role, Value
Read the official WCAG 2.1 specification at W3C.
Proof of Access provides technical accessibility assessments. We are not a law firm and nothing on this page is legal advice. If you have received a demand letter or a lawsuit, talk to an attorney.