Find the accessibility defects in your store — and the theme file each one lives in.
A real browser opens your storefront, tests it against WCAG 2.2 AA, and shows you every broken element with a screenshot, the success criterion it fails, and the Shopify section file it was rendered from. Free, no account, about a minute.
Scanning
A real page load takes as long as a real page load. Leave this open.
What you get
Evidence, not a score
Every defect arrives with a screenshot of that element on your own storefront, the WCAG 2.2 success criterion it fails, and the markup that failed it.
The file, not a selector
On Shopify we resolve each defect back to the section it was rendered from — sections/main-product.liquid — so a developer opens one file instead of hunting through a theme.
An honest boundary
We separate what a machine can measure from what needs a person with a screen reader. A scan result is not a legal opinion, and we never present it as one.
Why the file name is the whole point
Most scanners hand a merchant a CSS selector like .card__inner > button:nth-child(2). Nobody can act on that. Shopify renders every section inside a wrapper that names the section it came from, so the rendered page alone is enough to point at the right file — before you install anything, before you have trusted us with access to your theme.
Line numbers and one-click repair need the theme source, which needs the app installed. The scan is honest about which is which.
What this scan does not do
- It does not test your checkout — Shopify controls those pages, not your theme.
- It does not detect every barrier. Automated rules catch the measurable subset; keyboard traps, unclear flows, and confusing copy need a human tester.
- It does not tell you whether you meet a legal standard. It tells you what it found, where, and what a fix would involve.