UserWay pitches the WP plugin as install-and-forget. ADAflags gives you the code-level fix in the report. Here's the side-by-side.
A federal Magistrate recommended against dismissing the class action against UserWay in Feb 2026, meaning the suit will move into discovery on whether UserWay's marketing claims are deceptive trade practices. Behind that, the WP plugin is a JavaScript widget that patches the rendered page after load — the same structural problem as every overlay. And UserWay's "audit" report is a PDF that routes the SMB to a third-party remediation contractor for the actual code work. ADAflags scans your real source HTML with axe-core and gives you code-level fixes in the same report.
Source: ABA Title III Tracker / Seyfarth 2024 overlay-equipped defendants analysis. WebAIM 2024 Million Report overlay-equipped subset. FTC v. accessiBe settlement (January 2025); UserWay federal class action, Magistrate recommendation (Feb 2026).
ADAflags vs UserWay — the real comparison
Compared across the dimensions that matter for ADA lawsuit protection: how each approach actually fixes WCAG violations, what courts and regulators have said, price, screen reader compatibility, and what each "audit" deliverable actually contains.
| Feature | ADAflags Best | UserWay |
|---|---|---|
| Approach | Code-level scanner — identifies real violations in your HTML, ranked by lawsuit risk | WP-plugin/JavaScript overlay applied at runtime |
| Fixes source HTML? | ✓ Yes — exact code changes per violation | ✗ No — patches the page after load |
| Audit deliverable | ✓ Same report = violations + exact code fixes | ✗ PDF report; routes SMB to third-party remediation contractor |
| Price | Free scan; $19 one-time audit; $9.99/mo monitoring | $49–$490/month depending on traffic (UserWay.org WP-plugin tiers) |
| ADA lawsuit protection | ✓ Prioritizes violations most cited in actual ADA complaints | ✗ Overlay use cited as evidence of bad faith in lawsuits |
| WCAG coverage | Full automated axe-core scan — 50+ WCAG 2.1 AA rules | ~ Runtime patching catches surface-level issues only |
| Screen reader compatibility | ✓ Reports violations as they exist in source HTML | ✗ Overlay modifications don't reach screen readers |
| FTC/regulatory status | ✓ No enforcement actions or pending class actions | ✗ Federal class action proceeding (Feb 2026 Magistrate recommendation) |
| NFB endorsement | ✓ Not condemned | ✗ NFB condemnation of the overlay model applies to UserWay too |
| Multi-page scanning | ✓ Crawls entire site, aggregates violations by frequency | ✗ WP plugin applies site-wide but doesn't audit it |
| Setup time | Instant — enter URL, get results in seconds | ~10 minutes (install WP plugin), then recurring monthly billing |
The class-action proceeding + the manual-audit handoff gap
In Feb 2026, a federal Magistrate recommended against dismissing the class action against UserWay — the suit will proceed into discovery on whether UserWay's marketing of its overlay product constitutes deceptive trade practice.
The structural problem isn't UserWay specifically. The WP plugin is a JavaScript widget that runs after the page loads — same category as every overlay. And the "audit" deliverable UserWay charges $49–$490/month for is a PDF report that identifies violations and then hands the SMB back to a third-party contractor for the actual code work. UserWay routes the fix back to a vendor rather than delivering it in the report.
Court rejected motion to dismiss the UserWay class action
The Feb 2026 Magistrate recommendation means the suit moves forward — UserWay will have to defend its product marketing in federal court. SMBs paying for the same product during ongoing litigation are paying for a vendor whose core promise is being tested.
UserWay's "audit" deliverable hands coding work to a contractor
The PDF identifies violations. The actual code work is shipped back to a third-party remediation vendor. You pay monthly for the routing layer; the fix itself is a separate engagement you finance again.
NFB condemnation of the overlay model applies to UserWay
The National Federation of the Blind's condemnation wasn't vendor-specific — it covered the entire JavaScript overlay category, including the UserWay WP plugin. Their position is that overlays fail blind users and waste the time of accessibility professionals.
Code-level fixes = documented good-faith remediation
Code-level fixes documented in scan reports — before-and-after violation counts, exact code changes, WCAG rule IDs — are the most defensible artifact if a demand letter arrives. Using a WP plugin that hands the fix back to a contractor isn't documented remediation; it's a recurring bill.
Lawsuit stats for SMBs currently running the UserWay WP plugin
What the legal record looks like for small-business websites that installed UserWay — and what the price of false protection adds up to.
The Feb 2026 federal Magistrate recommendation against dismissal allows the class action to proceed. The plaintiffs allege UserWay marketed an overlay product as constituting ADA / WCAG compliance while delivering runtime patches that do not address the underlying source HTML. The case will go through discovery and likely trial — meaning UserWay's marketing claims are now in federal court record.
Sources: U.S. District Court, UserWay class action; Magistrate recommendation, Feb 2026.
456 overlay-using sites were sued in H1 2025. Of those defendants whose home pages still had measurable accessibility errors after WP-plugin install, 22.6% received an ADA demand letter — meaning the plugin did not filter them out of the lawsuit queue. The plugin ran on the home page, plaintiff scanning tools still found WCAG issues that mattered, and the demand letter arrived.
Sources: ABA Title III Tracker / Seyfarth 2024 overlay-equipped defendants analysis; 2025 ADA Title III lawsuit filings.
A typical UserWay.org WP-plugin SMB subscription at $49/month runs $1,764 over three years — and the high-traffic tier ($490/mo) hits $17,640. ADAflags' $19 audit identifies all of the same WCAG violations with exact code fixes; once they're fixed, they stay fixed for free. The "subscription" is actually the cost of deferring the fix to a contractor you have to pay separately.
Source: UserWay.org published WP-plugin pricing tiers as of 2026.
70% of screen reader and keyboard-only users reported that overlay widgets — including the UserWay WP plugin — actively made sites harder to use. The runtime layer manipulates focus in ways screen readers don't expect, inserts elements into the accessibility tree that don't correspond to source HTML, and creates inconsistency between what a screen reader announces and what sighted users see.
Source: WebAIM 2024 Million Report — overlay-equipped subset.
6 violations the UserWay WP plugin cannot fix — and ADAflags catches
These are structural limitations that apply to UserWay's WP plugin — and every JavaScript overlay widget. They are not fixable at runtime because accessibility is a code-level property, not a presentation layer.
Missing alt="" on <img>
The UserWay WP plugin can inject AI-generated alt text as a visible label on the rendered page — but a screen reader reads the alt attribute directly from the DOM. The plugin's visual layer is invisible to the screen reader. The underlying source still has no alt attribute, and that's what courts and plaintiff scanners evaluate.
Unlabeled <input> fields
A <label for="..."> association is a source HTML relationship between a label element and its input. The UserWay WP plugin running after page load can't retroactively add this relationship to the DOM in a way that screen readers and accessibility APIs recognize as semantically correct. The form remains unlabeled at the code level.
Keyboard trap in a modal dialog
Focus management for modal dialogs must be implemented in the page's JavaScript — the code that opens the modal must move focus into it, and the code that closes it must return focus to the trigger. The UserWay plugin running in parallel cannot intercept, reorder, or control focus flow that's already managed (or mismanaged) by the page's own event handlers.
WCAG 2.1.2 — No Keyboard TrapLow contrast text
Color contrast ratios are computed from the rendered CSS values at paint time. The UserWay WP plugin running after page load cannot change CSS custom property values, compiled stylesheets, or inline styles that are already applied. The contrast value a scanner (and a court's expert) reads is the computed value from the source CSS — not anything the plugin can modify.
WCAG 1.4.3 — Contrast MinimumMissing page <title> or lang attribute
The <html lang="en"> attribute and <title> element are document-level declarations in the source HTML. They must be present in the markup the server sends. The UserWay JS appended to the rendered page arrives after the browser has already parsed the document and set these values (or failed to). They cannot be retroactively patched at runtime.
Missing skip navigation link
A "Skip to main content" link must be the first focusable element in the document source — so keyboard users can bypass the navigation without tabbing through every link. The UserWay plugin appends elements to the rendered DOM; it cannot reorder elements that already exist in the source to make the skip link first. Any injected skip link arrives after the navigation it was supposed to skip.
WCAG 2.4.1 — Bypass BlocksUserWay's audit doesn't include a real VPAT — ours does →
UserWay charges $588+/year to hand you back to a contractor. ADAflags fixes the actual violations once.
UserWay SMB WP-plugin subscriptions run $49–$490/month — $588–$5,880/year — for a product currently in federal class-action litigation. Compare that to fixing the actual violations in your source HTML once.
- Full WCAG 2.1 AA scan (axe-core)
- Violation report with exact code fixes
- Lawsuit risk score per violation
- Re-scan after fixes to verify
- Documented compliance effort for court
- Weekly automated WCAG scans
- Email alerts for new violations
- Violation trend tracking
- Monthly PDF compliance summary
Looking at accessiBe, AudioEye, or EqualWeb instead?
UserWay is one of four major overlay vendors — they all use the same JavaScript runtime-patching model. See the full /vs/overlay-widgets comparison for accessiBe, AudioEye, and EqualWeb alongside UserWay.
See the full /vs/overlay-widgets comparison (covers accessiBe, AudioEye, EqualWeb too) →Or pit your site against a competitor.
If you want a head-to-head WCAG scan — your site vs a competitor, or two competitors — use ADAflags' /compare tool. Two URLs, free, ranked by lawsuit exposure delta.
Open /compare →Why not just install the UserWay WP plugin?
Don't pay $1,764 to be handed back to a contractor.
Scan your site now. Free, instant, and it shows you the exact violations the UserWay WP plugin can't fix — so you can actually fix them.
Free tools to run right now
Three no-signup ADAflags audits that catch the WCAG failures ADA Title III demand letters cite most. Run them before counsel runs them for you.
- Alt-Text Checker → WCAG 1.1.1 image audit — the violation most demand letters lead with.
- Color Contrast Checker → AA, AAA, large-text and UI-component thresholds — no signup.
- Accessibility Statement Generator → Vertical-templated DOJ-style statement with the formal complaint procedure.
- VPAT 2.4 Generator → Free ACR for federal RFPs, healthcare procurement, and enterprise vendor forms.