WAVE vs Deque axe 2026: Two Free Tools, Different Strengths
Updated June 2026 · 7 min read
The Bottom Line Up Front
WAVE and axe are both free, both check source code (not overlays), and both catch real WCAG violations. WAVE is better for visual, on-page auditing. axe is better for developer workflows and CI/CD integration. Accessibility professionals typically use both — they have different strengths and catch slightly different issue sets.
WAVE vs axe: Side-by-Side
| Factor | WAVE (WebAIM) | axe / Deque |
|---|---|---|
| Cost | Free (API: $4K+/yr) | Free (Pro: $2,400+/yr) |
| Type | Browser extension | Browser ext + open-source library |
| Interface | Visual overlay on page | DevTools panel + code-level output |
| CI/CD integration? | No | Yes — axe-core npm library |
| WCAG rule set | WCAG 2.1 AA (own rule set) | WCAG 2.1 AA (axe-core, industry standard) |
| Results format | Visual icons on page | Structured pass/fail report with element refs |
| Non-dev friendly? | Yes — very visual | Less so — code-focused |
| Used in other tools? | No | Lighthouse, Accessibility Insights, many more |
| Best for | Visual page audits, non-devs | Developer workflows, CI/CD, automated testing |
How WAVE Works
WAVE is a browser extension from WebAIM (Utah State University). When you activate it on any page, it overlays colored icons directly on the rendered page — red icons for errors, yellow for alerts, green for correctly implemented features. You can see exactly where each issue appears in context, click any icon to get an explanation, and understand the structural hierarchy of your page.
Confirmed WCAG failures: missing alt text, empty form labels, broken ARIA, keyboard traps
Items needing manual review: suspicious link text, redundant links, layout tables
Correctly implemented accessibility: present alt text, ARIA landmarks, language attributes
Heading hierarchy, page regions, list markup
Color contrast ratios for text elements against their backgrounds
WAVE's visual approach makes it uniquely accessible to non-developers. A content editor, QA tester, or accessibility coordinator can use WAVE effectively without understanding how to read HTML. That's one of its biggest advantages — accessibility auditing doesn't have to live only in the developer's domain.
How Deque's axe Works
Deque Systems created axe-core — the open-source JavaScript accessibility testing engine that has become the de-facto industry standard. axe-core powers Google Lighthouse's accessibility checks, Microsoft Accessibility Insights, GitHub's accessibility scanning, and dozens of commercial accessibility tools including RatedWithAI.
Deque offers several axe products:
axe DevTools (free browser extension)
Installs in Chrome and Firefox as a DevTools panel tab. Run it on any page to get a structured pass/fail report with element references, WCAG rule IDs, and remediation guidance. Unlike WAVE, results appear in a panel alongside your browser's standard DevTools — better for developers already working in DevTools.
axe-core (open-source npm library)
The JavaScript library you can import into test suites (Jest, Cypress, Playwright) or CI/CD pipelines. axe-core lets you automate accessibility checks on every deploy — failing the build if new WCAG violations are introduced. This is WAVE's biggest blind spot: WAVE has no CI/CD integration path.
axe DevTools Pro (paid)
Paid extension adding guided testing workflows, AI-assisted remediation, intelligent guided tests that catch issues automated scanning misses, and team collaboration features. Starting around $2,400/year per seat. Worth considering for dedicated accessibility engineers; overkill for most teams.
Do WAVE and axe Catch Different Issues?
Yes — and this is the key reason accessibility professionals use both tools together. Despite both checking WCAG 2.1 AA, WAVE and axe use different rule implementations and flag different edge cases. Studies comparing accessibility tool coverage consistently find that WAVE + axe together catches approximately 10–15% more issues than either tool alone.
Where WAVE catches more
- Heading hierarchy issues (skipped levels, missing H1)
- Redundant or suspicious link text patterns
- Empty links and buttons WAVE's visual pass catches in context
- Some contrast issues on complex backgrounds
Where axe-core catches more
- ARIA attribute validation (invalid values, role conflicts)
- Complex landmark and region violations
- Specific SC 4.1.2 violations axe's rule set is more rigorous on
- Dynamic content violations via JavaScript testing hooks
Both tools miss roughly 30–40% of WCAG 2.1 AA issues that require human judgment — dynamic content interactions, cognitive accessibility, complex navigation patterns, and context-dependent violations that automated scanning can't evaluate. Running both tools gives you better automated coverage, but manual testing is still essential.
The Professional Recommendation: Use Both
Since both WAVE and the axe DevTools extension are free, there's no reason to pick one over the other. The professional accessibility testing workflow typically looks like this:
axe-core in CI/CD
Prevent new violations from being deployed. axe-core integrated into your test suite catches issues before they reach production — something neither WAVE nor the browser extension can do.
WAVE for visual auditing
When reviewing pages manually, WAVE's visual overlay makes it fast to spot structural issues, heading problems, and contextual issues that benefit from seeing them on the rendered page.
axe DevTools for code-level detail
When you need precise element references and WCAG rule citations to document findings or assign remediation work, axe DevTools gives more structured output than WAVE.
Human testing for the rest
For keyboard navigation, screen reader compatibility, cognitive accessibility, and complex interaction patterns — neither tool can fully substitute for testing with real assistive technology.
Need site-wide monitoring, not just page-by-page checks?
WAVE and axe both work page by page. RatedWithAI uses axe-core to automatically scan your entire site and monitor it continuously — no manual work required.
Sponsored
Also audit your site's full technical health
SEMrush Site Audit checks 130+ issues — missing alt text, broken links, slow pages. Free crawl up to 100 pages, no credit card required.
Frequently Asked Questions
Is Deque axe-core open source?
Yes. axe-core is open-source under the Mozilla Public License 2.0 and available on GitHub. Anyone can use axe-core in their own tools, products, or test suites — and many commercial accessibility tools do exactly that. Deque's commercial products (axe DevTools Pro, axe Monitor) add proprietary features on top of the open-source core. The free axe DevTools browser extension is the most accessible way for developers to use axe-core without writing code.
Does Google Lighthouse use axe or WAVE?
Google Lighthouse uses axe-core (Deque's engine) for its accessibility checks. When you run a Lighthouse audit — either in Chrome DevTools, via PageSpeed Insights, or from the command line — the accessibility results come from axe-core. WAVE is a separate, independent tool from WebAIM. They use different rule implementations, which is why comparing results between Lighthouse/axe and WAVE sometimes shows different findings.
Can axe find all WCAG 2.1 AA violations?
No. Axe-core's documentation explicitly states that automated testing can find approximately 57% of WCAG issues. The remaining ~43% require human judgment — things like whether link text is descriptive in context, whether complex navigation is understandable to cognitive accessibility users, or whether interactive components work correctly when navigated with a screen reader. Automated testing with axe is a necessary starting point, not a complete compliance solution.
What is the difference between axe DevTools free and Pro?
The free axe DevTools browser extension gives you automated WCAG scanning in Chrome/Firefox DevTools with element references and remediation guidance. axe DevTools Pro (paid) adds: Intelligent Guided Tests (semi-automated workflows that walk you through checking issues automated tools miss), AI-powered fix suggestions, issue management for tracking remediation status across your team, and advanced reporting features. Pro is valuable for dedicated accessibility engineers doing comprehensive audits. For most developers, the free version is sufficient.
Is WAVE or axe better for beginners?
WAVE is generally more beginner-friendly because of its visual, on-page overlay that shows issues in context without requiring knowledge of DevTools or browser panels. Beginners can understand WAVE results without interpreting code. The axe DevTools extension requires opening the browser's DevTools panel and reading structured reports with element references — still accessible, but more developer-oriented. Both tools include explanations of each violation. If you're new to accessibility testing and want to understand your site's issues quickly, start with WAVE.