Know what to fix. Prove you fixed it.
A11y Suite opens your storefront in a real browser, checks it against WCAG 2.2 AA, and tells you which theme file or setting to change. It adds nothing to your storefront — no widget, no overlay, no script.
What a finding looks like
seriousbutton-name1 element · Search results
Buttons must have discernible text
A button has no readable name — a screen reader announces just “button”, so the shopper cannot tell what it does. Icon-only buttons (search, close, cart) are the usual cause.
Where to fix: the search submit button in sections/main-search.liquid — add aria-label="Search"
- Checks templates, not a list of pages
One product page stands for your whole catalogue, so a single fix clears the same problem everywhere it appears — and your cart and search results get checked too, which sitemap crawlers miss.
- Says where to change it
Not “colour contrast failed” — which theme setting, which Liquid file, and the replacement to paste. It also warns you when a change would break something, like alt text your theme uses to group variant images.
- Leaves a paper trail
Dated before-and-after results you can hand to a lawyer, an auditor, or a customer who asks.
Automated testing finds roughly a third of accessibility barriers. No app can make a store compliant on its own — we tell you what we found, what we didn’t check, and what still needs a person.