Resources

WCAG Fix It: 2.4.4 Link Purpose (In Context)

 

Table of Contents


Free Audit

If your website uses links like “Click here” or icon-only buttons, and it probably does, WCAG 2.4.4 applies to you.

In this WCAG Fix It guide, we’re breaking down a common accessibility issue: unclear link purpose.

It might seem small. Just a few words in a hyperlink, but when link text isn’t meaningful, navigation becomes confusing, frustrating, and sometimes impossible for users relying on assistive technology.

What Is WCAG 2.4.4?

WCAG 2.4.4 – Link Purpose (In Context) requires that the purpose of each link can be determined from:

  • The link text itself, or
  • The link text together with its surrounding context

In simple terms: A user should understand where a link goes or what it does without guessing.

This applies to:

  • Text links
  • Button links
  • Image links
  • Icon-only links

Level A compliance requires clarity at a basic usability level.

What Does “In Context” Mean?

“In context” means the link can be understood when read with the surrounding sentence or paragraph.

For example:

Bad:

Click here

Better:

Download the accessibility checklist

Context example:

Read more about our accessibility services.

Here, “Read more” works only because the sentence clearly defines what the link refers to.

But there’s a problem.

Screen readers often allow users to navigate by listing all links on a page.

If your site contains:

  • Click here
  • Read more
  • Learn more
  • More

That list becomes meaningless.

The Human Impact of Unclear Links

Imagine navigating a website using a screen reader and opening the links list.

You hear:

  • Click here
  • Read more
  • Learn more
  • View

That’s it. No context.

You don’t know:

  • Where the link goes
  • What you’ll download
  • Whether it’s external
  • Whether it’s important

Navigation becomes guesswork and when navigation becomes guesswork, users lose trust.

Unclear links don’t just reduce usability, they create digital barriers.

Common WCAG 2.4.4 Failures

Here’s what we typically see when scanning websites:

  • “Click here” used repeatedly
  • “Read more” with no descriptive context
  • Multiple links on a page with identical text but different destinations
  • Icon-only links with no accessible label
  • Empty anchor tags
  • Linked images with no alternative text

All of these can fail WCAG 2.4.4.

How to Fix Unclear Link Text

Identify Problematic Links

Run your site through an accessibility checker or check over all your link manually for the common mistakes

The Recite Me Accessibility Checker will flag:  WCAG 2.4.4 – Link Purpose (In Context)

You’ll see:

  • The affected link
  • The link destination
  • Why it lacks clarity

Replace Generic Link Text

Instead of:

<a href=”guide.pdf”>Click here</a>

Use:

<a href=”guide.pdf”>Download the 2026 Accessibility Compliance Guide</a>

The link now clearly explains its purpose.

Fix Icon-Only Links

If you use icons as links, such as a magnifying glass for search:

Bad:

<a href=”/search”><i class=”icon-search”></i></a>

Better:

<a href=”/search” aria-label=”Search the website”>

  <i class=”icon-search”></i>

</a>

The aria-label ensures screen readers announce the purpose.

If You’re Using a CMS

No coding required.

In platforms like WordPress, Shopify, Wix, or Squarespace:

  • Edit the hyperlink text
  • Replace vague phrases
  • Update button labels
  • Add accessible labels for icons

Save and retest.

How to Write Good Link Text

Here’s the golden rule:

👉 The link should make sense on its own.

Instead of:
“Click here”

Use:
“View our accessibility services”
“Download the annual report”
“Read the WCAG compliance guide”

Keep it:

  • Specific
  • Action-focused
  • Context-aware
  • Meaningful

Avoid:

  • Repeating identical link text to different pages
  • Using URLs as link text
  • Relying only on surrounding visuals

What About “Read More” Links?

“Read more” can pass WCAG 2.4.4 if the surrounding heading clearly defines what the link relates to.

For example:

Heading:

Accessibility in Healthcare

Link:

Read more

Because the heading provides context, this may be acceptable.

However, from a usability and SEO perspective, descriptive links are still stronger.

Why WCAG 2.4.4 Matters Beyond Compliance

Clear links:

  • Improve navigation
  • Reduce confusion
  • Support screen reader users
  • Improve SEO (anchor text matters)
  • Strengthen user trust
  • Reduce legal exposure

This isn’t just about accessibility.

It’s about making your website easier to use for everyone.

Small wording changes.
Massive navigation improvement.

WCAG 2.4.4 Quick Fix Checklist

All links clearly describe their destination
No repeated “Click here” links
Icon-only links include aria-label
Linked images include alt text
Link list makes sense when read independently
Links re-tested after updates

WCAG 2.4.4 Link Purpose Frequently Asked Questions

What is WCAG 2.4.4 Link Purpose (In Context)?

WCAG 2.4.4 requires that the purpose of a link can be determined from the link text itself or from its surrounding context so users understand where it leads.

Can I use “Click here” and still be compliant?

Only if the surrounding context makes the destination completely clear. However, descriptive link text is strongly recommended for usability and SEO.

Do icon-only links need accessible labels?

Yes. Icon-only links must include accessible labels (such as aria-label) so screen readers can announce their purpose.

Why does link text matter for accessibility?

Screen reader users often navigate by scanning a list of links. If link text is unclear, navigation becomes confusing and inefficient.

Related Content

WCAG Fix It: 4.1.2 Name, Role, Value

If your website has buttons, forms, menus, dropdowns, or interactive components, WCAG 4.1.2 applies to you. In this WCAG Fix It guide, we’re breaking down one of the most technical-sounding, yet critically important accessibility requirements: ensuring that interactive elements have a proper, programmatically defined name, role, and value. It sounds developer-heavy burut at its core,

Read more: WCAG Fix It: 4.1.2 Name, Role, Value

WCAG Fix It: 3.3.2 Labels or Instructions

If your website has forms, contact forms, checkout forms, booking forms, login forms, WCAG 3.3.2 applies to you. In this WCAG Fix It guide, we’re breaking down one of the most common and preventable accessibility failures: missing labels or unclear instructions. When users don’t know what information is expected in a field, forms become frustrating,

Read more: WCAG Fix It: 3.3.2 Labels or Instructions

WCAG Fix It: 3.1.1 Language of Page

If your website has text and they all do, WCAG 3.1.1 – Language of Page applies to you. In this WCAG Fix It guide, we’re breaking down a technical requirement that has a huge impact on accessibility: ensuring the primary language of your web page can be programmatically determined. It’s one line of code, but

Read more: WCAG Fix It: 3.1.1 Language of Page