Issue guide
Missing or vague link text
Link purpose should be clear from text alone where possible.
When link text is vague or missing, users cannot tell where a link goes—especially when links are read out of context.
See this on your site
Run a scan, then match rule names in your report to the sections below.
At a glance
Instructional
The link alone should still make sense when read out of line.
Why this matters
- Screen readers can list all links; “click here” repeated is useless.
- Voice control users need unique speakable names.
Where this shows up
Use this list to spot the same pattern on your templates and key URLs.
Content
- “Read more” without article title
- Adjacent “learn more” links to different URLs
Navigation
- Multiple “Details” links in tables
Fix priority — address first
- CTA rows, tables of actions, and footer link clusters.
Fix priority — can follow
- Links where programmatic context is exposed and consistent (still prefer clear text).
Who is affected
Screen reader users scanning links out of context and people who need predictable link text.
Fix this in your platform
Stack-specific steps, pitfalls, and verification. Core issues link under /wordpress, /shopify, /react, or /nextjs; all issues also have /fix/… URLs.
Examples
Replace “read more” with “read more about return policy”. Ensure adjacent context is programmatically associated if design requires it.
Examples (bad vs good)
Bad
`Read more`
Good
`Read more about free returns`
How to fix
- Find vague links in the report.
- Rewrite visible text to include purpose: “Read full return policy”.
- If design constrains text, use visually hidden text or aria-label carefully.
- Rescan.
Platform-specific notes
Where this often comes from on common stacks—and what to change.
- WordPress
- Excerpt “read more” links should include the post title in visually hidden or visible text.
Common mistakes
- Relying on surrounding paragraph text without aria-labelledby.
- Using the same label for different destinations.
How to verify the fix
- List links with a screen reader rotor.
- Check each label is unique or clearly distinguished.
- Rescan.
Related: 2.4.4 Link Purpose (In Context).
Related guides
Run another scan
After you ship a fix, rescan the same URL and keep both report links to compare.
Broader topics
Principles on these pages overlap with HTML issues: PDFs for documents and downloads, mobile for touch, contrast, and small screens.
Related issues
Next steps
Keep the scan, fix, rescan loop going
Ship a fix, then run another scan on the same URL. Each run gets its own report link so you can compare before and after.
Open scan