Meaningful links (avoid “click here”)
A short, practical UI accessibility note for games and web UIs. No tracking.
Try the micro-demo: meaningful-links-demo.html
It compares vague link text (“Click here”, “Read more”) vs descriptive links that still make sense in a list of links.
What goes wrong
Many apps and sites use links like “Click here”, “Here”, or “Read more”. Those can look fine in a paragraph… but they break down in common real navigation modes.
The quick test: “links list”
Screen reader users often jump through links or open a list of links. If your page has multiple “Read more” links, the list becomes ambiguous and slow.
Why it matters
- Screen readers: link navigation is a primary browsing mode.
- Keyboard users: scanning links with Tab is faster when link text is descriptive.
- Voice control / switch users: “Click here” can be unclear and harder to target.
- Everyone: descriptive links are easier to skim.
A safe pattern (minimal)
- Put the topic/destination in the link text.
- Avoid “click” language when you can (not everyone clicks).
- If you must reuse text like “Read more”, make it specific: “Read more about performance improvements”.
Example rewrite:
Bad:
Read more
Better:
Read version 2.1 release notes
Also OK:
Read more about performance improvements
The goal: link text that still makes sense out of context.