Accessibility issue guide
Some links may not be understandable to assistive technologies
Some links may not communicate clear purpose to assistive technologies, making navigation harder for users relying on spoken or non-visual output.
This issue is commonly reviewed against WCAG 2.2 AA expectations and should be paired with manual review.
- Category
- Link accessibility
- Suggested owner
- Content editor
- Estimated effort
- Medium
What This Issue Means
- This issue indicates that some links may not have clear accessible names.
- When link names are ambiguous, users may struggle to understand where a link goes before activating it.
- Automated checks can detect missing discernible names and related labeling signals.
Why It Matters
- Navigation clarity may drop across campaign pages, product hubs, and service menus.
- Ambiguous links can increase friction in lead-generation and conversion journeys.
- Teams may spend more QA effort troubleshooting inconsistent naming patterns late in release cycles.
How To Fix It
- Use descriptive link text that communicates destination, outcome, or next action.
- Add accessible labels for icon-only links and controls where visible text is absent.
- Standardize CTA naming patterns across templates so similar actions use consistent, meaningful language.
Common implementation mistakes
- Using vague text such as “click here” or “learn more” without context.
- Rendering icon-only links without accessible labels.
- Reusing identical link text for different destinations on the same page.
Manual Verification Checklist
- Review all actionable links in key templates and confirm names are understandable out of context.
- Test icon-only links with assistive technologies to verify descriptive labels are announced.
- Check repeated CTA blocks to ensure each link distinguishes destination and intent.
- Retest automated findings after content and component updates.
WCAG 2.2 AA Expectations
This issue is commonly reviewed against WCAG 2.2 AA expectations related to link accessibility, screen reader support.
Principles: Operable, Understandable
Related references: 2.4.4 Link Purpose (In Context), 4.1.2 Name, Role, Value
How WARC Helps
WARC helps identify this readiness signal through automated checks, prioritize likely business impact, and organize remediation planning in a full report.
WARC includes AI remediation prompt support for planning fixes while keeping issue IDs and categories consistent across reports.
This assessment is not a legal certification. It helps identify practical accessibility and site-quality risks against WCAG 2.2 AA expectations and common customer-journey issues.
Use AI to plan remediation safely
- Ask AI to audit link purpose clarity across buttons, icon links, and repeated CTA patterns.
- Provide component examples so recommendations match your design system and content style.
- Validate that suggested names stay concise and specific in real navigation contexts.
Prompt starter
Review these links for accessible naming quality. Suggest clearer destination-oriented labels and a manual verification checklist.
For broader workflow guidance, see AI accessibility remediation prompts.
Related Issues
FAQ
What is a discernible link name?
A discernible link name clearly communicates destination or purpose when announced by assistive technologies.
Why are ambiguous links a problem?
Users may not know which action to take, which can increase navigation errors and task abandonment.
Can automated checks catch all link-name issues?
Automated checks catch many common issues, but manual review helps confirm meaning in the full page context.
Can AI improve link naming?
AI can suggest clearer text patterns, but teams should review destination accuracy and brand voice before publishing.
Run an accessibility readiness check
Scan your website for accessibility, usability, and customer-journey signals before campaigns, redesigns, or compliance reviews.
Run an accessibility readiness check