Use descriptive link text
SkillMedialink-text is a skill for AI agents that reviews rendered HTML, interactive components, and design-system patterns for descriptive link text. It checks that links have clear wording so users know where they lead, starting with native semantics and then looking at keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
Available today. Use it from your connected AI after setup.
No other account needed.
Have the rendered HTML, interactive component, or design-system pattern to be reviewed available.
Then ask your AI: use the Use descriptive link text skill
What your AI can do with it
- Review rendered HTML for descriptive link text
- Check native semantics before other inspection
- Inspect keyboard behavior of links
- Check focus flow across interactive components
- Verify accessible names on links
- Review screen-reader output where relevant
Getting started
- Have the rendered HTML, interactive component, or design-system pattern to be reviewed available.
- Add the link-text skill to the agent's available skills.
- Ask the agent to review the material for descriptive link text.
- Review the agent's findings, which will check native semantics first, then keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/link-text/SKILL.md and read by ahel’s review.
Screen reader users navigate by listing all links—'click here' repeated 10 times tells them nothing, while descriptive links let them jump directly to relevant content.
Quick Reference
- Avoid generic text like 'click here', 'read more', 'learn more'
- Link text should describe the destination without surrounding context
- Use links for navigation to a URL, not for in-page actions
- Use aria-label when visual design requires short text
- Include file type and size for download links
Check
Review all links and verify text describes the destination. Avoid generic phrases like 'click here', 'read more', 'learn more' without additional context. Check that screen readers can understand link purpose out of context.
Fix
Replace generic link text with descriptive phrases. Use aria-label or aria-labelledby when visual design requires short text but context is needed. Ensure each link's purpose is clear from its text alone.
Explain
Explain how screen reader users often navigate by listing all links on a page, and why 'click here' repeated multiple times provides no useful information about where each link leads.
Code Review
Review the rendered markup and interactive states that affect Use descriptive link text. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/accessibility/link-text
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Aug 2026
Questions
- When should the link-text skill be used?
- Use it when reviewing rendered HTML, interactive components, or design-system patterns related to using descriptive link text.
- What does the skill check first?
- It checks native semantics first, then inspects keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
- What is the goal of the review?
- To confirm links have clear, descriptive text so users know where they lead.
Advanced
- Item type
- skill
- Key
link-text- Source
- github.com/thedaviddias/front-end-checklist