Free scan · plain-English report in 60 seconds

See what's actually broken on your store — in 60 seconds.

Not a widget. Not a badge. A real scan of what stops blind, low-vision, and keyboard-only shoppers from checking out — plus exactly how to fix each one.

View Example Report

60 seconds. No card. No install.

In 2025, overlay-widget company accessiBe agreed to pay $1 million to settle FTC charges. The FTC alleged it falsely claimed its widget could make any website meet accessibility guidelines; accessiBe did not admit or deny this. Here's what's really on your site.

How it works

Three steps: see what's broken, fix it, keep the record.

01

Scan your store

A real browser opens your store and checks it against the WCAG accessibility rules that ADA and EU law reference.

02

Get plain-English findings

Every failure names the WCAG rule it breaks and is explained without jargon: what we found, the legal exposure, and exactly how to fix it — with screenshots.

03

Build your compliance record

Monthly re-scans track what's fixed and what's new, building a dated record — your evidence of ongoing monitoring.

Coverage

What we check.

The scan checks the barriers that most often shut out blind, low-vision, keyboard-only, and older shoppers — the things that quietly cost you orders. They're also the WCAG rules accessibility complaints tend to reference.

  • Images without descriptions
  • Text too light to read
  • Buttons and links with no name
  • Form fields without labels
  • Keyboard access to menus and controls
  • Missing page structure and landmarks
  • Text baked into images
  • Meaning shown by color alone
  • Zoom and text-resize behavior
  • Language and page-title basics

Anatomy of a finding

What a finding looks like.

This is the exact format your report arrives in — an accessibility score, and every failure as a plain-English card: the WCAG rule it breaks, where it is, why it matters, and how to fix it.

Example report using a fictional demo store.

52/100
At risk

Accessibility score (automated)

2Critical2Serious0Moderate0Minor
#01CriticalRule checkWCAG 1.1.112 placesProduct images have no descriptions
Location: Product gallery and homepage collection imagesReference ↗
What we found

Twelve images across the homepage and product page — including every photo in the Alpine Shell Jacket gallery — have no description, so a screen reader announces them as unnamed images or skips them entirely.

Why it matters

This fails WCAG 1.1.1 — the single most-cited violation in ADA web lawsuits. It also means a blind shopper using a screen reader can't tell what any product photo shows.

How to fix

Give every product image a short, factual description of what it shows — product name, color, and the detail the photo highlights. In most store editors this is the image's “alt text” field.

#02CriticalRule checkWCAG 4.1.2The discount-code field has no label
Location: Order summary, on the CartReference ↗
What we found

The cart's discount-code input relies on placeholder text alone. It has no label, so a screen reader announces it as just “edit text” with no clue what to enter.

Why it matters

This fails WCAG 4.1.2 — and it sits on the path to payment, exactly where accessibility lawsuits focus. An unlabeled checkout field blocks the exact people the law protects at the moment they're trying to pay.

How to fix

Add a real label to the field (visible, or screen-reader-only if the design requires it) — placeholder text is not a label.

View the full example report

4 findings, screenshot evidence, and the summary — exactly as a real scan delivers it.

More example findings

Every finding names the rule it breaks — and how to fix it.

The scan checks image descriptions, contrast, button and form labels, and keyboard access — each finding names the WCAG rule it fails and the page it came from.

highContrast & ReadabilityCart

Muted gray text is too light to read

This fails WCAG 1.4.3, one of the most common violations cited in accessibility demand letters. It shuts out low-vision and older shoppers, who are a large share of buyers.

mediumButtons & LinksFeatured product

Color swatch buttons have no accessible name

This fails WCAG 4.1.2 — a screen reader announces each swatch as just “button”, so a blind shopper can't choose between Slate, Moss, and Black. Color-only cues also fail shoppers with color blindness.

mediumKeyboard & StructureFeatured product (mobile)

The mobile menu can't be opened without a mouse or touch

Keyboard access is a core WCAG requirement (2.1.1) regularly cited in ADA suits. If the menu can't be reached without a mouse, most of the store is unusable for shoppers with motor impairments.

How findings are validated

The industry rulebook, plus eyes on the page.

Every finding is grounded in either a named WCAG rule failing on your live page, or something clearly visible in the captured screenshot — never advice that would apply to any store.

  • Real rules, not AI guesses

    The backbone is axe-core — the industry-standard WCAG engine used by accessibility professionals. Every rulebook finding cites the exact rule it fails.

  • A second pair of eyes

    A vision review reads the captured page for failures rule engines can't detect — text baked into images, unreadable contrast in practice, meaning shown by color alone.

  • We never claim you're compliant

    The report describes findings and risk. No overlay widgets, no compliance badges, no lawsuit-proof promises — regulators have fined companies for those.

  1. Open the real page

    A real browser loads your store exactly the way a shopper's does.

  2. Run the WCAG rulebook

    axe-core checks the live page against WCAG 2.1 A and AA — the rules ADA and EU law reference.

  3. Capture the evidence

    A full-page screenshot records what was checked, dated and kept with the findings.

  4. Look for what rules miss

    The vision review flags visual failures only if they're clearly visible — it never guesses.

  5. Translate into plain English

    Every finding ships as what we found, who it shuts out, and how to fix it — no jargon.

Who built this

Built by Andrew Basquin

I built CheckMyStore after watching store owners get sold widgets that promise compliance and don't deliver it.

This tool doesn't claim to fix your site automatically, because no tool honestly can. It tells you exactly what's broken, in plain English, so you or your developer can fix it properly. If a scan comes back clean, I'll tell you that too.

Questions, or want a second pair of eyes on a report? Email me directly at [email protected].

Why not an overlay?

A widget can't fix what it can't understand.

An accessibility overlay is a piece of code you paste into your store. It tries to patch problems in the browser, live, every time someone visits. Your actual store code never changes.

The trouble is that the hard parts can't be guessed by software. A machine can tell that a photo has no description, but it can't reliably write one that's actually right. Same with labelling checkout fields, or making a menu work by keyboard. The Overlay Fact Sheet, signed by over a thousand accessibility practitioners, documents this: automatic repair of image descriptions, form labels, and keyboard access is not reliable.

So the underlying problems stay in your store, and they come back every time your theme updates or you add an app.

$1 million

What overlay-widget company accessiBe agreed to pay to settle FTC charges. The FTC alleged it claimed its AI could make any website meet accessibility guidelines when it did not, and that it paid for reviews made to look independent. accessiBe did not admit or deny the allegations. The final order was approved April 22, 2025.

Source: FTC press release

1 in 4

Of the 1,037 US website accessibility lawsuits filed in the first three months of 2026, 265 — about 25% — were against websites that already had an accessibility widget installed. Having one did not prevent the claim.

Source: EcomBack Q1 2026 report

What we do instead

We don't add anything to your store. We scan your live pages, find the real problems in your own code, explain each one in plain English, and tell you how to fix it properly — so it stays fixed. If a page comes back clean, we say so.

Pricing

Start free. Pay only if you want it watched over time.

The free check is a real scan — no card, no sign-up, and you keep every finding it turns up. Monitoring is for when you want it re-checked as your store changes, with a dated record of what was found and when.

See where you stand — free.

Free Instant Check

$0

A real scan of your homepage against the WCAG rules ADA and EU law reference.

  • Scans your homepage, a product page, and your cart
  • Checked against the industry WCAG rulebook
  • Accessibility score (0–100)
  • Plain-English findings with the fix for each
  • Full-page screenshot evidence
  • No credit card required
Most popular

Stay covered as your store changes.

Store Monitoring

$199/month
Per store. Cancel anytime.

Monthly re-scans build a dated compliance record — your evidence of ongoing monitoring.

  • Everything in the Free Instant Check, re-run monthly
  • Automatic monthly re-scansBeta
  • Dated compliance record — your monitoring paper trail
  • New vs. fixed issue tracking between scans
  • Accessibility score history over time
  • Vision review that catches issues rule engines miss
  • Re-scan any time — each result added to your dated record
  • PDF export of your compliance record, anytime
  • Email alert when a new issue appearsComing soon

Cover every client store you manage.

Agency

$1,000/month
Up to 10 client stores.

Monitoring and compliance records for your client stores, under one plan.

  • Monitoring for up to 10 client stores
  • A separate dated compliance record per client
  • Everything in Store Monitoring, per store
  • White-label reports with your brandingComing soon
  • Add or swap client stores anytime
  • Priority support

The free check gives you the full report — findings, fixes, and screenshot evidence. Monitoring adds the monthly re-scan, the dated compliance record, new-vs-fixed tracking, and score history. Agencies: that's $100/store across 10 clients — and one dated record per client.

  • No changes are made to your store
  • Nothing is installed — no store access required
  • Free check before you pay
  • First payment fully refundable within 30 days
  • Cancel anytime

The legal context

Why this matters

The numbers, stated plainly. We're not going to tell you you're about to be sued — nobody can know that. This is just the context these rules sit in.

  • 1 in 6

    People live with a significant disability worldwide. If they can't use your store, they buy somewhere they can.

    World Health Organization

  • June 2025

    The European Accessibility Act came into force. It applies to stores selling to consumers in the EU.

    European Commission

  • 1,037

    US website accessibility lawsuits were filed in the first three months of 2026, up 5.49% from the same period in 2025.

    EcomBack Q1 2026

  • 44%

    Of those lawsuits named Shopify stores — 459 of the 1,037 filed.

    EcomBack Q1 2026

The honest version

A quick-fix widget won't make your store usable. Finding the real issues will.

  1. Real shoppers hit these failures every day — a screen reader that can't read your prices, a checkout a keyboard can't finish. They rarely complain. They just leave and buy somewhere they can.

  2. There's genuine legal exposure behind them, too: US accessibility complaints and the EU Accessibility Act both cite these same WCAG failures. We show you what's on your store — the legal read is yours and your lawyer's.

  3. You can't sticker your way out of it. The $49 overlay widgets don't fix the underlying issues, and regulators have fined vendors for claiming otherwise. Finding and fixing the real failures is what actually works.

That's what CheckMyStore does: find the real failures, explain each fix in plain English, and keep a dated record as you fix them — so you've got proof of good faith if it ever comes up.

See exactly what's blocking shoppers on your store —
and how to fix each one.

Scan My Store Free

60 seconds. Free. No card.

Honest limitations

What CheckMyStore does — and doesn't.

Automated checks catch many WCAG failures, but not all of them. Knowing the edges is part of trusting the results — and part of why the report never claims you're compliant.

What it does

  • Checks your live pages against WCAG 2.1 A and AA — the rules ADA and EU law reference
  • Explains every finding in plain English, with the exact fix
  • Builds a dated compliance record of scans, fixes, and re-checks

What it doesn't

  • Certify your store as compliant or lawsuit-proof
  • Replace a manual audit with real assistive-technology users
  • Give legal advice
  • Install overlay widgets or auto-“fix” your store

CheckMyStore inspects public ecommerce storefronts such as Shopify, WooCommerce, Wix, Squarespace, BigCommerce, Webflow, and custom builds. Some stores block automated browsing and may return partial results. Nothing is installed, no store access is required, and a manual review is recommended before making any compliance claim.

Common questions

Fair questions, straight answers.

How long does the free check take?

About a minute. A real browser opens your store, checks your homepage — plus a product page and your cart when it can find them — against the WCAG 2.1 A and AA rules, and writes up the findings in plain English. It's a real scan of your live store, not a demo.

Do I need to install anything or give you access?

No. We only look at your public pages, the same way any visitor's browser does. Nothing is installed, no store login is needed, and nothing on your store is ever changed.

Will you fix the issues for me?

No — we find them and tell you exactly how to fix them. Every finding comes with a plain-English fix that you or your developer can usually apply in minutes (most are things like adding image descriptions or darkening a text color). After you fix something, re-scan free to confirm it's resolved — the fix gets logged in your dated record.

How is this different from free checkers like Lighthouse or WAVE?

The rulebook layer is the same industry engine those tools use — we don't pretend otherwise. On top of it, a visual review reads the actual page for failures rule engines can't detect (text baked into images, contrast that's unreadable in practice), everything is translated into plain English instead of developer jargon, and every scan is saved to a dated compliance record. Free tools give you a one-off report; this builds your paper trail.

Will this make my store ADA or EAA compliant?

No tool can honestly promise that, and we never claim it — companies that sold "instant compliance" have been fined by regulators. What we do: find real failures of the WCAG rules those laws reference, help you fix them, and keep dated evidence that you're actively monitoring — which is the strongest position a store can be in. A manual review is still recommended before making any compliance claim.

What if my store passes the scan?

That's the best outcome — and still worth recording. Stores change with every theme update, new product, and app install, which is how issues quietly reappear. A dated record showing clean monthly scans is exactly what you want on file if a complaint ever arrives.

What happens after I subscribe?

Your store is re-scanned every month automatically. Each scan is added to your compliance record with the date, score, what got fixed, and anything new — and you can re-scan on demand right after shipping a fix or download the record as a PDF anytime. Cancel whenever you like, and your first payment is fully refundable within 30 days.

Who can see my report?

Only people you share the link with. Reports aren't listed publicly or indexed by search engines, and we don't share or sell your results. Your compliance record is your evidence — it's yours.

Find out what's costing you orders.

A real scan of your live store — every issue in plain English, with a screenshot and the exact fix for each. If your store comes back clean, we'll tell you that too.

No card required. Takes about a minute.