We checked. On 3 of 17 real Shopify stores, between 75% and 100% of the contrast failures reported by the free tools did not exist. On the other 14, every single one was real. The merchant gets the same report either way — and no way to tell which one they're holding.
The scan runs inside the Shopify app, on the store you install it on — we never scan a shop on someone else's say-so. The full report is free and stays free. This page itself collects nothing — no form, no cookies, no trackers, no third-party scripts.
Modern Shopify themes animate content as you scroll. Elements start at
opacity: 0 and fade in. A scanner that loads the page, waits a couple of seconds
and measures immediately catches those elements mid-fade — and reports the blended,
transitional color as a contrast failure.
Here is one real example, measured on a live store:
| What the free scanner measured | What the page actually renders |
|---|---|
#fdfdfe on #ffffff — ratio 1.01 |
#283992 on #ffffff — ratio 10.05 |
Text at 10:1 contrast — comfortably compliant — reported as a critical failure. Act on that report and you will "fix" a color that was never broken.
Of those same 17 storefronts, 11 scored in the green band (≥0.90) on the accessibility audit merchants and agencies reach for first. Ten of those eleven still had real, reproducible WCAG failures — 125 of them.
Part of that is scope. That audit lists 76 checks, but 10 of them are "please verify this yourself" reminders that run no test at all — including keyboard traps and visible focus indicators. Of the checks it does automate, it skips 18 WCAG A/AA rules entirely.
We test keyboard traps and focus visibility by actually pressing Tab, because
:focus-visible only applies to keyboard focus — calling .focus() in a script
would flag every site that implements it correctly. We also re-test layout at a 320px viewport
for reflow failures.
Most contrast failures are fixable without touching your brand. We work in OKLCH — a perceptually uniform color space — and move lightness only, holding hue and chroma, stopping at the first point that passes. When adjusting both the text and its background costs less visually than hammering one side, we do that instead.
Real color pairs from real storefronts, anonymized:
Across 1,286 contrast failures on 22 storefronts, 51.9% could be brought into compliance with a change most people cannot see. We label the rest honestly — "slightly visible" or "clearly different" — because a fix you'd reject is not a fix.
There are two ways to get the corrected colours onto your storefront, and they are genuinely different. We tell you which, so you can pick.
We tell you which setting and what value, and link you straight to that field in the theme editor. In practice a store's dozens of contrast failures collapse to two or three colour settings — about a minute of work.
The change is written into your own theme. It stays if you uninstall us. This is the version we recommend.
One click. We publish the corrected colours as a stylesheet through Shopify's app extension framework. It is always on — there is no toggle for shoppers to find, and an auditor testing your site in its default state sees the corrected colours.
This one is delivered by the app, so it stops applying if you uninstall. Included with Pro.
We never rewrite your theme files. Shopify gates that behind a separate exemption we do not hold — and having looked at both, we think a merchant changing two values they can see beats an app silently rewriting theme code. Where we do write — product alt text and the statement page — every change stores its previous value and can be rolled back.
No card. No trial clock.
7-day trial. Cancel anytime.
Every answer this scanner can give you is free, permanently — including exactly what to change. Pro does not unlock answers. It does the repetitive parts for you and remembers to check when you do not, because compliance is a continuing obligation, not a one-time cleanup.
This is a private beta built by one person. The most useful thing you can send us is not praise — it is the specific thing we got wrong: a finding that is not real, a fix that would have broken your storefront, a problem we missed entirely, or a reason the whole approach does not fit how you actually run your shop.
Email hello@maycomayco.com. No form, no ticket number, no autoresponder — it goes to a person who will read it and write back.
If you run a store and want to argue with the numbers on this page, we will happily send you the raw scan data behind them so you can check our work.
No tool makes you compliant, and anyone who tells you otherwise is selling something. Automated testing can only reach about a third of WCAG's success criteria. The rest — whether your alt text is meaningful, whether your page order makes sense, whether a custom widget is actually operable — needs a person.
We tell you which findings we can fix, which need your judgment, and which live inside third-party embeds we can't touch. We do not overlay a widget on your storefront and call it done. We do not write alt text by guessing what's in your photos — we use the product title and variant you already entered, because an invented description is worse than none.
The European Accessibility Act has applied since June 2025. If you sell to consumers in the EU, WCAG 2.1 AA is the operative standard, and "we installed a plugin" is not a defense. We are not lawyers and this is not legal advice.