Worried your store isn't ADA compliant? See what a free scan finds.
See what stops disabled shoppers from buying on your Shopify or WooCommerce store, then get a report your developer can act on: the failing code, the fixed code, and a re-scan that proves it. No widget to install, no subscription.
- Free, about 20 seconds
- Nothing installed on your store
- Shopify and WooCommerce
- Cart button has no nameScreen readers say “button”. Fix: add aria-label.
- Low contrast price2.9:1, needs 4.5:1. Fix: darken the text colour.
Why store owners are checking now
- 44%
- of US website accessibility lawsuits in early 2026 were filed against Shopify stores.
- 1 in 4
- stores that were sued already had an accessibility widget installed.
- 24 h
- from order to report, with one payment and no call.
Lawsuit figures: EcomBack, Q1 2026 ADA website lawsuit report.
How it works
- 1Scan a page for freePaste your store address. You see the most serious issues on that page in about 20 seconds.
- 2Order the full reportWe scan up to 150 pages, including the cart on Pro, and email the report within 24 hours.
- 3Your developer fixes the codeEach issue comes with the failing markup and the corrected markup, plus Shopify and WooCommerce notes where they apply.
- 4Re-scan to prove itA second report shows what changed, with a date, for your records.
What your developer receives
- Every issue, grouped by template
- A product page problem shows up once with a count, not 400 times.
- The failing code and the corrected code
- Copied from your pages, with the change marked, so a fix takes minutes instead of research.
- Shopify and WooCommerce notes
- For most issues, where the fix lives in your theme or plugin settings.
- A 30, 60 and 90 day order of work
- Critical issues first, grouped so one change fixes many pages.
- A re-scan after the fixes
- Proof of what changed, as a second report.
<button class="cart-toggle">
<svg>…</svg>
</button>
<button class="cart-toggle"
aria-label="Open cart, 2 items">
<svg aria-hidden="true">…</svg>
</button>A report, not a widget
Accessibility widgets add a toolbar on top of your store. They don't change the code that causes the problems, which is why so many sued stores had one.
| Feature | Accessibility widget | FixRamp report |
|---|---|---|
| Fixes the underlying code | No, adds a script on top | Gives your developer each code change |
| Cost | A monthly subscription | One payment, from US$99 |
| Proof of the fixes | None | A dated re-scan report |
| Added to your store | A third-party script | Nothing |
Pricing
One payment per report. Prices in US dollars. Applicable sales tax is calculated at checkout.
Spot check
Your home page and one product page: the two templates most shoppers see, with the code fixes.
$99one payment
- 2 pages scanned
- USD 99 credited if you upgrade to Starter or Pro within 30 days
Starter
For smaller stores: your home page, collections and top product pages.
$249one payment
- 25 pages scanned
- 1 re-scan included
Pro
For growing stores: up to 150 pages, including the cart.
$599one payment
- 150 pages scanned
- 3 re-scans included
Re-scan after fixes: $99. After your developer has made the fixes.
Popular accessibility widget plans start around USD 490 a year, every year, and do not change your store's code. A FixRamp report is one payment, and the fixes stay in your theme.
Our promises
- Fewer than 5 issue instances found: full refund, automatically.
- Changed your mind: ask for a refund within 7 days, for any reason.
- Your included re-scan still flags an issue we gave you code for: reply to the report email and we run one more re-scan free.
Order a report
Questions
Does this make my site compliant?
No report can promise that, and we don't. FixRamp tells you what automated testing finds and how to fix it. Some issues can only be found by people testing with assistive technology, and we say so in every report.
Who does the fixing?
Your developer, or you if you edit your own theme. The report is written so that someone who knows HTML and CSS can apply each fix without prior accessibility experience.
Is the report written by people?
The scan is automated and the explanations come from a reviewed fix library, assembled with AI assistance. Every issue in the report traces back to something the scanner found on your pages.
Does it work with my Shopify or WooCommerce theme?
Yes. We scan the pages your customers see, whatever theme you use, including Dawn and Horizon. For most issues, the report tells your developer where the fix lives in your theme or plugin settings. Other platforms can be scanned too.
My theme says it's accessible. Isn't that enough?
A theme starts out accessible, but your colours, content, apps and edits change the code your customers get. In our October 2026 scan of 501 Shopify homepages, 82% of the 74 Dawn homepages (Dawn is Shopify's own free theme) had text with too little colour contrast. The scan checks your store as it is today.
What about checkout?
On Shopify, checkout is hosted and maintained by Shopify, so we don't scan it and you can't edit its code. We scan everything that leads to it: home, collections, product pages and the cart.
I already have an accessibility widget. Do I need this?
A widget adds a toolbar to the page, but it doesn't change your store's code, which is where these issues are. We don't install anything; the report gives your developer the code changes.
Will this protect me from a lawsuit?
No one can guarantee that, and we don't. What you get is a dated record: the issues found, the fixes made, and a re-scan showing what changed. Your lawyer can decide how to use it.
What can't an automated scan find?
Automated testing finds only part of the problems. Whether alt text actually describes the image, or whether a screen reader flow makes sense, needs a person testing. Every report explains what automated testing cannot cover.
I sell in Ontario. Does this help with AODA?
Under AODA, Ontario businesses with 50 or more employees must make their public website meet WCAG 2.0 level AA. Smaller businesses are not required to, but the same fixes help every customer. The scan tests WCAG 2.2 A and AA rules, which cover those checks, so the report is a practical to-do list. It is engineering guidance, not a legal opinion.
Do you install anything on my site?
No. We read your public pages the way a browser does. We never ask for passwords and never add scripts or overlays.