Find links that use identical text but lead to different URLs. Review the rendered page and suggest distinct labels or consistent destinations so readers, including people using screen readers, can understand where each link goes.
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure identical links have consistent destinations. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
Run score Not tested
See how to installThis skill checks whether links with identical text point to different URLs and helps revise labels so their destinations are clear. Links to different places receive distinct wording, while links that keep the same wording are aligned to the same resource. It reviews rendered HTML and interactive states, then identifies the specific elements and labels that need attention.
Use it when a page contains several links with the same text or when reviewing link wording in shared components. It is particularly useful for checking whether people who navigate through a screen reader’s list of links can distinguish the destinations from the labels they hear.
Checks require the rendered page. Where needed, use browser accessibility tools or a screen reader to verify labels, focus, and keyboard operation as well.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
When links with identical text lead to different destinations, it creates confusion and unpredictability, especially for users who rely on a list of links to navigate.
Identify any links on the page that have identical link text but point to different URLs.
Change the link text to be unique for each destination, or ensure that identical text always leads to the same resource.
Explain how identical link text for different destinations can mislead users, particularly those using screen readers to scan a list of links.
Review the rendered markup and interactive states that affect Ensure identical links have consistent destinations. 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/rules/accessibility/identical-links-same-purpose
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.