AccessiBe and UserWay Alternative: Real Code, Not an Overlay

What an Accessibility Overlay Actually Does

An overlay is a script tag. You paste it into your theme or install it as a plugin, and it loads a widget that runs in the visitor's browser on every page view. The widget can resize text, adjust contrast, and attempt to auto-generate things like alt text or ARIA labels, live, as the page renders.

Nothing about your site's actual HTML changes. Deactivate the plugin, and every "fix" disappears with it. The Overlay Fact Sheet, signed by accessibility consultants, W3C working group members, in-house accessibility experts at Google, Microsoft, and Apple, and disabled end users, names both AccessiBe and UserWay directly as products in this category. Its verdict: automated repair of alt text, form labels, and keyboard access "is not reliable," and full compliance "cannot be achieved with an overlay."

Why Disability Advocates and Courts Have Objected to Overlays

Two separate objections show up here, and they're not the same claim.

The first is technical: overlays run client-side JavaScript that guesses at fixes without understanding your site's actual markup or intent. Screen reader users have reported overlays making sites harder to use, not easier, because the widget adds new controls and behavior on top of a page it doesn't actually understand. Disability rights attorney Lainey Feingold's site, lflegal.com, states plainly that overlays "often block many disabled people from full and equal use of websites" and that "hundreds of lawsuits have been filed against organizations using them."

The second is regulatory. In 2025, the FTC found that the maker of one of the major accessibility overlays had made deceptive claims about the product achieving automated compliance, and ordered it to stop and to pay $1 million. Law firm Saul Ewing covers the order in its ADA website accessibility risk brief, which also notes that more than 4,000 ADA website lawsuits were filed in US federal and state courts in 2024 alone. The vendor is named in the FTC's own announcement, FTC Approves Final Order Requiring accessiBe to Pay $1 Million, dated April 2025.

None of this means every overlay is worthless for every user. It means the marketing claim "install this widget and you're compliant" is the specific thing that's been challenged, by advocates on accessibility grounds and by a federal regulator on truth-in-advertising grounds.

What "Real Code Changes" Means

This is the part that's easy to say and hard to prove, so here's a concrete example instead of a slogan.

What an Overlay Does With an Image That Has No Alt Text

The overlay's script runs in the browser, detects the missing attribute, and often generates a placeholder or a machine-guessed description on the fly, purely in the rendered DOM. Nothing is written back to WordPress. View source or disable JavaScript, and the image still has no alt text, because none was ever saved anywhere.

What WCAGpatch Does With the Same Image

On Pro and up, WCAGpatch's AI writes the alt text directly into the image's WordPress record, the _wp_attachment_image_alt field in your Media Library. That's the same field WordPress itself uses. It's there the next time a screen reader loads the page, the next time Google crawls the page, and independent of whether WCAGpatch is even still active. On Starter, you don't get the AI writer, but you get the finding, so you or your developer can fix it by hand in the same place.

That's what "real code changes" means on this page: the fix lives in your database and your markup, not in a script that has to run correctly, every time, forever, for the fix to exist.

The Honest Limits (Including Ours)

No tool, ours included, checks everything WCAG covers. Roughly a third to 40% of WCAG success criteria can be verified by software at all. The rest, things like whether alt text is actually meaningful, whether a color choice makes sense in context, whether a form's error messages are genuinely understandable, require a human tester, ideally one who uses assistive technology.

WCAGpatch runs 64 automated checks against WCAG 2.1 A and AA, using axe-core, the open source engine maintained by Deque Systems. That's real coverage of the mechanical stuff: missing alt attributes, broken heading order, unlabeled form fields, insufficient contrast. It is not a substitute for manual testing, and no plan, ours or anyone else's, guarantees ADA or WCAG compliance. Anyone who tells you otherwise is selling you something they can't back up. Read the full disclaimer beside the plans.

Sources

1. Overlay Fact Sheet. Names AccessiBe and UserWay as overlay products; signed by accessibility consultants, W3C contributors, in-house experts at Google, Microsoft and Apple, and disabled end users.
2. Lainey Feingold, disability rights attorney. Overlays and lawsuit volume.
3. Saul Ewing LLP, "A Rise in ADA Website Accessibility Lawsuits". FTC $1M order against an overlay maker; 4,000+ 2024 lawsuits.
4. Federal Trade Commission, "FTC Approves Final Order Requiring accessiBe to Pay $1 Million", April 2025. The primary record for the vendor name, the order, and the dollar figure.
5. TestParty, "7 accessiBe Alternatives After the $1M FTC Fine". Names AccessiBe specifically, April 2025.
6. Allied Accessibility. Names AccessiBe specifically, April 2025, $1M figure.
7. accessiBe pricing page. Micro plan $59/mo or $490/yr, fetched 2026-09-07.
8. UserWay pricing page. Traffic-tiered, no fixed published list price found, fetched 2026-09-07.
9. WCAGpatch product code, checked 2026-09-07. The 64 automated checks are axe-core's WCAG 2.1 A and AA rule set; alt text persistence is the plugin's AI fixer writing to WordPress's _wp_attachment_image_alt post meta field.