Link Checker

Detect ambiguous link text and enforce WCAG 2.4.4 and 2.4.9 compliance.

387|42|Updated Feb 21, 2026

Search Tags:#accessibility #a11y #web development #auditing #wcag #link text

Ready to run

npx skills add https://github.com/Community-Access/accessibility-agents --skill link-checker-community-access

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Link Checker
Source: https://github.com/Community-Access/accessibility-agents/tree/main/.gemini/extensions/a11y-agents/skills/link-checker
Command: npx skills add https://github.com/Community-Access/accessibility-agents --skill link-checker-community-access

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the common accessibility failure of ambiguous link text, which hinders screen reader users by making navigation and understanding difficult.

Core Features & Use Cases

Detects vague link text: Identifies patterns like "click here", "read more", and "learn more".
Enforces WCAG standards: Aligns with Link Purpose (In Context) and Link Purpose (Link Only) criteria.
Provides clear fixes: Offers strategies like rewriting text, using aria-label, or visually hidden text.
Use Case: Reviewing a marketing webpage to ensure all calls-to-action are descriptive and understandable out of context.

Quick Start

Use the Link Checker skill to audit all links on the provided webpage URL for ambiguity.

Frequently Asked Questions about Link Checker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check my website for ambiguous link text like "click here"?▼

To check for ambiguous link text, you can audit your web pages to identify vague phrases like "click here" or "read more" and receive recommendations for rewriting them to ensure WCAG 2.4.4 compliance. This process flags non-descriptive links and suggests using ARIA attributes for clarity.

What makes link text accessible for screen reader users?▼

Accessible link text provides clear purpose out of context, avoiding vague terms like "learn more." It enforces WCAG 2.4.9 by ensuring links are descriptive or utilizing ARIA attributes and visually hidden text to improve navigation for screen reader users.

How do I fix WCAG 2.4.4 link purpose failures on my web application?▼

To fix WCAG 2.4.4 failures, rewrite ambiguous link text to be descriptive, add an `aria-label`, or include visually hidden text. This ensures the link purpose is clear either in context or when read alone by screen readers.

Does this tool detect repeated identical link text on the same webpage?▼

Yes, this tool detects repeated identical links pointing to different destinations and URL-based text. It flags these context-dependent patterns to enforce WCAG Link Purpose standards and provides detailed rewriting recommendations.

Can I audit a marketing webpage's calls-to-action for WCAG compliance?▼

Yes, you can audit marketing webpages to ensure calls-to-action are descriptive and understandable out of context. This identifies vague link text and enforces WCAG 2.4.4 and 2.4.9 standards for improved web accessibility.

What are the limitations of using ARIA attributes to fix vague link text?▼

While ARIA attributes like `aria-label` can fix vague link text, they do not address repeated identical links or URL-based text issues. Rewriting the visible text or adding visually hidden text often provides a more robust WCAG 2.4.9 compliance solution.