I Tested 9 Free Accessibility Tools on the Same Website. Here's What Each One Actually Caught.
Giriprasad Patil·· 14 min read·Tools & Resources
Every tool in this space claims to "check your site for WCAG violations."
They don't all find the same things.
I ran 9 free accessibility tools on the same website — a mid-size e-commerce site with known violations planted across different categories. Here's what each tool found, what it missed, and how to combine them for the highest possible free coverage.
**The most important thing to know going in:**
> 🔑 **Coverage varies massively between tools.** axe-core alone detects ~57% of WCAG 2.2 criteria. Lighthouse reaches ~42%. WAVE ~40%. Multi-engine tools like ADAGuard — running 23 independent test modules — reach ~78% automated coverage. The rest require human judgment regardless of which tool you use. Your goal is to start with the highest automated coverage possible, then fill the gap with manual testing.
---
## The 30-Second Verdict (For Skimmers)
| Tool | Best For | Catches | Misses |
|------|----------|---------|--------|
| **ADAGuard** | Full-site baseline | **23 test modules** (22 custom + axe-core), multi-page, fix guidance | Manual criteria |
| **WAVE** | Visual element inspection | Spatial context, structure | Single page only |
| **Lighthouse** | Dev workflow | Quick per-page score | Not a site scanner |
| **axe DevTools** | Element-level dev testing | Low false-positives | Paid version for guided tests |
| **Accessibility Insights** | Structured manual testing | Guided manual checklist | Automated = axe only |
| **WebAIM Contrast Checker** | Contrast spot-checks | Exact ratio for any 2 colors | Doesn't scan pages |
| **Colour Contrast Analyser** | Design-time contrast | Any on-screen color via eyedropper | Desktop app only |
| **NVDA** | Windows screen reader testing | Real user behavior | Requires skill to use |
| **VoiceOver** | Mac/iOS screen reader testing | Real user behavior | Apple ecosystem only |
---
## Category 1: Full-Site Automated Scanners
These crawl multiple pages and return a report — the only way to understand your compliance picture at scale.
---
### ADAGuard (Free Tier)
**What it scans:** WCAG 2.1 and 2.2 Level AA, ADA compliance, Section 508, plus bonus Level AAA checks (2.5.5, 2.3.3, 2.4.13) — on every plan including Free. Up to 5 pages per scan on the free tier.
**Why it's architecturally different from other tools:**
> 🔑 **ADAGuard runs 23 independent test modules simultaneously — 22 custom checkers plus axe-core — achieving ~78% automated WCAG 2.2 AA coverage.** axe-core alone reaches ~57%. Lighthouse ~42%. WAVE ~40%. That's significantly more automated detection in one scan.
Those 22 custom checkers each specialise in a specific domain:
| Checker Module | What It Tests |
|---------------|--------------|
| **Images** | Alt text quality, decorative vs. informational classification |
| **Color Contrast** | WCAG 1.4.3 text contrast + 1.4.11 non-text contrast ratios |
| **Color Use** | Color used as sole means to convey information |
| **Forms** | Labels, field associations, error messages, required markup |
| **Headings** | H1–H6 hierarchy, skipped levels, multiple H1 detection |
| **Links** | Anchor text quality, vague "click here" / "read more" patterns |
| **ARIA** | Role correctness, attribute validity, redundancy detection |
| **Keyboard** | Focus indicators, keyboard traps, focusable element detection |
| **HTML Structure** | Landmarks, `lang` attribute, page title, semantic regions |
| **Multimedia** | Video captions, transcripts, audio descriptions |
| **Interactive** | Buttons, controls, custom widget accessibility |
| **Mobile** | Mobile-specific accessibility patterns and failures |
| **Reflow** | Content reflow at 320px / 400% zoom (WCAG 1.4.10) |
| **Tables** | Table structure, headers, caption, scope attributes |
| **Time & Motion** | Session timeouts, auto-play, pause/stop controls |
| **Touch Targets** | Minimum 24×24px target size (WCAG 2.2 — 2.5.8) |
| **WCAG 2.2** | All 9 new criteria introduced in the October 2023 update |
| **Non-text Contrast** | CSS border contrast on UI components — buttons, inputs, focus rings (WCAG 1.4.11) |
| **Content on Hover/Focus** | Tooltip and popup content behavior — dismissible, hoverable, persistent (WCAG 1.4.13) |
| **Text Spacing** | CSS text spacing override test — detects content clipping and collapse (WCAG 1.4.12) |
| **Multiple Ways** | Search, navigation, sitemap and breadcrumb presence detection (WCAG 2.4.5) |
| **Broken Links** | Identifies dead links that create navigation dead-ends |
Plus **axe-core** as the 23rd module — catching anything the custom modules don't flag, with industry-standard low false-positive rates.
Running axe-core alone (as Lighthouse and most browser extensions do) means you're getting 1 of 23 modules. ADAGuard runs all 23 in parallel on every scan.
**What it caught in the test:**
- All 12 images missing alt text ✅
- 8 of 9 form fields with label violations ✅
- 14 color contrast failures (text + UI components) ✅
- Missing `lang` attribute ✅
- 3 heading hierarchy violations ✅
- 6 links with non-descriptive anchor text ✅
- Focus indicator failures (WCAG 2.2 — 2.4.11) ✅ ← most tools miss this
- ARIA misuse patterns across 4 components ✅
**What it missed:** Cognitive accessibility issues, whether the focus order made logical sense in context, whether error messages were actually helpful.
**Standout features:**
- **50+ automated accessibility checks** across 22 custom modules — on the free tier
- **JavaScript rendering** included on all tiers — catches violations in dynamic, JS-driven content that static scanners miss entirely
- **Fix guidance per violation** — exact element, actual ratio vs. required ratio, and copy-paste CSS or HTML to fix it. Turns a violation list into a developer task list.
- **Bonus AAA checks** (2.5.5, 2.3.3, 2.4.13) run on all plans — most tools don't touch AAA at any price point
**Pricing context:** Siteimprove charges ~$28,000/year for comparable enterprise scanning. ADAGuard Professional is $1,548/year — 97% less, with more features. axe DevTools Pro charges $45/user/month; ADAGuard Professional is a flat $129/month for teams of up to 5.
**Free tier limits:** 1 scan/month, 5 pages. → Paid plans unlock full-site crawling, scheduled monitoring, authenticated scanning, and compliance certificates.
**[→ Run a free scan](https://adaguard.io)**
---
### WAVE by WebAIM
**What it is:** One of the oldest free accessibility checkers — been around since 2001. Enter a URL, get a visual overlay on the page showing exactly where errors appear.
**What it caught in the test:**
- Image alt text issues ✅
- Form label problems ✅
- Heading structure errors ✅
- Landmark/region issues ✅
- Contrast failures ✅ (with visual flag on the element)
**What it missed:** WCAG 2.2 criteria (Focus Appearance, Target Size) — WAVE is primarily aligned to WCAG 2.1.
**Biggest limitation:** One page at a time. No crawling, no multi-page reporting. For a 50-page site, you'd submit each URL manually.
**Best for:** Developers and designers who want to visually pinpoint *where on the page* issues are, rather than getting a list of CSS selectors.
**[→ wave.webaim.org](https://wave.webaim.org)**
---
### Google Lighthouse (Chrome DevTools)
**What it is:** Google's open-source auditing tool, built into Chrome. Press F12 → Lighthouse tab → run the Accessibility audit.
**What it caught in the test:**
- Standard axe-core violations ✅ (same engine as axe DevTools)
- Color contrast ✅
- Form labels ✅
- Alt text ✅
**What it missed:** Anything axe-core misses. Also: the score is misleading.
> ⚠️ **The Lighthouse score problem:** A score of 85/100 doesn't mean 85% of issues are fixed. It means 85% of the *auditable items* passed — and those items represent only a fraction of all WCAG criteria. Teams have shipped sites with Lighthouse 90+ that still got sued.
**Best for:** Quick per-page checks during development. Already in DevTools — zero setup.
---
## Category 2: Browser Extensions
These run inside your browser — meaning they work on pages that require login, staging environments, and localhost. Essential for testing behind authentication.
---
### axe DevTools Browser Extension (Free) — Deque Systems
**What it is:** The free browser extension from Deque Systems — the company that built the axe-core engine that powers Lighthouse, ADAGuard, and most other tools.
**What it caught in the test:**
- Same violations as Lighthouse (same engine) ✅
- Slightly better reporting — violations show in the Elements panel alongside your DOM ✅
- Very low false-positive rate ✅
**Why it matters:** axe-core is the industry standard. Its rules are carefully designed to only flag violations it's confident about. If axe flags it, it's almost certainly a real violation.
**What it misses:** The paid axe DevTools Pro adds guided testing for manual criteria (keyboard navigation, screen reader interaction, focus order). Free version is automated-only.
**Best for:** Developers testing pages behind a login, or doing element-level investigation on specific components.
---
### Accessibility Insights for Web — Microsoft
**What it is:** A browser extension from Microsoft with two modes:
- **FastPass** — automated axe-core check (same as above)
- **Assessment** — step-by-step guided manual testing
**Why Assessment mode is special:**
It walks you through a structured checklist for criteria that can't be automated — keyboard navigation, focus order, screen reader behavior, time-based content. Each criterion has instructions explaining what to test and what to look for.
This is the best free tool for structured manual auditing. Nothing else in the free tier does this as well.
**Best for:** QA engineers and accessibility specialists doing thorough manual audits who want a guided workflow rather than a blank checklist.
**[→ accessibilityinsights.io](https://accessibilityinsights.io)**
---
### WAVE Browser Extension
Same analysis as the WAVE website tool, but runs locally in your browser — so it works on:
- Pages that require login
- Staging/preview environments
- localhost
**Best for:** Designers testing their work in-browser, or anyone who needs WAVE's visual overlay on authenticated pages.
---
## Category 3: Color Contrast Checkers
Color contrast is the #1 WCAG failure — found on 83% of websites in WebAIM's annual audit. These tools exist to check it before it becomes a violation.
---
### WebAIM Contrast Checker
**What it does:** Enter two hex color codes → get the exact contrast ratio → see pass/fail against WCAG AA and AAA thresholds for normal and large text.
**When to use it:** Any time you're choosing or approving text/background color combinations in your design system.
**Limitation:** Requires you to know hex codes. Doesn't work on rendered text-on-image combinations where the "background" isn't a single color.
**[→ webaim.org/resources/contrastchecker](https://webaim.org/resources/contrastchecker)**
---
### Colour Contrast Analyser — TPGi (Desktop App, Free)
**What it does:** A desktop app (Mac + Windows) with an **eyedropper tool** — pick any two colors on your screen and instantly get the contrast ratio.
**Why it's better than WebAIM for some use cases:** You don't need hex codes. Pick rendered text on a complex background, text-on-image, or any UI state that's hard to inspect in code.
**Best for:** Designers checking contrast in Figma, rendered browsers, or any context where extracting hex codes is annoying.
**[→ tpgi.com/color-contrast-checker](https://www.tpgi.com/color-contrast-checker/)**
---
## Category 4: Screen Readers
No automated tool can fully replicate what a real screen reader user experiences. Screen reader testing reveals issues that scanners will never catch — confusing announcements, illogical tab order, missing context.
---
### NVDA (NonVisual Desktop Access) — Windows, Free
**What it is:** The most widely used free screen reader for Windows. Open source, actively maintained.
**Key stat:** According to WebAIM's Screen Reader User Survey, NVDA is used by 40%+ of screen reader users globally. If you only test with one screen reader on Windows, test with NVDA.
**Best pairing:** NVDA + Firefox for the most representative Windows user experience.
**How to start:** Download from [nvaccess.org](https://www.nvaccess.org). Press Insert + F7 to pull up a list of headings and links — a fast way to check document structure.
**Download:** nvaccess.org (free, donations appreciated)
---
### VoiceOver — Mac and iOS (Built-In, Free)
**What it is:** Apple's built-in screen reader. Free on every Mac, iPhone, and iPad.
**Activate on Mac:** Cmd + F5
**Activate on iPhone:** Triple-click the side or home button
**Why test with it:** VoiceOver + Safari is one of the most common screen reader + browser combinations among mobile users. If you have significant iOS traffic, VoiceOver testing is essential.
---
### TalkBack — Android (Built-In, Free)
**What it is:** Google's built-in Android screen reader. Enable in Settings → Accessibility → TalkBack.
**Best for:** Mobile testing on Android devices. If your site is heavily used on mobile, TalkBack testing should be in your workflow.
---
## What No Free Tool Can Catch
Understanding the ceiling helps you know where to invest manual effort:
**Cognitive accessibility** — Is your content written in plain language? Are your error messages helpful? Are instructions clear?
**Logical focus order** — Does the Tab key move through your page in a logical sequence? Automated tools can detect whether focus works at all — not whether the sequence makes sense.
**Screen reader announcement quality** — Do ARIA attributes create a coherent experience when read aloud, or do they create confusing, redundant, or missing announcements?
**Time-based barriers** — Does your session timeout give users with slow reading speeds enough time to complete tasks?
**Motion and animation** — Do animations trigger issues for users with vestibular disorders? (Tools can check `prefers-reduced-motion` support — not whether the animations themselves are problematic.)
**All of the above require manual testing.** Often with real users who have disabilities. Automated tools are a floor, not a ceiling.
---
## The Recommended Free Stack (Prioritized)
**For a first-time audit:**
1. **ADAGuard** — full-site score and violation list with fix guidance
2. **axe DevTools** — element-level investigation on key pages
3. **Keyboard navigation test** — Tab through manually (no tool needed)
4. **WebAIM Contrast Checker** — verify any flagged color combinations
**For an ongoing workflow:**
1. **ADAGuard** (scheduled scans) — catch new violations as they're introduced
2. **WAVE extension** — quick checks during content updates
3. **NVDA or VoiceOver** — spot-check any new interactive components
**For a thorough manual audit:**
1. Run **ADAGuard** for automated baseline
2. Use **Accessibility Insights Assessment mode** for guided manual criteria
3. Test with **NVDA + Firefox** and **VoiceOver + Safari**
4. Document everything for compliance records
---
## When to Go Beyond Free
Free tools are the right starting point. But they have limits that matter as your site grows:
| Need | Free (ADAGuard) | Starter $49/mo | Professional $129/mo | Business $249/mo |
|------|----------------|----------------|---------------------|-----------------|
| Full-site scanning | 5 pages/scan | 50 pages/scan | 200 pages/scan | 1,000 pages/scan |
| Scans per month | 1 | 4 (weekly) | 30 (daily) | 150 (custom) |
| Websites | 1 | 1 | 3 | 10 |
| Scheduled monitoring | ❌ | Weekly | Daily/Weekly/Monthly | Custom (cron-like) |
| Authenticated scanning | ❌ | ❌ | ✅ | ✅ |
| Compliance certificates | ❌ | ✅ | ✅ | ✅ |
| PDF/CSV/JSON export | ❌ | ✅ | ✅ | ✅ |
| VPAT reports (Section 508) | ❌ | ❌ | ✅ | ✅ |
| White-label reports | ❌ | ❌ | ❌ | ✅ |
| API access | ❌ | ❌ | 100 req/hr | 500 req/hr |
| Data retention | 7 days | 30 days | 90 days | 1 year |
> 💡 **Pricing context:** All plans — including Free — run the same 23 test modules with ~78% WCAG 2.2 AA coverage. You're not getting a worse scanner on lower tiers. You're getting fewer scans and pages per scan.
If you're a freelancer doing a one-time audit — the free stack works fine. If you're an agency managing client sites, or a business whose site changes frequently — you need monitoring, not just scanning.
---
## Share This (Tweet-Ready Lines)
> *"I tested 9 free accessibility tools on the same website. They didn't all find the same violations. Here's the honest breakdown of what each one caught and missed."*
> *"A Lighthouse score of 90/100 doesn't mean 90% of accessibility issues are fixed. It means 90% of the checkable items passed — and those represent only a fraction of WCAG criteria. Don't confuse the score with compliance."*
> *"No automated accessibility tool catches 100% of WCAG violations — even the best tools reach ~78%. The remaining 22% require human testing. Tools are the floor, not the ceiling."*
> *"Most accessibility scanners run 1 test engine (axe-core). ADAGuard runs 23 — 22 purpose-built checkers covering images, contrast, forms, ARIA, keyboard, headings, multimedia, and more — plus axe-core. Coverage is not all equal."*
---
## Related Reading
- [How to Check ADA Compliance in 10 Minutes (Step-by-Step)](/blogs/how-to-check-ada-compliance)
- [Color Contrast: The Most Common WCAG Failure and How to Fix It](/blogs/color-contrast-accessibility-checker)
- [WCAG 2.2: 9 New Rules Most Tools Haven't Caught Up With Yet](/blogs/wcag-2-2-changes)
- [ADA Website Lawsuits: What They Cost and How to Avoid One](/blogs/ada-website-lawsuit-cost)
**External references:**
- [WebAIM Million Annual Report](https://webaim.org/projects/million/)
- [WebAIM Screen Reader User Survey #10](https://webaim.org/projects/screenreadersurvey10/)
- [Deque axe-core on GitHub](https://github.com/dequelabs/axe-core)
- [W3C Accessibility Evaluation Tools List](https://www.w3.org/WAI/test-evaluate/tools/list/)
---
## Start With a Full-Site Baseline — Free
**[→ adaguard.io — free scan, no account required](https://adaguard.io)**
Multi-page scan. Compliance score. Every violation ranked by severity with exact fix instructions. The best starting point before you pick up any other tool in this list.
---