link-purpose

Add context so each link's purpose is clear: append visually hidden text like <span className="sr-only">about {title}</span>, use aria-label or aria-labelledby, or make the link text itself descriptive. Linking the heading instead is often the best practice.

Violations include generic text like "click here" or "learn more" without context, identical link text pointing to different destinations, image-only links without alt text, raw URLs as link text, and download links missing file type or size information.

Yes. It detects framework-specific link components including React Router's <Link>, Next.js <Link>, Vue's <router-link>, and Nuxt's <nuxt-link>, as well as repeated link patterns generated inside .map() loops or v-for directives.

Rarely. The exception applies when the link's purpose would be ambiguous to all users, such as game interfaces with intentional mystery like "Door 1" and "Door 2". When in doubt, make link text descriptive since that satisfies the stricter Level AAA criterion.

Screen reader users commonly navigate by jumping link to link or opening a links list (Insert+F7 in NVDA, VO+U in VoiceOver), which strips away surrounding visual context. Generic text like "read more" repeated across a page gives them no way to distinguish destinations.