wcagdefender

UserWay Review for Small Business: Tested Against WCAG AA

UserWay is worth paying for if you want a visual-preferences toolbar, a quick scan dashboard, and contrast or text-sizing options for users. It is not worth buying as ADA compliance: the structural failures that drive demand letters live in your source code, and a script loaded at runtime does not change your source code.

Buy UserWay if you want a user-facing preferences toolbar and lightweight monitoring; do not buy it as ADA compliance. The failures that actually block disabled users and attract demand letters — missing labels, wrong heading structure, broken focus order, unlabeled custom widgets, meaningless alt text — are structural. An overlay script can change the rendered DOM at runtime; it cannot change your templates, and it cannot reliably infer what your content means.

The 50-word verdict

Genuinely useful: a visual-preferences toolbar (contrast, text size, spacing, link highlighting), an accessibility statement generator, scheduled scanning, and fast cosmetic wins on small brochure sites built from clean templates. Leaves you exposed: structural WCAG failures in headings, form labels, focus order, keyboard operability, alt text equivalence, and custom JavaScript components.

How we tested, and our conflict of interest

Disclosure first: WCAGDefender sells scanning and code-level remediation guidance. We compete with overlay vendors. Read this review with that in mind, and re-run the protocol yourself — that is why we publish it.

The protocol is deliberately boring and reproducible:

We do not publish invented pass/fail percentages. The table below describes what a DOM-injection overlay can and cannot change by design — which is the part that stays true across versions and across vendors, including accessiBe, AudioEye and EqualWeb.

Per-criterion results

CriterionFailure introducedOverlay outcome (runtime DOM)After code remediation (source)
1.1.1 Non-text ContentHero and product images with no alt attributeAn alt value may be injected by image recognition; the text is generic, cannot be verified as an equivalent, and is wrong for images that carry meaning in context. Decorative images are not reliably marked as decorative.Author-written alt reflecting purpose; decorative images get alt=""; alt lives in the template and survives the widget being blocked.
1.3.1 Info and RelationshipsHeadings faked with styled divs; data presented in a layout tableCannot infer which divs were meant to be headings or which table cells are headers. Structure announced to the screen reader stays flat.Real h1–h3, th/scope, list markup. Screen-reader users can navigate by heading.
1.4.3 Contrast (Minimum)Grey-on-white body text below 4.5:1Genuinely helps. A user who opens the toolbar and selects a high-contrast mode gets readable text. The default page is unchanged for everyone who never opens the widget.Palette fixed once; readable for every visitor, including those on the plain page.
2.1.1 KeyboardCustom div-based accordion operable only by mouseNo keyboard handler is added for a bespoke component. Tab skips it; Enter and Space do nothing.Button semantics, key handlers, aria-expanded. Operable without a mouse.
2.4.3 Focus OrderModal opens without moving focus; focus continues behind the overlayFocus management for your own scripts is outside the widget's control. The modal is still unreachable or inescapable.Focus moved on open, trapped inside, returned to the trigger on Esc.
2.4.7 Focus Visibleoutline: none applied globallySome widgets paint a focus ring when their keyboard-navigation mode is enabled. Off by default; absent for users who never open the toolbar.Visible, high-contrast focus indicator in CSS for everyone.
3.3.2 Labels or InstructionsQuote form inputs with placeholder text onlyPlaceholder text may be exposed as an accessible name in some configurations, but the visible label is still missing and the association is not in your markup.<label for> tied to each input; errors described in text and programmatically linked.
4.1.2 Name, Role, ValueDiv "button" with an icon and no accessible nameCannot determine the intended role or name of an arbitrary component. Announced as a group or ignored.Native button or correct ARIA role, name and state.
2.4.1 Bypass BlocksNo skip link; 30-item nav before main contentSome widgets add their own navigation shortcuts inside the widget UI, which is not the same as a skip link in the page tab order.Skip link as the first focusable element; landmarks (header, nav, main).

The pattern is consistent: criteria that are presentational (contrast, text size, spacing) are where a toolbar adds real value. Criteria that are semantic or behavioural require someone to decide what the content means and how the component should behave. For a longer treatment see overlay vs. real code fix.

Overlay vs. remediation, in one sentence each

An overlay is third-party JavaScript that loads after your page and rewrites the rendered DOM plus offers a user-settings menu; remove the script and every change disappears. Remediation changes your HTML, CSS, components and content so the page is accessible before any script runs, with or without assistive technology, and so that your developers stop reintroducing the same defects. The independent Overlay Fact Sheet, signed by a large number of accessibility practitioners including screen-reader users, documents the same limitations.

Three-year cost, framed so you can verify it

Do not take anyone's numbers, including ours. Price it yourself with this structure, using the current list price on userway.org/pricing/ and a real quote from a developer.

LineWidget subscription pathRemediation path
Year 1Monthly or annual fee per domain, by pageview tierOne-time fix effort: developer hours x rate, scoped by page templates, not by page count
Years 2–3Same fee again, twiceLight monitoring plus a few hours per year for new templates and content
What you own at the endNothing; cancel and the changes vanishAccessible templates in your repository
If you redesignPay again, same exposureAccessible patterns carry forward
New content (blog posts, PDFs)Not covered by the widgetCovered by an author checklist

For most small business sites the work is bounded because templates repeat: a header, a nav, a form, a card grid, a footer. Fix the templates and you fix hundreds of pages. Our free scan on the homepage will tell you which templates are the problem; a scoped estimate turns that into hours. If you are weighing a managed service instead, see AudioEye vs. hiring a developer.

No tool, including ours, makes a site permanently compliant or lawsuit-proof. Accessibility is a property of your code and content, and it decays every time someone publishes a new page.

Legal reality check

The Department of Justice's web accessibility guidance states that businesses covered by ADA Title III must make their websites accessible and does not endorse any product as a means of doing so; the Title II rule adopts WCAG 2.1 AA for state and local government. No court has treated the presence of an overlay as a defence, and plaintiffs routinely file against sites running one. In 2025 the Federal Trade Commission brought an enforcement action concerning marketing claims that an overlay product made websites automatically WCAG-compliant — read it directly in the FTC press releases rather than taking a vendor's summary. More detail: do overlays prevent ADA lawsuits.

Who should buy UserWay anyway

There is a legitimate buyer, and pretending otherwise would be dishonest:

It is the wrong purchase for ecommerce checkouts, booking and quoting flows, dashboards, PDFs, and anything with custom JavaScript components.

The cheapest credible path

  1. Run a free scan to list issues by template, then tab through your top three pages with the mouse unplugged. If you cannot complete the main task, no widget will save you.
  2. Fix the top five template-level defects: labels, headings, focus visibility, skip link, alt text. This is usually a handful of developer hours and removes the majority of recurring failures.
  3. Write a one-page content checklist so new posts do not reintroduce them.
  4. Re-test manually each quarter and after every theme or plugin update. See tools for small business owners.

Frequently asked questions

Is UserWay enough to make my site ADA compliant?

No. A widget changes the rendered page at runtime and cannot fix structural problems such as heading semantics, form label associations, focus order, or custom components that are not keyboard operable. Those require changes to your source code.

Do accessibility overlays like accessiBe actually work?

They work for presentational preferences — contrast, text size, spacing — for users who open the toolbar. They do not reliably resolve semantic or behavioural WCAG failures, and the independent Overlay Fact Sheet documents the same limits across vendors.

Will having an overlay protect me from a demand letter?

No court has accepted an overlay as a defence, and sites running overlays are routinely sued. The FTC has also brought an enforcement action over automated-compliance marketing claims in this category.

What is the difference between an overlay and real remediation?

An overlay is third-party JavaScript layered on top of your page; disable it and every change disappears. Remediation changes your HTML, CSS and components so the page is accessible before any script runs.

What is the cheapest way to make a small business site accessible?

Fix templates rather than pages. Scan to find which templates fail, fix labels, headings, focus indicators, skip links and alt text once, then add a short content checklist and re-test manually each quarter.

Should I ever pay for a widget alongside code fixes?

Possibly, as a user-facing preferences feature or for scheduled monitoring, provided you treat it as a convenience and not as a compliance control, and you have a dated plan for the underlying code.

See where your site stands with wcagdefender
Run the free scan →