Skip to main content
Accessibility.com, LLC
Category: Input and Navigation

Descriptive Link Text

Also known as: Meaningful Link Text, Descriptive Links
Simply put

Descriptive link text is wording for a hyperlink that clearly indicates where the link goes or what it does, rather than using vague phrases like "click here" or "read more." This helps everyone, including people who use screen readers, understand and reach content more easily. Because some users navigate by scanning through a list of links, the link text needs to make sense on its own.

Formal definition

Descriptive link text is link text (or programmatically associated text) that conveys the purpose or destination of a hyperlink so its function can be understood, ideally when read in context and often when read out of context. It supports WCAG 2.4.4 Link Purpose (In Context), a Level A success criterion, which addresses whether the purpose of each link can be determined from the link text alone or together with its programmatically determined context. Practitioners generally avoid ambiguous phrases such as "click here" and "read more," keep link text concise but meaningful, and, where images serve as links, ensure the image's alternative text performs the function of link text. Because screen reader users may navigate via a generated list of links, link names should be self-descriptive and not unnecessarily lengthy. Note that a related, stricter criterion, WCAG 2.4.9 Link Purpose (Link Only), is Level AAA and is out of scope for this entry; this guidance describes accessibility technique and usability practice and is not legal advice.

Why it matters

Link text is one of the primary ways users decide whether and where to navigate. When links use vague phrases like "click here" or "read more," users must rely on surrounding text to infer where the link leads. Many screen reader users navigate by pulling up a generated list of all links on a page, and in that list each link is presented out of its surrounding context. A list full of identical "read more" or "click here" entries gives those users no way to distinguish one destination from another, forcing them to explore each link individually or hunt back through the page.

Descriptive link text is not only an accessibility consideration but also a usability one. As accessibility practitioners have noted, descriptive links help all users, not just those using assistive technology, reach the information they want faster; non-descriptive link text is fundamentally a usability issue. Clear link wording lets everyone scan a page and predict where each link will take them before they select it.

Meaningful link text also supports conformance with WCAG 2.4.4 Link Purpose (In Context), a Level A success criterion, which addresses whether the purpose of each link can be determined from the link text alone or together with its programmatically determined context. Meeting this criterion is one component of accessible content, though conformance with a single success criterion does not by itself guarantee an accessible experience or legal compliance. This entry describes accessibility technique and usability practice and is not legal advice.

Who it's relevant to

Content authors and editors
Those who write and publish web content choose the wording of links directly. Writing link text that indicates the purpose or destination of a link, rather than reusing vague phrases like "click here" or "read more," is one of the most direct ways they can improve both accessibility and usability.
UX and content designers
Designers who define patterns for navigation, calls to action, and repeated components (such as article teasers with "read more" links) can build descriptive, self-descriptive link naming into their templates and design systems, avoiding the usability problem of many identical, non-descriptive links.
Screen reader users
People who use screen readers may have links read to them or navigate through a generated list of links presented out of context. They benefit directly when link names are descriptive and concise, since this lets them understand and reach destinations without exploring each link individually.
Developers implementing linked images
Developers who build image-based links are responsible for ensuring the image's alternative text performs the function of link text, conveying the link's purpose or destination rather than merely describing the image.
Accessibility and compliance teams
Teams evaluating content against WCAG can assess link text as part of Success Criterion 2.4.4 Link Purpose (In Context), a Level A criterion. Because such review often requires judgment about whether purpose is clear from the text or its programmatically determined context, manual review generally supplements automated checks.

Inside Descriptive Link Text

Link Purpose in Context
Descriptive link text is closely associated with WCAG 2.0 Success Criterion 2.4.4 Link Purpose (In Context) at Level A, which addresses whether the purpose of a link can be determined from the link text alone or together with its programmatically determined context.
Link Purpose (Link Only)
WCAG 2.0 Success Criterion 2.4.9 Link Purpose (Link Only) is a Level AAA criterion that calls for the purpose of a link to be identifiable from the link text alone, without relying on surrounding context.
Programmatically Determined Context
Context that assistive technologies can access, such as the sentence, paragraph, list item, table cell, or heading associated with a link, which may supplement the link text to convey purpose under 2.4.4.
Screen Reader Navigation
Many screen reader users navigate by pulling up a list of links out of context; descriptive link text helps ensure each link remains meaningful when separated from surrounding content.
Non-Descriptive Patterns to Avoid
Generic phrases such as 'click here', 'read more', or 'learn more', and bare URLs, are commonly cited as text that does not clearly communicate a link's destination or function on its own.

Common questions

Answers to the questions practitioners most commonly ask about Descriptive Link Text.

Does using descriptive link text guarantee WCAG conformance or legal compliance?
No. Descriptive link text supports specific WCAG success criteria related to the purpose of links, but conformance depends on meeting all applicable criteria, and no single technique guarantees full conformance. Meeting WCAG success criteria also does not by itself guarantee an accessible experience for every user or immunity from legal claims. Automated tools detect only a portion of link-related issues, so manual review and assistive technology testing are generally needed. This is general information and not legal advice; consult qualified counsel regarding your specific obligations.
Is "click here" always prohibited by accessibility guidelines?
Guidelines do not ban any specific phrase outright. The concern with text like "click here" or "read more" is that it may not convey the link's purpose when read on its own, which matters because some users navigate by pulling up a list of links out of context. The relevant question is whether the purpose can be determined from the link text, or in some cases from the link together with its surrounding context, depending on which WCAG success criterion and conformance level you are targeting.
How can I make link text descriptive without making it excessively long?
Aim for text that identifies the destination or action concisely, using the words a user would recognize, such as the title of the target page or document. You generally do not need to restate surrounding sentence context in the link itself. Front-loading the most distinguishing words can help users who scan a list of links, while avoiding unnecessary boilerplate keeps the text readable.
What are my options when the same visible label appears on multiple links, such as repeated "Read more" links?
Options commonly discussed include revising the visible text so each link is distinct, or supplementing the visible text through techniques such as visually hidden text or accessible-name mechanisms that add context for assistive technology. Which approach is appropriate depends on your design, the target conformance level, and how the success criterion applies, so test the result with assistive technology rather than assuming the markup behaves as intended.
How should link text be handled for links that open documents or files, such as a PDF?
It is often helpful to convey the destination clearly in or near the link, and many practitioners include the file type or format so users know what to expect. This is a usability and clarity practice; confirm how your specific approach maps to the WCAG criteria and conformance level you are targeting, and verify the experience with manual and assistive technology testing.
Can automated testing tools confirm that link text is descriptive?
Automated tools can flag certain patterns, such as empty links or repeated generic phrases like "click here," but they generally cannot judge whether text meaningfully conveys a link's purpose, which is a matter of human interpretation. Because automated testing detects only a portion of issues, manual review and testing with assistive technology are typically required to evaluate descriptive link text reliably.

Common misconceptions

Descriptive link text is a Level AA requirement.
The core requirement, WCAG 2.4.4 Link Purpose (In Context), is generally cited at Level A. The stricter version requiring purpose from the link text alone, 2.4.9 Link Purpose (Link Only), is a Level AAA criterion. AA-targeted programs commonly need to satisfy 2.4.4 but not 2.4.9.
Every link must be understandable from its text with no surrounding context.
Under 2.4.4 (Level A), the purpose may be determined from the link text together with its programmatically determined context. Requiring the text to stand entirely alone reflects the more demanding Level AAA criterion 2.4.9 rather than the baseline expectation.
Automated tools can fully verify that link text is descriptive.
Automated testing can flag some patterns, such as repeated generic phrases, but it detects only a portion of issues. Determining whether link text meaningfully conveys purpose generally requires manual review and testing with assistive technology.

Best practices

Write link text that conveys the link's destination or function, avoiding generic phrases like 'click here', 'read more', and 'learn more' where they stand alone.
Ensure link purpose can at minimum be determined from the link text plus its programmatically determined context to support WCAG 2.4.4 (Level A).
Where feasible, make link text meaningful on its own so links remain clear when a screen reader user reviews a list of links out of context, moving toward the intent of 2.4.9 (Level AAA).
Avoid using multiple links with identical text that point to different destinations, and differentiate them through the link text or accessible name.
Test link text with screen readers and manual review rather than relying solely on automated checks, since automated tools detect only a subset of issues.
Treat descriptive link text as one component of accessibility and usability; meeting this criterion does not by itself guarantee full conformance, an accessible experience, or legal compliance, and this guidance is not legal advice.