Alternatives

UserWay alternative: audit & fix, not an overlay

In short: UserWay is an accessibility widget and overlay: a JavaScript toolbar plus automated adjustments applied in the visitor's browser. Because overlays don't change your source code, they can't reliably deliver WCAG 2.1 AA or EAA conformance. NormHarbor is not an overlay — it scans your real HTML, CSS and ARIA and shows you exactly what to fix, and where.

If you're evaluating UserWay or already using it, here's an honest, fact-based comparison: what UserWay does, the well-documented limitations of the accessibility-overlay category, and how NormHarbor's source-level audit approach is different.

What UserWay does

UserWay is an accessibility widget and overlay product. You add a JavaScript snippet to your site; it adds an on-page accessibility toolbar that lets visitors adjust settings such as contrast, font size, and text spacing, combined with automated adjustments intended to improve compatibility with assistive technology.

Known limitations of the overlay approach

These limitations apply to accessibility overlays and widgets as a product category — they're not specific to UserWay. The accessibility community, including hundreds of practitioners who signed the public "Overlay Fact Sheet," has raised the same concerns about this category for years.

An overlay does not change your site's underlying HTML/CSS/ARIA — it layers JavaScript on top at runtime.
Widely documented community concerns say overlays do not reliably achieve WCAG conformance by themselves.
Screen-reader users have publicly reported cases where overlay scripts made pages harder to use, not easier.
Automated remediation can't make judgment calls that need human review — meaningful alt text, correct reading order, keyboard-trap fixes.
If the overlay script is removed or fails to load, the page reverts to its pre-overlay state — nothing was changed in the code.

How NormHarbor is different

We don't sell an overlay and we don't add a widget to your site. NormHarbor scans your actual HTML, CSS, and ARIA, maps every finding to the relevant WCAG 2.1/2.2 success criterion and the EAA's EN 301 549 clause, and shows you exactly what to fix and where — in your code, not in a runtime layer on top of it. Compared with UserWay, that's the practical difference: a persistent code-level fix instead of a script that has to keep running.

	UserWay (overlay)	NormHarbor (code audit)
What it changes	Adds a JavaScript layer at runtime; your HTML/CSS stays as-is.	Scans your actual HTML/CSS/ARIA and shows the code-level fix.
Persistence if removed	Reverts instantly to the pre-overlay state.	Fixes live in your codebase — nothing has to keep running.
Keyboard & focus order	Can add controls, but can't reliably repair a broken DOM focus order.	Flags the underlying structural issue so a developer can fix it at the source.
Screen reader behavior	Some users report interference with standard screen-reader optimizations.	Fixes are standard markup, so they work with assistive tech like any accessible site.
On-page preference toggles (font size, contrast)	Yes — one of the genuinely useful features of this category.	Not our product — we focus on fixing the underlying code, not adding a preferences widget.
Setup time	Minutes — add a script tag.	A free scan takes ~20 seconds; fixing what it finds takes developer time, same as any code change.
EAA / EN 301 549 mapping	Not typically the core focus of UserWay's product.	Each finding maps to the relevant WCAG 2.1/2.2 criterion and EN 301 549 clause.

See your real code-level issues, free

Run a free automated scan and get a plain-language report of the WCAG issues in your actual code — no UserWay widget or account required.

Run a free scan →

FAQ

Is UserWay a bad product?

We're not making that claim. UserWay is an overlay/widget vendor; the broader accessibility community has raised documented concerns about the overlay category as a whole — not a specific claim about UserWay's engineering. Our position is simply that we don't sell an overlay: we help you fix the underlying code.

Can I use NormHarbor together with UserWay?

Yes. Using an overlay for genuinely useful user-preference toggles doesn't conflict with also fixing the underlying code — many sites do both. We just don't think an overlay by itself should be your only accessibility work.

Does a clean NormHarbor scan mean I'm fully WCAG compliant?

No — like any automated tool, our scan catches a meaningful share of code-level issues but not everything (contrast on CSS-driven styles, full keyboard/screen-reader behavior). See our scan-vs-audit comparison for what's covered.

UserWay is a trademark of its respective owner. NormHarbor is not affiliated with, endorsed by, or sponsored by UserWay. We reference UserWay's name here only for nominative, comparison purposes, to help you evaluate your options. This page is general information, not legal advice.

accessiBe alternative · AudioEye alternative · Overlay vs. code fix · Methodology