Loading...
Loading content...
Loading content...
Link text must be descriptive on its own (no 'click here').
Why it matters: Screen reader users often browse by links list, so links need to make sense out of context.
A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.
What This Means: This success criterion is a stricter version of 2.4.4 (Level A). At Level AAA, the purpose of each link must be identifiable from the link text alone, without needing surrounding context. This means link text must be descriptive and self-contained, avoiding generic phrases like 'click here', 'read more', or 'here'.
Why It's Important: Screen reader users often navigate by jumping from link to link, reading only the link text in a list. If link text is generic or relies on context, users cannot determine the link's purpose when reading it in isolation. This makes navigation difficult and time-consuming. By requiring descriptive link text, we ensure links are understandable out of context.
Use descriptive link text that makes sense on its own (e.g., 'Download WCAG 2.2 guide' instead of 'Download' or 'click here'). Avoid generic phrases. If multiple links have similar purposes, make each one unique and descriptive. Use aria-label to provide additional context when necessary, but ensure the visible link text is still meaningful.
This criterion ensures that screen reader users can access and understand the content, improving their overall experience and ability to use the website effectively.
This criterion ensures that users with cognitive disabilities can access and understand the content, improving their overall experience and ability to use the website effectively.
Impact: When this criterion is properly implemented, it removes barriers for these user groups and creates a more inclusive web experience for everyone.
Link text like 'click here' or 'read more' doesn't describe the purpose.
<p>For more information, <a href="/about">click here</a>.</p>Link text clearly describes the destination or action.
<p>For more information, see our <a href="/about">about page</a>.</p>This success criterion benefits the following user groups:
Tip: Use this checklist during development and testing to ensure all requirements for 2.4.9 Link Purpose (Link Only) are met. Check off items as you complete them.
Note: These are official W3C resources for 2.4.9. For the most up-to-date information and detailed technical guidance, always refer to the official W3C documentation.
Implementing 2.4.9 Link Purpose (Link Only) correctly requires understanding your specific context. Code solutions vary significantly based on multiple factors:
HTML, React, Vue, Angular, PHP, Python, and other frameworks each have different patterns and best practices.
Server-side rendering, client-side rendering, static generation, and hybrid approaches require different solutions.
Your existing components, styling approach, and UI library influence how accessibility must be implemented.
Your specific user base, content type, and interaction patterns determine the most appropriate implementation.
We provide tailored implementation guidance by analyzing your specific technology stack, coding patterns, design system, and project requirements. Our team reviews your codebase and provides custom solutions that integrate seamlessly with your existing architecture.
Get Custom Implementation HelpPart of
Operable PrincipleGuideline
2.4 Navigable