DEV Community

VibeFix
VibeFix

Posted on Edited on

What free accessibility checkers miss on a Shopify store

I'm building VibeFix.

You ran a free accessibility checker on your Shopify store. WAVE, axe or Lighthouse showed a handful of findings, or maybe none. It is tempting to read "nothing found" as "all good".

It isn't, and the people who write the standards say so. The W3C's guidance on choosing evaluation tools puts it plainly: "Tools cannot check all accessibility aspects automatically. Human judgement is required." It also says such tools "can not determine accessibility, they can only assist in doing so."

Even the tool makers say it. WebAIM, who make WAVE, state that "WAVE cannot tell you if your web content is accessible." Deque, who make axe, say their extension helps catch "57% of accessibility issues", which is their own figure and still leaves a lot for a person to look at.

So what falls through the gap?

What a checker can see, and what it can't judge

A checker reads the page code. That makes it good at things like a missing description on an image, a form field with no label, or text that is too faint against its background. Those are worth fixing, and a free tool finds them in seconds.

What it can't do is judge meaning or behavior. Here are the common gaps on a store.

1. Whether the alt text is any good.
A tool can tell you the alt text is missing. It cannot tell you whether what you wrote helps. The W3C's own quick-check page says "Automated tests can tell you if alt is missing", and leaves the judging to you: does the text give the same information the image gives, in context? A product photo described as "IMG_4521.jpg" or "image" passes a "has alt text" test and tells a screen reader user nothing.

2. Keyboard flow through menus and the cart.
Some visitors never use a mouse. They move with the Tab key. Can they reach every link, open the menu, get into the cart, and get back out? A scan of the page code can't press Tab for you.

3. Focus order.
When you tab through the page, focus should move in an order that makes sense. WCAG 2.4.3 (Level A) asks that focused items "receive focus in an order that preserves meaning and operability." A checker sees the code. It doesn't see that focus jumps from the header to the footer and back to the product grid.

4. Whether you can see where you are.
As you tab, the W3C says the focus should be "clearly visible", for example a border or highlight. Whether it really is, on your theme, is something you have to look at.

A 10-minute check you can do by hand

You need your keyboard and a browser. This follows the W3C's "easy checks" and adds store-specific spots.

  1. Tab through the homepage (about 3 minutes). Click the address bar, then stop using the mouse. Press Tab to move forward, Shift+Tab to go back. Can you reach every link, button and form field? Does the order follow the order you would read the page?
  2. Watch for the focus mark. Is it always clear which item is selected? If you lose track of it, a visitor using a keyboard will too.
  3. Open the menu with the keyboard. Use the arrow keys inside drop-downs. Can you get into the sub-menus and out of them again?
  4. Try the cart (about 3 minutes). Add a product and open the cart using only the keyboard. Can you change the quantity and reach the checkout button? Can you close the cart and carry on?
  5. Judge your alt text (about 2 minutes). Run WAVE on a product page. Look at the text it shows for each image. Would it make sense to someone who can't see the picture?
  6. Zoom the text to 200% (about 2 minutes). The W3C's check is simple: all text gets larger, nothing disappears or gets cut off, and nothing overlaps.

Write down what fails. Even a short list tells you where to start, and it is more than any scan alone gives you.

Where a free scan still fits

None of this means skipping the tools. Run one first, because it clears the easy, mechanical problems quickly, then do the manual pass for what it can't judge. If you want a comparison of the free options, with what each one can and can't do, we put one together: free Shopify accessibility checkers compared.

We also run a free check of our own. It is worth being clear about its limits, because they are the point of this article. It reads your public homepage only, and tests only what software can test of WCAG 2.0 and 2.1, Levels A and AA. It does not test keyboard use, focus, the cart or checkout. You can try the free Shopify homepage accessibility checker, then use the list above for the rest.

If you would rather have the issues fixed in your theme's code, that is what we do: our AI agent works on an unpublished copy of your theme, and you publish it yourself. Details are on VibeFix for Shopify stores.

No scan, ours or anyone's, can tell you whether your store meets a law, and nothing here is legal advice. The W3C also warns that a page "could seem to pass these checks, yet still have significant accessibility barriers", so a clean result is a starting point, not a finish line.

Top comments (0)