accessiBe alternative: what to use instead of an overlay widget

The real alternative to accessiBe, or any accessibility overlay widget, is not another widget. It is fixing the code of your store: your theme templates, your product content and the apps you install. This guide is for Shopify and WooCommerce owners who have a widget, or are being offered one, and want to know what else they can do. By the end you will know what an overlay does and does not change, the three practical alternatives, and how to choose between them.

The short answer

An overlay adds a script and a toolbar on top of your pages. It does not change your theme's source code, so issues such as a "Buttons have no name" error or "Form fields are missing labels" stay in your templates. In April 2025 the US Federal Trade Commission finalized an order requiring accessiBe to pay $1 million to settle allegations that it misrepresented its widget's ability to make any website WCAG-compliant (FTC). The alternatives are to find the issues and fix them at the source: yourself or with a developer, with a manual audit by accessibility specialists, or with an automated audit tool that gives you the fixes. Most stores end up using a mix.

What an overlay widget does

The Overlay Fact Sheet, a statement signed by more than 1,000 accessibility practitioners and users, describes overlays as technologies that "apply third-party source code (typically JavaScript) to make improvements to the front-end code of the website." In practice, a widget usually does two things:

• A toolbar for visitors. Buttons to enlarge text, change contrast or pause animations.
• Automatic repairs. A script that tries to guess missing labels or image descriptions while the page loads.

The toolbar can be useful to some visitors, but many people with disabilities already use their own settings and assistive technology, such as a screen reader or browser zoom. The automatic repairs are where the limits show. The Fact Sheet states that "automated application of text alternatives for images is not reliable", that "automated repair of keyboard access is not reliable", and that "full compliance cannot be achieved with an overlay." Its recommendation is to fix accessibility issues "at the source of the original error."

What the FTC alleged, and what the order requires

On January 3, 2025, the FTC announced a proposed order against accessiBe, and it approved the final order on April 22, 2025, by a 3-0 vote (FTC final order). According to the FTC:

• accessiBe marketed accessWidget as a product that "can make any website compliant with WCAG." According to the complaint, accessWidget "did not make all user websites WCAG-compliant," and these claims were therefore "false, misleading, or unsubstantiated" (FTC, January 2025).
• The complaint also alleged that accessiBe formatted third-party articles and reviews to look like independent opinions without disclosing its connection to the reviewers.
• The order requires a $1 million payment and bars accessiBe from claiming its automated products can make any website WCAG-compliant, or keep it compliant over time, without evidence to support the claim.

The order settles the FTC's complaint and is about how accessiBe advertised its product, including how reviews and endorsements were presented. It is still a useful reminder: no product can promise that a script makes your store conform to WCAG.

Do widgets stop lawsuits?

The lawsuit data suggests they do not. EcomBack counted 1,037 ADA website lawsuits in Q1 2026, and 265 of them (25.55%) involved websites that had an accessibility widget installed, up from 209 in Q1 2025. UsableNet reaches the same conclusion in its analysis of its 2026 midyear lawsuit numbers: "the presence of a widget has not proven to be a meaningful deterrent, legally or practically." Our 2026 lawsuit numbers page has the full breakdown by platform and state.

Widget vs code fix: three store examples

These are common issues on Shopify and WooCommerce stores. In each case, a widget tries to patch the page in the browser; a code fix changes the template once, and every page using it is fixed.

1. Product images with no description

A screen reader user hears "image" or a file name instead of what the product looks like. A widget may generate a description automatically, which the Fact Sheet calls "not reliable". The fix is to write alt text in Shopify (open Products, choose a product, click an image, then Add alt text) and make sure your theme outputs it:

{{ product.featured_image | image_url: width: 800 | image_tag: alt: product.featured_image.alt }}

In WooCommerce, open Media in WordPress, select the image and fill in Alternative Text. FixRamp reports this as "Images are missing text alternatives". See our guide to alt text on Shopify.

2. Icon buttons with no name

Cart, search and menu buttons that show only an icon are announced as "button", with no hint of what they do. The fix is one attribute in the theme's header snippet:

<button type="button" class="header__icon" aria-label="{{ 'general.search.search' | t }}">
  {% render 'icon-search' %}
</button>

FixRamp reports this as "Buttons have no name". More examples in buttons with no name in Shopify.

3. Form fields with no label

A newsletter or quantity field with no label is announced as just "edit text", and placeholder text alone is a weak substitute because it disappears as soon as someone types. The fix is a real label tied to the field:

<label for="NewsletterEmail" class="visually-hidden">Email address</label>
<input id="NewsletterEmail" type="email" name="contact[email]" autocomplete="email" placeholder="Email address">

Use your theme's visually hidden class: visually-hidden in Dawn and most Shopify themes, screen-reader-text in WordPress themes. Or drop the class to show the label.

In WooCommerce, the same fix goes in a child theme template override or the plugin that outputs the form. FixRamp reports fields with no accessible name as "Form fields are missing labels".

The alternatives to an overlay widget

There is no single right choice. It depends on your budget, your store's size and whether you have a developer.

The W3C puts the limit of any tool plainly: evaluation tools "can not determine accessibility, they can only assist in doing so", and "human judgement is required" (W3C WAI). That applies to FixRamp as much as to any other tool. A good plan often starts with an automated audit, fixes the clear issues in the templates, then adds manual testing of key flows such as cart and checkout.

Some overlay vendors also sell audits, developer tools or expert services. When you compare any option, ask one question: does it change the code of my store, or only what loads on top of it?

Where FixRamp fits

FixRamp is an automated audit, not a widget. Nothing is installed on your store.

1. Run the free scan on one page. It shows up to 5 of the most serious issue types it finds, so the full report may list more.
2. For a full report, choose Spot check ($99, 2 pages), Starter ($249, 25 pages) or Pro ($599, 150 pages, including the cart). The report arrives by email within 24 hours.
3. The report groups each issue by template and shows how many times it appears on each page, with up to 3 examples and the code fix for Shopify or WooCommerce. See a sample report.
4. If a paid report finds fewer than 5 issue instances, you get a full refund automatically.

A FixRamp report is a diagnostic. It is not a certification, and it does not replace a manual audit for the issues automated testing cannot find. Selling in Ontario? See our AODA compliance guide.

This page is general information, not legal advice. If you have received a demand letter or a lawsuit, talk to a lawyer.

Sources

• Federal Trade Commission, FTC Approves Final Order Requiring accessiBe to Pay $1 Million, April 22, 2025
• Federal Trade Commission, FTC Order Requires Online Marketer to Pay $1 Million for Deceptive Claims, January 3, 2025
• Overlay Fact Sheet
• EcomBack, Q1 2026 ADA Website Lawsuits Recap Report
• UsableNet, Inside the 2026 midyear numbers
• W3C WAI, Selecting Web Accessibility Evaluation Tools