Link Text Accessibility Checker
WCAG 2.4.4 requires that the purpose of every link can be determined from its text or context. Generic links like 'click here' and 'read more' are found on 18% of home pages.
No signup required. Results in under 60 seconds.
What WCAG 2.4.4 and 2.4.9 Require
WCAG 2.4.4 (Link Purpose in Context, Level A) requires that the purpose of each link can be determined from the link text alone, or from the link text together with its programmatically determinable context (surrounding paragraph, list item, table cell, or heading). WCAG 2.4.9 (Link Purpose Link Only, Level AAA) raises the bar — the link text alone must be sufficient without any surrounding context. Screen reader users frequently navigate by pulling up a list of all links on the page. When that list contains ten entries reading "click here", "read more", "learn more", and "here", the links are meaningless outside their visual context. The WebAIM Million study finds generic link text on 18% of home pages. Fixing this is straightforward and has immediate impact.
Why Descriptive Link Text Matters
Generic link text creates real barriers:
- Screen reader link lists: Users invoke a links list (Insert+F7 in JAWS) to navigate. A list showing "click here, click here, read more, read more, learn more" is useless — every link sounds identical
- Voice control: Users of Dragon NaturallySpeaking say "click" followed by the link text. Saying "click read more" when there are five "read more" links forces the software to number them, slowing navigation significantly
- Cognitive accessibility: Descriptive links help all users understand where a link goes before clicking. "Download Q3 financial report (PDF, 2.4MB)" is far more useful than "click here"
- SEO benefit: Search engines use anchor text to understand linked page content. Descriptive link text improves your internal linking SEO — another case where accessibility and SEO align perfectly
Common Link Text Violations and Fixes
Replace generic link patterns with descriptive alternatives:
- Bad:
<a href="/report">Click here</a> to download the report. Good:<a href="/report">Download the Q3 financial report</a> - Bad:
<a href="/pricing">Read more</a>. Good:<a href="/pricing">See CompliScan pricing plans</a> - Bad:
<a href="https://example.com">https://example.com</a>. Good:<a href="https://example.com">Visit Example.com's accessibility guide</a> - Icon-only links:
<a href="/cart"><svg>...</svg></a>has no accessible name. Fix:<a href="/cart" aria-label="Shopping cart (3 items)"><svg aria-hidden="true">...</svg></a> - Redundant links: An image and text linking to the same URL in adjacent elements. Fix: combine into one link containing both the image and text
How CompliScan Detects Link Text Issues
CompliScan identifies links with generic or ambiguous text including "click here", "here", "read more", "learn more", "more", and similar patterns. The scanner also detects: links with no accessible name (empty links or icon-only links without aria-label), links whose accessible name is just a URL, and adjacent duplicate links pointing to the same destination. Each finding shows the current link text, its destination, and an AI-generated suggestion for descriptive replacement text based on the surrounding content and link target. Automated detection of generic link text is highly reliable — CompliScan catches these patterns consistently. For more nuanced link purpose issues (whether "Download report" is specific enough when there are multiple reports), manual review supplements the automated scan. Fix link text issues before the ADA Title II deadline of April 24, 2026 — it is one of the fastest compliance improvements. Try a free scan to identify all problematic links on your site.
Frequently Asked Questions
Is 'Read more' always a violation?
Under WCAG 2.4.4 (Level A), 'Read more' can pass if the surrounding programmatic context (like a heading or paragraph) makes the link purpose clear. For example, 'Read more' inside an article card with a heading visible to screen readers may be acceptable. However, under WCAG 2.4.9 (Level AAA), 'Read more' always fails because the link text alone does not convey the purpose. Best practice is to use descriptive text like 'Read more about our accessibility scanning features' regardless of conformance level.
How do I fix 'read more' links in WordPress or CMS templates?
Most CMS platforms generate 'Read more' links in post excerpts. In WordPress, you can use the_title() in the link text: 'Read more about [Post Title]'. Many themes support this through customization options. Alternatively, add aria-label to the link: <a href='...' aria-label='Read more about [Post Title]'>Read more</a>. This keeps the visual design while providing screen readers with descriptive text.
Should links open in new tabs?
Opening links in new tabs (target='_blank') should be used sparingly and always indicated to the user — both visually (an external link icon) and programmatically (add text like '(opens in new tab)' visible or via sr-only span). Unexpected new tabs disorient screen reader users and break the Back button. WCAG 3.2.5 (Level AAA) advises against changes of context that the user does not initiate. If you must use new tabs, warn users.
How do I handle links that are images?
If a link contains only an image, the image's alt text becomes the link's accessible name. The alt text should describe the link destination, not the image: alt='CompliScan home page' rather than alt='CompliScan logo'. If the link contains both an image and text, the image can have alt='' (decorative) and the text serves as the link name. Never have a link with neither text nor alt text — it will be announced as just the URL or 'link' with no purpose.
More Free Tools
Check Your Website Now
Enter your URL below and get a free accessibility report with AI-powered fix suggestions in under 60 seconds.
No signup required. Results in under 60 seconds.