Skip to content
StoreA11y

Your accessibility widget is not protecting you.

22.6% of 2025 US accessibility lawsuits hit websites that had a widget installed. StoreA11y finds the defects that are actually in your theme code, ranks them by the risk they carry, and tells your developer which file to open.

For Shopify and WooCommerce merchants. Not an overlay — we never inject anything into your store.

5 pages. No account, no card. Results in about a minute.

Standard
WCAG 2.1 level A and AA
Engine
axe-core in headless Chromium
Rules with written fixes
47
Pages, free / paid
5 / 20

What you get

One finding, exactly as it appears in the report

Drawn from the same guidance table the paid report reads from. Every rule we check has an entry written by hand against real theme structure.

01

Critical

image-alt

Instances47
Pages affected16 / 20
Fix effortlow
Priority95
Litigationfrequently cited

Images missing alternative text

47 images have no text alternative. A screen reader announces them as "image" or reads the raw filename, so a blind shopper hears "IMG_4471 dot jpg" instead of the product name. Product images without alt text are the single most common defect cited in filed accessibility complaints.

Fails

  • 1.1.1 Non-text Content (Level A)

How to fix it

  1. 01Product photos: Shopify admin > Products > [product] > hover the image > Add alt text. Describe what is in the photo — "Navy merino wool crew neck sweater, front view" — not "product image" and not the SKU.
  2. 02Content images: Content > Files does not hold alt text; alt is set wherever the image is placed. For rich-text blocks, edit the block and use the image alt field.
  3. 03Theme images: Online Store > Themes > Edit code. Search the theme for `<img` and for `image_tag`. Every one needs an `alt` attribute.
  4. 04and 2 more, plus the code below

Code

{% comment %} Liquid: fall back to the product title, never to the filename {% endcomment %}
<img src="{{ image | image_url: width: 800 }}"
     alt="{{ image.alt | default: product.title | escape }}"
     width="{{ image.width }}" height="{{ image.height }}" loading="lazy">

<!-- Purely decorative: empty alt, so it is skipped -->
<img src="{{ 'divider.svg' | asset_url }}" alt="">

Shopify location

sections/image-banner.liquid, sections/slideshow.liquid, snippets/card-product.liquid, snippets/product-thumbnail.liquid, and the alt-text field on each product image in admin

Evidence

Why this is worth an hour of your time

Every figure below links to its source. We did not commission any of them.

Accessibility litigation and enforcement figures
4,928US web-accessibility lawsuits filed in 2025UsableNet lawsuit tracker
69%of H1-2025 suits targeted online storesTestParty ecommerce data
64%of sued companies had revenue under $25MUsableNet 2025 research
22.6%of 2025 suits hit sites that already had an overlay widget installedTestParty / CourtListener analysis
$1,000,000FTC fine against accessiBe for claiming its AI overlay made sites meet WCAGFTC press release, January 2025

Overlays

If you already pay for a widget, read this first

An accessibility overlay is a script that loads on top of your store and offers a toolbar of font-size and contrast controls. It does not change your theme, so the defects underneath it stay exactly where they were.

In January 2025 the FTC ordered accessiBe to pay $1,000,000 over claims that its AI overlay could make websites meet WCAG, and over undisclosed endorsements. Litigation data for the same year shows 22.6% of filed suits hit sites that had a widget installed.

The full analysis, with sources

Our scan reports

Which vendor is loading
accessiBe, UserWay, AudioEye or EqualWeb — with the evidence that detected it.
How many issues remain
Counted from your live pages, with the widget script running.
What to change instead
In the paid report: the theme file, the markup, and the code.

Method

What happens when you press scan

  1. 01

    Pages are chosen, not guessed

    Sitemap first, links as fallback. We pick a representative set — homepage, a collection, a product, cart, checkout entry, contact, policies — rather than twenty blog posts.

  2. 02

    Each page runs in a real browser

    Headless Chromium with your theme JavaScript executing, tested with axe-core against WCAG 2.1 A and AA. Anything rendered client-side is tested as a visitor receives it.

  3. 03

    Findings are ranked, not dumped

    Severity, how often the rule appears in filed lawsuits, how much of your store is affected, and how fast the fix is. The top of the list is where to start.

  4. 04

    Each one names a file and a change

    Written by hand per rule against real Shopify and WooCommerce theme structure. Not the tool’s help text reworded.

Pricing

One report, one price, no subscription

Overlay vendors charge $49–199 every month. A single $79 report costs less than two months of a widget that litigation data shows does not stop suits being filed.

StoreA11y pricing
TierPricePagesContents
Free scan$055 pages. Counts, severity split and overlay detection.No fix instructions · No affected selectors · No PDF
Auditmost bought$79one-time2020 pages, every finding, ranked, with fix instructions.
Audit + re-scan$149one-time20Everything in Audit, plus one re-scan within 30 days.
Monitoring$19per month20 weeklyWeekly re-scan. Email alert when new issues appear.

Billed by Lemon Squeezy, the merchant of record. Prices in USD; tax handled at checkout.

Find out what is actually broken.

Five pages, free, no account. Automated testing detects roughly 30–40% of WCAG issues; the rest needs a human tester.

5 pages. No account, no card. Results in about a minute.