The Identical Link Text Audit is the audit you reach for when you already suspect a problem in this dimension and need a fast, copy-paste-able fix list. It reuses the same chrome as every other jwatte.com tool — deep-links from the mega analyzers, AI-prompt export, CSV/PDF/HTML download — but the checks it runs are narrow and specific.
Why this dimension matters
US ADA Title III web-accessibility case filings hit 4,600+ in 2024 (UsableNet annual report), and settlements in the $10–75K range have become a routine line item for any site that handles online commerce or public accommodation. Beyond legal exposure, WCAG AA conformance correlates with measurable SEO: screen-reader-friendly structure is also LLM-friendly structure, and accessible sites rank better on Google since 2020 page experience updates.
Common failure patterns
- Missing or decorative-when-content alt text — WCAG 1.1.1 Level A. Screen readers skip empty
alt=""(correct for decoration) but announce the filename for missingalt. Product images, hero images, and infographics all need descriptive alt; purely decorative images needalt="". - Contrast failures on brand colors — 4.5:1 for normal text, 3:1 for large text and UI controls. Brand guidelines often favor a 3:1-style color pair that fails WCAG AA; the fix is typically a darker variant of the accent color used only on text.
- Keyboard-trap or non-focusable custom components — any
<div onClick>withouttabindex="0"+role="button"+ keyboard handler is a Level A violation. Modern component libraries ship accessible equivalents; custom carousels, modals, and drop-downs are the repeat offenders. - Form inputs without associated labels —
<label for="id">or wrapping<label>is required. Placeholder text does not count. WCAG 1.3.1 + 3.3.2.
How to fix it at the source
Adopt an accessibility-first component library (or the WAI-ARIA Authoring Practices Guide patterns). Run axe-core or Lighthouse a11y in CI — any critical-severity regression fails the build. For legacy sites, prioritize the critical-severity items first; the fix-time per item is usually < 15 minutes and the legal exposure drops meaningfully after the top 20 fixes.
When to run the audit
- After a major site change — redesign, CMS migration, DNS change, hosting platform swap.
- Quarterly as part of routine technical hygiene; the checks are cheap to run repeatedly.
- Before an investor / client review, a PCI scan, a SOC 2 audit, or an accessibility-compliance review.
- When a downstream metric drops (rankings, conversion, AI citations) and you need to rule out this dimension as the cause.
Reading the output
Every finding is severity-classified. The playbook is the same across tools:
- Critical / red: same-week fixes. These block the primary signal and cascade into downstream dimensions.
- Warning / amber: same-month fixes. Drag the score, usually don't block.
- Info / blue: context-only. Often what a PR reviewer would flag but that doesn't block merge.
- Pass / green: confirmation — keep the control in place.
Every audit also emits an "AI fix prompt" — paste into ChatGPT / Claude / Gemini for exact copy-paste code patches tied to your stack.
Related tools
- WCAG A11y Audit — WAVE-style accessibility audit — WCAG 2.1 / 2.2 AA + 3.0 draft checks, CSV/PDF/HTML export, AI fix prompt..
- ADA Litigation Risk Score — Scores your website's ADA Title III demand-letter exposure.
- Mega Analyzer — One URL, every SEO/schema/E-E-A-T/voice/mobile/perf audit in one pass..
- Redundant Alt Text Audit — Finds images where alt duplicates adjacent heading/caption text.
Fact-check notes and sources
- W3C: WCAG 2.1 Quick Reference
- Deque: axe-core rules reference
- WebAIM: Million survey — top-1M home-page a11y benchmarks, published annually
- UsableNet: Annual ADA Digital Accessibility Lawsuit Report
This post is informational and not a substitute for professional consulting. Mentions of third-party platforms in the tool itself are nominative fair use. No affiliation is implied.
