Free toolAccessibility Audit

Shopify accessibility checker

Enter a store address and see which common WCAG 2.1 problems appear on the home page and two product pages: images without alt text, form fields without labels, buttons and links without a name, zoom blocking, a missing page language and more.

Anonymous: we keep only daily counts of checks. Store addresses and results are not saved, and there are no tracking cookies in the tool.

We check the rendered HTML of 3 public pages, respecting robots.txt. Nothing is saved and no login is needed. An automated check cannot show that a store conforms to WCAG or the European Accessibility Act. Not legal advice.

Free tool

How it works

  1. 01Enter a store address

    Any Shopify store with a public storefront.

  2. 02We check 3 rendered pages

    The home page and two product pages, with the element rules of the app’s scanner, each linked to a WCAG 2.1 success criterion.

  3. 03See the summary

    Issues by rule and criterion, with up to three examples of the markup involved.

The full check

Accessibility Audit checks the theme code itself

This page checks the HTML a visitor receives. The app scans the theme’s Liquid, CSS and colour settings, including colour contrast and focus styles, shows the file, line and WCAG criterion of every issue, offers patches for common fixes and compares scans to catch regressions, with no overlay script on your storefront.

About Accessibility Audit
FAQ

Questions about this tool

Which WCAG criteria are checked?

Selected Level A and AA success criteria of WCAG 2.1 that can be checked in markup: 1.1.1 Non-text Content, 1.3.1 Info and Relationships, 1.4.2 Audio Control, 1.4.4 Resize Text, 1.4.10 Reflow, 2.1.1 Keyboard, 2.2.2 Pause, Stop, Hide, 2.4.3 Focus Order, 2.4.4 Link Purpose, 2.4.6 Headings and Labels, 2.4.7 Focus Visible, 3.1.1 Language of Page, 3.3.2 Labels or Instructions, 4.1.1 Parsing and 4.1.2 Name, Role, Value.

Does a clean result mean the store is accessible?

No. Automated checks find only part of the problems; keyboard use, screen reader output, contrast in context and content need manual testing. A clean result is not a conformance statement for WCAG or the European Accessibility Act.

What is the difference between this check and the app?

This check reads rendered pages, including content added by apps. The app reads the theme code, so it can point to the file and line, check colour settings and offer patches, and it keeps a baseline to catch new issues.

Why can results include false positives?

Some stores set alt text or labels with JavaScript after the page loads. The check skips elements whose names are bound by common frameworks, but a few may still be reported. Check each example in the browser.

All free tools →

Guides