Ensure links have descriptive accessible names
Accessibility isn’t only about avoiding violations — it’s about ensuring your product can be used confidently by everyone. This guide explains the principle of this rule, shows what goes wrong in real-world code, and provides a verified fix that meets WCAG and the European Accessibility Act (EAA).
Why this matters and how to fix it
Why this matters
Links like 'Click here' or 'Read more' are meaningless to screen reader users out of context. Descriptive link text makes navigation easier.
How to fix this issue
Ensure every link describes its destination or action. Use aria-labels only when visible text isn’t sufficient.
Developer guidance
Test links out of context using a screen reader’s list of links — each should make sense on its own.
Code examples
Incorrect Implementation
<a href='/report'>Read more</a>Correct Implementation
<a href='/report'>Read the 2025 Accessibility Report</a>
Trusted by organizations across Europe working toward WCAG and EAA conformance