Skip to content

Link text and accessibility

Links are what makes the ‘web’ part of the worldwide web. They’re crucial to a usable user journey. So they need to work for everyone. This post explains how to write an accessible link, so everyone understands where it goes.

It’s part of a series called Accessible Intentions, which is for people who want to do the right thing for accessibility, but aren’t sure how. For more context and definitions of some terms I use here, read my introduction to the Accessibility Intentions series.

Cheat sheet: Just tell me what to do

To make sure the links on your website work in an accessible way, every link should make sense out of context.

That means you should be able to read every link on your website with no other information, and understand where it goes. In particular, never use generic text like ‘click here’ or ‘read more’.

Also, never repeat link text on a page if the link destination is different.

Why is it important to think about how we write links?

When people are looking at a page on your website, they’re often thinking about where to go next, or even looking for a specific link.

Visual formatting helps sighted people to scan the links on a page. Screen reader users can ask for the links on a page to be read out. The principle is the same.

In either case, it’s confusing to have link text that doesn’t give enough context about where it goes. If every link says ‘click here’ or ‘read more’, people have to read all of the surrounding context to work out where each link goes. This can be difficult for everyone, but particularly hard for people using a screen reader.

Examples of accessible and inaccessible link text

Good link text makes it uniquely clear where the link is taking someone. It also needs to be clear if it will do something unexpected, like opening in a new tab or downloading something.

Link destination Bad link text Better link text
A page about company valuesClick hereRead about our values
A PDF download of an essay about otters Read more Download ‘Otters and Me’ [PDF]
A how-to video on YouTube about playing a game Find out how Watch the game instructions on YouTube

What does WCAG say about accessible links?

The bare minimum WCAG standard (level A) is 2.4.4 Link Purpose (In Context). This says that the purpose of the link must be clear from the link text alone. But for this level, there’s an exception for links with a ‘programmatically determined link context’. This means you get away with an unclear links if there’s some context in the same programmatic element, like a sentence or a list item.

For gold standard accessibility (WCAG AAA), 2.4.9 Link purpose (Link only) says exactly the same thing, but without the exception for context.

The exception for programmatically determined context can be hard to get right, and ultimately is still less accessible, so there’s no real reason not to go straight for the AAA standard here.

Exceptions

The only other exception to this rule is when ‘the link would be ambiguous to users in general’.

This means that, for example, I could make the words ‘screen reader’ into a link. This might go to a Wikipedia page about screen readers, or an image search for screen reader users, or a chart about screen reader use.

No-one has any idea where this link goes. Someone navigating visually has no idea. A screen reader user has no idea.

Technically, this amounts to equality. No-one has a clue what’s going on, so no-one is being disadvantaged, according to WCAG.

Is ‘equally bad’ something to strive for?

Personally, I’d argue that people with cognitive issues, learning disabilities or other related conditions probably are being disadvantaged, compared to people who might have a better guess based on context.

Perhaps more importantly, why on earth do you want to create content that is equally inaccessible to everyone?

Where it gets complicated

Link text you can’t control

Some content management systems or plugins automate link text in a way that fails the AAA standard here. ‘Read more’ links on WordPress is a common one. If you’re looking for a blog post and your screen reader reads you out a bunch of links that just say ‘Read more’, it’s hard to know where to go, but sometimes it’s difficult or impossible to change this behaviour.

Sometimes you can find a way around this. If you can’t, make sure you let the company that runs the CMS or plugin know. You can add it to your Accessibility Statement if necessary, and make sure there’s an alternative way in for people who need it.

ARIA

You can also sometimes use ARIA to add context to a link. This context is hidden visually, but accessible to screen reader users.

ARIA is a kind of web language used by developers. This isn’t the right place to explain ARIA, but I will tell you one thing:

“The first rule of ARIA is don’t use ARIA, unless you have to.”

This isn’t an informal mantra – it’s guidance set out by the W3C, who write the WCAG guidelines. It’s very unlikely you’ll need to use ARIA to make your links readable and accessible.

Free tools

The WAVE browser plugin can help surface links on your page so you can see them out of context and make sure they make sense.

Turn  on WAVE and go to the third tab along, called ‘Order’. This will show a pane with all the links and buttons on that page, so you can check them.

Get in touch

If you have feedback on this post, or want help writing accessible links, or anything else to do with accessible and inclusive content, you can get in touch via email.