Accessible Links – Link Text, WCAG Requirements and Best Practices
Accessible links are one of the most fundamental elements of accessible websites – and at the same time one of the most common sources of errors. An accessible link has meaningful link text that clearly communicates to users – especially screen reader users – where the link leads. Link texts such as "click here", "more" or "read more" without explanatory context are typical barriers that make navigation difficult or impossible for people with disabilities.
For screen reader users, the quality of link text is particularly critical: they can call up all links on a page as a list and navigate through them – without hearing the surrounding text. An example: a page with ten instances of "click here" is completely unusable for a screen reader user. The same page with ten meaningful link texts is efficiently navigable.
The WCAG address accessible links under the principle of Operability. Criterion 2.4.4 (Level AA) is relevant for digital offerings covered by the EAA and requires understandable link text. Criterion 1.4.1 (Level A) additionally prohibits colour as the sole distinguishing characteristic for links within body text.
Accessible Links at a Glance
- Meaningful link text: Purpose of link understandable without context – no "click here"
- Keyboard accessible: All links reachable via Tab, visible focus indicator present
- Not distinguished by colour alone: Underline or other visual indicator required
- Image links: Alt text of image describes the link destination, not the image
- WCAG criterion: 2.4.4 Link Purpose (AA) – purpose determinable from link text or context
Good and Bad Link Text: Examples Compared
The difference between accessible and inaccessible link text is quickly illustrated in practice. The following examples show how poor link text arises and how to improve it. The key question is always: does a user understand the purpose of this link if they only hear or read the link text – without surrounding text or context?
- ❌ "Click here" → ✓ "Download Accessibility Report 2025 (PDF)"
- ❌ "Learn more" → ✓ "Learn more about our accessibility testing tools"
- ❌ "Next" → ✓ "Next: Step 2 – Payment details"
- ❌ "www.sitecockpit.com" → ✓ "SiteCockpit – digital accessibility testing"
- ❌ "[image]" → ✓ alt="Go to SiteCockpit homepage" (when image is a link)
Link Text and Screen Readers: How Navigation Works in Practice
Screen reader users navigate websites fundamentally differently from sighted users. One of the most common navigation methods is the link list: the screen reader lists all links on the current page – the user moves through this list and activates the desired link. In this mode, the user hears only the link text – no body text, no context, no headings.
Another example: a product page with twenty "Buy now" links for different products is completely indistinguishable in screen reader mode. Accessible link texts would read: "iPhone 15 Pro – buy now", "MacBook Air M3 – buy now" – allowing the user to select the desired product directly.
WCAG Requirements for Accessible Links
The WCAG set several requirements for accessible links. The most important criterion is 2.4.4 – but accessible link design involves more than just the link text. Visual recognisability, keyboard operability and context all play a role.
- 2.4.4 Link Purpose (AA): Purpose of link determinable from link text or programmatically determined context
- 2.4.9 Link Purpose – Link Only (AAA): Purpose determinable from link text alone – without context
- 1.4.1 Use of Colour (A): Links in body text not distinguishable by colour alone
- 2.1.1 Keyboard (A): All links reachable and activatable via keyboard
- 2.4.7 Focus Visible (AA): Keyboard focus on links must be visible
Making Image Links and Icon Links Accessible
Image links and icon links – links where no visible text is present – deserve special attention. When an image or icon is used as a link, the accessible name of the link must communicate the link purpose to the user. This is done via the alternative text of the image or an aria-label on the link element.
- Logo as link:
alt="Go to [Company name] homepage"– notalt="logo" - Social media icons:
aria-label="SiteCockpit on LinkedIn"instead of empty icon - Product images as links: Alt text describes the destination, not the image – e.g.
alt="iPhone 15 Pro – open product page" - Arrow or plus icons:
aria-labeldescribes the action – e.g.aria-label="Expand product details"
SiteCockpit Solution
easyMonitoring: Automatically Detect Inaccessible Link Text
easyMonitoring automatically checks all links on your website for WCAG 2.4.4 compliance – detecting empty link text, generic content such as "click here" and image links without an accessible name. This gives you an immediate overview of which links on your website create barriers for screen reader users and other people with disabilities.
Discover easyMonitoring →Frequently Asked Questions about Accessible Links
Is "learn more" always a problem?
Not necessarily. WCAG 2.4.4 permits link texts like "learn more" when the context – for example the immediately preceding heading – is programmatically associated with the link and the screen reader automatically reads this context. However, a fully self-explanatory link text is always preferable, as not all screen readers interpret context identically.
Can links open in a new tab?
Yes – but users should be informed in advance. A note in the link text (e.g. "Privacy policy – opens in new tab") or an aria-label with this information is recommended. Unexpected new tabs can be particularly confusing for screen reader users and people with cognitive impairments.
Should URLs be used as link text?
No – and in most cases this is poor practice. A URL such as "https://www.sitecockpit.com/en/products/easymonitoring" read aloud by a screen reader character by character is barely understandable for users. A descriptive link text should be used instead, for example "easyMonitoring by SiteCockpit".
What is the difference between WCAG 2.4.4 and 2.4.9?
WCAG 2.4.4 (Level AA) allows the purpose of a link to be determined from the link text together with its programmatically determined context. WCAG 2.4.9 (Level AAA) is stricter: the purpose must be determinable from the link text alone – without context. Level AA is the relevant benchmark for legal compliance under the EAA.
Check the Links on Your Website for Accessibility
With easyMonitoring, you can automatically identify which links on your website are inaccessible to screen reader users and other people with disabilities – and get concrete guidance on improvement.
Try for free