If you're shopping for an accessibility vendor, you've probably narrowed it down to one of two categories: a widget-based subscription service like AudioEye, accessiBe, or UserWay — or a one-time engagement that remediates the site's actual source code. They're marketed as if they're doing the same job. They're not. This post breaks down how each approach works, what the data says about their legal defensibility, and when each is actually the right fit.
How AudioEye Works
AudioEye is a publicly traded accessibility vendor (NASDAQ: AEYE) that combines two products: an AI-driven JavaScript overlay that loads on top of your site, and a managed-services layer where human specialists review flagged issues. The overlay is delivered through a single script tag you add to your site's HTML. Once installed, it attempts to apply automated fixes at page load — things like adjusting alt text, tweaking ARIA attributes, and overriding color contrast in the rendered DOM.
Pricing is subscription-based and typically tiered by monthly page views, with small-business plans starting in the low hundreds of dollars per month and enterprise plans scaling into the thousands. The fixes are applied in the browser at runtime — your underlying HTML, CSS, and JavaScript are never modified. Stop paying, remove the script, and the "compliance" layer disappears with it.
How Source-Code Remediation Works
Source-code remediation is exactly what it sounds like: accessibility specialists audit your site against WCAG 2.2 AA, then edit the actual HTML, CSS, JavaScript, and templates to bring them into conformance. Missing alt attributes are added to the image tags themselves. Form fields get real <label> elements. Color tokens are adjusted in your stylesheet. Focus order is fixed in the markup.
It's a one-time engagement, typically billed as a fixed project fee. When it's done, the fixes are permanent — they live in your codebase and ship with every deploy. No vendor script, no monthly bill, no dependency on a third party continuing to exist.
Head-to-Head Comparison
What the Data Says
The marketing around overlays and source remediation is loud. The underlying data is quieter, and more useful.
Overlays Are a Lawsuit Magnet, Not a Shield
The 2025 UsableNet ADA lawsuit report found that roughly 22.6% of federal ADA web lawsuits filed in 2025 targeted sites that already had an accessibility widget installed. That's nearly one in four — and it reflects a pattern plaintiffs' firms have openly acknowledged: widget-wearing sites are easy to identify and often fail basic WCAG testing anyway.
The FTC's $1M Order Against accessiBe
In April 2025, the Federal Trade Commission finalized a $1 million order against accessiBe for making deceptive claims that its overlay made websites WCAG-compliant. The commission found the claims unsubstantiated and specifically called out the gap between marketing language and actual accessibility outcomes. It's the clearest federal signal yet that "our widget made you compliant" is not a defensible position.
The Overlay Fact Sheet
More than 800 accessibility professionals, developers, and disability advocates have signed the Overlay Fact Sheet, which documents in detail why overlay products fail to deliver meaningful accessibility and often actively harm users of assistive technology. It's not a fringe position — it's the consensus view across the practitioners who actually build and test accessible software.
Screen Reader Users Don't Like Them
WebAIM's most recent screen reader user survey found that a majority of respondents reported overlay widgets made the sites they visited harder to use, not easier. When the users the product is marketed as helping say it's making their experience worse, that's a product problem, not a perception problem.
When AudioEye Might Actually Be the Right Fit
This is where most comparison posts on this topic lose credibility, so it's worth saying plainly: there are situations where a managed overlay service makes business sense.
- Very large sites with high content velocity. A news publisher adding 50 articles a day, or an enterprise e-commerce site with a constantly-changing catalog, can't realistically remediate faster than it publishes. Continuous automated monitoring, even imperfect, can catch low-hanging issues between human audits.
- Sites where the code isn't yours to fix. Some hosted platforms and legacy systems simply don't expose the templates you'd need to edit. If you literally cannot touch the HTML, an overlay may be the only intervention available.
- As a supplement, not a substitute. Some larger organizations use an overlay for ongoing monitoring layered on top of a fully remediated source — not in place of it.
Note what's not on that list: a typical small-business site, a WordPress or Webflow marketing site, or any codebase you or your developer can edit.
When Source-Code Remediation Is the Right Fit
Source-code remediation is the right approach for the situation most businesses are actually in:
- Small to mid-size sites — typically 15 to 50 pages — where a full audit and remediation can be completed in days to a couple of weeks.
- Owner-operated businesses — law firms, medical practices, restaurants, agencies, SaaS companies — where a demand letter is a serious financial event and defensibility matters.
- Any site where you control the code — WordPress, Webflow, custom stacks, Shopify themes, static sites — and can have the fixes merged into your source of truth.
- Businesses that want to stop renting compliance. A one-time fee that stays fixed beats an ongoing subscription that scales with your traffic every time.
The Bottom Line
AudioEye and other overlay vendors aren't scams — they're products designed to make a genuinely hard problem feel easy. But ease of purchase isn't the same as protection. The sites being sued in 2025 include a lot of overlay subscribers. The FTC's enforcement action against accessiBe is a preview of where regulatory scrutiny is heading. And the accessibility community has made its position clear.
If your site is small enough to remediate at the source, remediate at the source. You'll pay once, own the fix, and stop worrying about what happens if the vendor disappears, raises prices, or gets sued itself.
Key Takeaways
- AudioEye applies fixes in the browser at runtime; source-code remediation edits your actual codebase.
- Roughly 22.6% of 2025 ADA web lawsuits hit sites that were already running accessibility widgets.
- The FTC finalized a $1M order against accessiBe in April 2025 for deceptive WCAG-compliance claims.
- Over 800 accessibility professionals have signed the Overlay Fact Sheet opposing widget-based compliance.
- Overlays can be a defensible tactic on very large, constantly-changing sites — not on the typical small-business website.
- For 15–50 page owner-operated sites, one-time source remediation is cheaper, more defensible, and permanent.