axe DevTools vs UserWay 2026: Developer Tool vs AI Overlay
Updated June 2026 · 8 min read
The Core Distinction (Read This First)
axe DevTools and UserWay aren't competing in the same category. axe DevTools finds real WCAG violations in your source code so developers can fix them permanently. UserWay installs an AI widget that attempts to patch your site at runtime without touching the code. The compliance evidence — and the lawsuit record — strongly favors the fix-it approach.
axe DevTools vs UserWay: Side-by-Side
| Factor | axe DevTools (Deque) | UserWay |
|---|---|---|
| Type | Developer auditing tool (browser extension + CI) | AI overlay widget |
| Cost | Free browser extension; paid Pro from ~$100/seat/yr | $49+/month |
| How it works | Scans DOM, reports WCAG violations in DevTools panel | Injects JS widget that patches rendering at runtime |
| Fixes your code? | No — but shows exactly what to fix and where | No — runtime patches only, source code unchanged |
| Screen reader support? | Fixes remove actual barriers for AT users | Documented conflicts with JAWS, NVDA |
| CI/CD integration? | Yes — axe-core npm package, GitHub Actions | No developer integration |
| Continuous monitoring? | No (manual per-page; CI checks on deploy) | Partially — AI rescans site periodically |
| ADA lawsuit history? | Tool has no lawsuit history | Sites using UserWay have been sued |
| Best for | Developers building accessible code | Not recommended for compliance |
What axe DevTools Is (And Why Developers Trust It)
axe DevTools is the browser extension and testing toolkit from Deque Systems, one of the oldest and most respected accessibility consultancies in the world. The tool is built on axe-core, an open-source accessibility rule engine that has become the industry standard — it powers Google Lighthouse, Microsoft's Accessibility Insights, and the US government's accessibility testing infrastructure.
When you run axe DevTools on a page, it analyzes the live DOM and reports:
- Violations — confirmed WCAG failures with rule ID, impact level (critical/serious/moderate/minor), affected DOM element, and fix guidance
- Incomplete — items requiring manual review that can't be automatically determined
- Passes — rules that are correctly implemented
- Inapplicable — rules that don't apply to elements on this page
Beyond the browser extension, axe DevTools integrates into developer workflows in ways UserWay simply cannot:
axe DevTools Integration Points
- axe-core npm package: Embed accessibility testing directly in your test suite (Jest, Cypress, Playwright)
- GitHub Actions: Run axe-core on every pull request to catch regressions before merge
- Chrome DevTools panel: Test in-browser without leaving your dev environment
- VS Code extension (axe Accessibility Linter): Flag issues as you write JSX/HTML in your editor
- Storybook integration: Test component accessibility in isolation
axe DevTools Limitations
- Manual and page-level: The free extension tests one page at a time — no site-wide crawling
- ~57% automated detection: axe-core catches roughly 57% of WCAG issues automatically — the rest require human judgment
- Requires developers: axe DevTools outputs technical information that needs a developer to interpret and fix
- No continuous monitoring: axe DevTools doesn't watch your live site — for that you need a separate monitoring tool
What UserWay Is (And Why It's Controversial)
UserWay is an accessibility overlay company founded in 2015. It markets an AI-powered widget that claims to make websites accessible by injecting JavaScript that modifies how your site renders in the browser. UserWay is one of the most widely-installed overlays in the market, with millions of websites using their widget.
The UserWay widget provides:
- A floating accessibility toolbar (the "accessibility widget icon") visible to all site visitors
- User-adjustable display settings: font size, contrast, cursor size, reading guide, animations pause
- AI-generated alt text for images missing descriptions
- ARIA attribute injection at runtime
- Claims of WCAG 2.1 AA compliance based on widget installation
The UserWay Problem — Why Overlays Can't Deliver Compliance
UserWay's fundamental limitation is shared by all overlay widgets: screen readers and other assistive technologies interact with the page's actual DOM, not the runtime-patched version UserWay creates.
When a JAWS or NVDA user visits your site, their screen reader builds a virtual buffer of the page's accessibility tree from the source DOM — before UserWay's JavaScript has finished executing. The AI-generated ARIA attributes and alt text that UserWay adds often come too late, arrive in the wrong order, or conflict with what the screen reader has already cached.
This is why the Overlay Fact Sheet — signed by over 400 blind users and accessibility advocates — specifically documents UserWay along with other overlays as failing to provide genuine accessibility. Sites using UserWay have been named in ADA lawsuits even after installation, because the underlying WCAG violations remain in the source code.
axe DevTools vs UserWay: Which to Use When
Use axe DevTools when…
- You're a developer who can act on audit findings
- You want to integrate accessibility into your CI/CD pipeline
- You need WCAG rule references for each violation
- You're testing component accessibility in isolation
- You want the same engine used by Microsoft, Google, and US agencies
Avoid UserWay when…
- Your goal is genuine WCAG 2.1 AA compliance
- You want reliable ADA lawsuit protection
- You have screen reader users in your audience
- You're in regulated industries (healthcare, finance, government)
- You don't want a visible widget added to your site
The limited case for UserWay
If you're on a completely locked platform (certain hosted builders or legacy CMSs) where you have zero ability to edit templates or code, UserWay's display controls give users some ability to adjust their experience — and UserWay's AI alt text generation occasionally produces useful descriptions for truly missing alt attributes. These are marginal gains, not compliance. Treat it as a temporary accessibility UX improvement, not a legal shield.
The Right Accessibility Stack for Developers
If you're evaluating UserWay because you want WCAG compliance without deep developer effort, here's what actually works:
axe DevTools — Free WCAG Auditing
Free browser extension
Install the free Chrome or Firefox extension. Run it on your key pages. Review violations by impact level (critical first). Fix them in your source code. This is the foundational step — no overlay, no widget, just identifying real issues.
RatedWithAI — Continuous Monitoring
$29/month
Fills the gap axe DevTools leaves: continuous site-wide monitoring. RatedWithAI uses axe-core to scan your entire site and alert you when new WCAG violations appear — no widget added to your site. At $29/month vs. UserWay's $49+/month, you get better compliance data at lower cost.
Start Free Scan →axe-core in CI/CD — Regression Prevention
Free (open source)
Add axe-core to your test suite so accessibility regressions are caught before they reach production. The @axe-core/playwright, @axe-core/cypress, and jest-axe packages make this straightforward. This is the highest-leverage investment for teams that ship frequently.
Manual Testing with JAWS/NVDA — The Gaps Automation Misses
Free (NVDA) / $90/yr (JAWS Home)
No automated tool catches 100% of accessibility issues. Keyboard navigation, reading order, screen reader announcements, and complex widget interactions require manual testing. Even a few hours of NVDA testing per quarter catches issues that axe-core and WAVE can't detect.
Fix what's actually broken. Skip the widget.
RatedWithAI runs continuous axe-core scans across your site and alerts you to WCAG violations — no overlay widget, no runtime patches. $29/month.
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 axe DevTools free?
Yes. The axe DevTools browser extension for Chrome and Firefox is free and provides unlimited WCAG scans at no cost. Deque also offers axe DevTools Pro (from ~$100/seat/year) which adds guided testing, intelligent guided tests for issues that can't be fully automated, and team collaboration features. But for the core WCAG violation scanning that most developers need, the free extension is sufficient.
What's the difference between axe DevTools and axe-core?
axe-core is the open-source accessibility testing library — the rule engine. axe DevTools is a product built on top of axe-core that provides a user-friendly browser extension and DevTools panel interface. When you install axe DevTools as a browser extension, you're using axe-core under the hood, but with a more accessible UI. axe-core can also be used directly in code via npm for programmatic testing, CI/CD integration, and building custom tools.
Does UserWay work with WordPress?
UserWay has a WordPress plugin that installs the overlay widget on WordPress sites. The plugin installs easily and adds UserWay's floating toolbar to your site. However, the same limitations apply: the widget doesn't fix your WordPress theme's underlying WCAG violations — it just applies runtime patches that screen readers may not benefit from. If you're on WordPress and want real WCAG compliance, use a WCAG-compliant theme and fix violations in your templates — then use free tools like axe DevTools or Lighthouse to verify.
Can I use axe DevTools and UserWay together?
Technically yes, but it's counterproductive. If you run axe DevTools while UserWay is installed and active, UserWay's JavaScript modifications may interfere with axe DevTools' analysis of the true DOM state — giving you inaccurate results. If you want to audit your site's real accessibility, disable UserWay (or test in an incognito window without the extension active) before running axe DevTools. The goal should be to find and fix real violations, which makes UserWay redundant.
What percentage of WCAG issues does axe DevTools catch?
axe-core (the engine behind axe DevTools) catches approximately 57% of WCAG 2.1 issues automatically — a figure confirmed in Deque's own research. This is the highest detection rate of any automated tool, but it still means about 43% of WCAG issues require manual testing. This is true of all automated accessibility tools — no scanner catches everything. The issues automation misses tend to be subjective (is this alt text meaningful?) or interaction-based (does keyboard navigation work as expected?) rather than structural errors.
What are the best UserWay alternatives?
The best UserWay alternatives depend on why you were considering UserWay. For WCAG auditing: axe DevTools (free) or WAVE (free). For continuous site-wide monitoring: RatedWithAI ($29/month). For managed remediation with human experts: AudioEye (~$49+/month) or Level Access (enterprise). For organizations that truly want no-overlay compliance, the combination of free auditing tools + RatedWithAI monitoring at $29/month covers more ground than UserWay for less money.