Overview
Link text must describe the destination or purpose of the link. "Click here" and "Read more" are meaningless when read out of context.
Screen reader users often pull up a list of every link on a page to navigate quickly—and in that list, ten links all reading “click here” or “read more” are useless. Vague link text (WCAG 2.4.4) forces users to hunt for context they can’t easily reach, and it hurts SEO too, since search engines use anchor text to understand the destination. Descriptive links help everyone, especially on mobile and for users with cognitive disabilities.
The Problem
This pattern is inaccessible — avoid it.
The Fix
Use this accessible pattern instead.
Step-by-step
Replace generic phrases ("click here", "learn more", "read more") with descriptive text.
The link text should make sense when read alone, out of context.
For links that open in a new tab, add visually-hidden text '(opens in new tab)' or an aria-label.
For icon-only links, add aria-label to the <a> element.
Common Mistakes
Repeating “Read more” / “Learn more” / “Click here” across many links.
Using a raw URL as link text (screen readers read it character by character).
Opening a link in a new tab with no warning.
Linking an image that has no alt text and no aria-label.
How to Test for It
List all links in a screen reader (Insert+F7 in NVDA) and check each makes sense alone.
Read your link text out of context—does it still describe where it goes?
Run an automated scan for generic or ambiguous link text.
Framework Notes
How to apply this fix in your stack.