Links Must Have Discernible Text

Links must clearly communicate their purpose to users. A link with no accessible name, hidden text, or mouse-only behaviour prevents users from understanding where the link goes or even activating it at all. When the link purpose is unclear or unavailable to assistive technologies, navigation becomes confusing and unreliable.

WCAG Success Criteria

2.4.4 Link Purpose (In Context) (Level A)
4.1.2 Name, Role, Value (Level A)

This issue is commonly reported under multiple criteria because missing or unclear link text affects both navigation (2.4.4) and programmatic naming (4.1.2).

Each link must have an accessible name that can be programmatically determined and understood by assistive technologies.

Why This Matters

Links are one of the primary ways users navigate the web.

For screen reader users, links are often explored through:

• A list of links on the page
• Sequential navigation from link to link

If a link’s purpose is not discernible:

• Users cannot tell where the link goes
• Multiple links may sound identical
• Users may activate the wrong link
• Navigation becomes slow and error-prone

For keyboard-only users, links that cannot receive focus or rely on mouse-only interactions are completely unusable.

Who This Helps

This requirement primarily supports:

• Screen reader users
• Keyboard-only users
• Users with motor impairments
• Users with cognitive or memory limitations
• Users navigating long pages with many links

Clear, accessible link text benefits all users, not only those using assistive technology.

Accessible Name (Key Concept)

The accessible name is the text that assistive technologies use to identify an element.
For links, this is what screen readers announce.

If a link does not have an accessible name, it effectively has no label for assistive technology users.

What “Discernible Text” Means

A link has discernible text when:

• It has an accessible name
• That name describes the link’s purpose
• The name is available to assistive technologies

The accessible name may come from:

• Visible link text
• aria-label
• aria-labelledby
• alt text, when an image is used as a link

It is not enough for a link to exist visually.
Its purpose must be programmatically available.

Link Purpose vs Link Name

These are related but distinct concepts.

Link Purpose (2.4.4)
Asks whether users can understand what the link does, using the surrounding context if needed.

Link Name (4.1.2)
Asks whether assistive technologies can determine the link’s name at all.

A link may pass one and fail the other.
For example, a visually clear link may still fail if its text is hidden from screen readers.

Common Causes of Undiscernible Links

Links often fail this requirement when:

• Link text is hidden using display: none or aria-hidden="true"
• Multiple links use identical text like “Read more” without sufficient context
• Links rely only on icons with no accessible label
• Clickable elements are not real links (<a href>)
• Interaction depends on mouse-only events

Focusability and Keyboard Access

Links and form controls receive keyboard focus by default, while most other elements do not unless explicitly made focusable.

A link fails if:

• It cannot be focused using Tab
• It can only be activated using a mouse
• It relies on hover-only behavior

Keyboard users must be able to:

• Tab to the link
• Identify it
• Activate it

Mouse-Only Events Are Not Enough

Events that depend solely on mouse interaction exclude keyboard users. Avoid using:

• onmouseover()
• onmouseout()
• Hover-only behavior

Instead, ensure equivalent keyboard support using:

• onfocus()
• onblur()
• Standard link activation (<a href>)

Mouse and keyboard users must be able to access the same functionality.

Using ARIA to Clarify Link Purpose

ARIA can be used when visible link text alone is insufficient.

<h4>Neighborhood News</h4>
<p>
  Seminole tax hike: Seminole city managers are proposing a 75% increase in property taxes.
  <a href="taxhike.html" aria-label="Read more about the Seminole tax hike">
    Read more
  </a>
</p>

In this case:

• Visible text is short
• aria-label provides a clear, descriptive, accessible name

ARIA should supplement, not replace, meaningful visible text where possible.

Link Styling and Focus Visibility

Do not remove visual focus styles from links. Suppressing focus indicators makes it impossible for sighted keyboard users to know:

• Which link is currently focused
• Where they are on the page

Ensure that:

• Focus styles are preserved or enhanced
• Links remain visually identifiable when focused

This requirement works closely with 2.4.7 Focus Visible.

Examples

Passing examples

1. A text link reads “Download annual accessibility report (PDF)” and is focusable, visible, and announced correctly by screen readers.
2. An icon-only link includes an aria-label that clearly describes its purpose.

Failing examples

1. Multiple links labelled “Read more” appear on a page with no additional accessible context to distinguish them.
2. A clickable element uses onmouseover to trigger navigation and cannot receive keyboard focus.

Rule Description

Every link must have an accessible name that clearly identifies its purpose and must be focusable using the keyboard.

If a link cannot be identified or activated by assistive technologies, the requirement fails.

The Algorithm

1. Identify all links on the page
2. Check that each link can receive keyboard focus
3. Verify that each link has an accessible name
4. Ensure the name describes the link’s purpose
5. If a link is unlabeled, hidden, duplicated without context, or mouse-only:
   • The criterion fails

How to Avoid Discernible Link Issues

• Use meaningful, descriptive link text
• Avoid vague labels like “Click here” or “Read more” without context
• Avoid relying on the surrounding visual context alone to explain link purpose
• Ensure links are real <a href> elements
• Provide accessible names for icon-only links
• Avoid mouse-only event handlers
• Preserve visible focus styles

How to Test This

• Navigate the page using Tab only
• Use a screen reader to list all links
• Check for duplicate or unclear link names
• Verify that all links can be focused and activated
• Confirm that link purpose is clear without relying on surrounding visuals

Wrapping Up

Links are navigation. If users cannot tell where a link goes or cannot activate it with the keyboard, the page is functionally broken for them.

Discernible link text ensures that:

• Navigation is predictable
• Link purpose is clear
• Keyboard and screen reader users can move confidently through content

At Level A, this requirement is fundamental. If links are not accessible, the web is not usable.