skills.rest
scamai
scamaiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

link-purpose

Identifies problematic link text and recommends WCAG 2.4.4 compliant fixes for UI components.

Updated Aug 27, 2026
Search Tags:#accessibility#a11y#aria#link-text#wcag-2.4.4#contextual-links
One-click install
npx skills add https://github.com/scamai/scamai-landing --skill link-purpose-scamai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: link-purpose
Source: https://github.com/scamai/scamai-landing/tree/main/.agents/skills/link-purpose
Command: npx skills add https://github.com/scamai/scamai-landing --skill link-purpose-scamai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes link text to ensure the purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, aligning with WCAG 2.4.4 guidelines.

Core Features & Use Cases

  • Detects generic link text like "click here" or "read more" and ambiguous links.
  • Recommends fixes: descriptive link text, sr-only context, ARIA labels, or linking headings.
  • Scans common UI structures (cards, navigation, lists) to improve accessibility across pages.

Quick Start

Audit a UI for WCAG 2.4.4 link purposes and generate remediation recommendations.

Frequently Asked Questions about link-purpose

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

FAQPage Schema
How do I fix WCAG 2.4.4 link purpose issues for ambiguous links?▼

Audit and fix WCAG 2.4.4 link purpose issues by replacing generic text with descriptive links, adding sr-only context, applying ARIA labels, or wrapping headings in links to clarify intent for screen readers.

Why do generic links like Read more fail WCAG 2.4.4 accessibility checks?▼

Generic links like Read more fail WCAG 2.4.4 because they lack programmatically determined context, preventing screen reader users from distinguishing the target destination among multiple similar links.

How do I make icon-only links accessible in UI cards and navigation?▼

Make icon-only links accessible by applying ARIA labeling attributes or providing sr-only text, ensuring the link purpose is programmatically available for assistive technologies navigating cards and lists.

Can I audit contextual links across card and list components for screen reader compatibility?▼

Yes, audit contextual links across card and list components to verify screen reader compatibility, generating remediation recommendations for structures missing descriptive text or ARIA attributes.

What is the best way to provide programmatically determined context for ambiguous link text?▼

Provide programmatically determined context for ambiguous link text by using sr-only context, ARIA labels, or linking headings, ensuring link purpose is clear from the text or its immediate context.

Related Skills

Explore More Software Engineering Skills→
timsvoicetimsvoice

specimin-ui-accessibility

Audit and fix generated UI code for WCAG 2.1 AA compliance.

Community
Advanced
coastdigitalgroupcoastdigitalgroup
2

accessible-main-navigation

Implement accessible keyboard-friendly main navigation with ARIA attributes and skip links.

Official
Intermediate
zinohomezinohome
1

accessibility-auditor

Audit web pages for WCAG 2.1 compliance and implement accessibility fixes.

Community
Advanced
Community-AccessCommunity-Access
387

Link Checker

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

Official
Intermediate