# WooCommerce accessibility checker
URL: https://pandus.online/en/woocommerce-accessibility-checker
Updated: 2026-10-14

Free WooCommerce accessibility checker: test a shop page against WCAG 2.2 AA and see how to fix theme, page builder and plugin problems in WordPress.

Enter the address of any page of your WooCommerce shop: we test it against WCAG 2.2 A and AA in a real browser and explain every problem with a fix for WordPress themes, page builders and plugins. Free, no signup, about a minute. An automated check, not a full audit.
No signup
WCAG 2.2 A and AA
Fixes for WordPress themes
Tests one WooCommerce shop page against WCAG 2.2 levels A and AA with axe-core in a real browser
Explains each problem in plain words with a fix for themes, child themes, page builders and plugins
Finds images without alt text, low contrast, unlabelled checkout fields and nameless icon buttons
Free WordPress plugin shows the problems next to every page, post and product
Automated check, not a full audit: tells you what still needs manual testing
## What the WooCommerce accessibility checker tests

The scan opens your page in Chromium, runs [axe-core](https://github.com/dequelabs/axe-core), the open-source rules engine also used by Lighthouse, and maps every finding to a WCAG 2.2 success criterion and to EN 301 549, the European standard behind the EAA. Each finding is explained by a card from our [rule library](https://pandus.online/en/rules) with a separate note for WooCommerce.

Test the pages your customers use: the home page, a category, a variable product, the cart and the account login. The checkout form needs a product in the cart, so test it with the browser extension. A shop in maintenance mode or behind a login can be checked with our free [browser extension](https://pandus.online/en/accessibility-checker-browser-extension).

## Typical problems in WooCommerce shops

In WordPress, markup comes from three places: the theme, the page builder and plugins. The WooCommerce notes of our rule cards say where each problem usually sits:

| Problem | Where it usually comes from | How to fix it |
| --- | --- | --- |
| Buttons without a name (critical) | Themes, page builders, cart and wishlist plugins | Add labels in child-theme templates or plugin settings; report plugin buttons to the plugin author |
| Dropdowns without a label (critical) | Variation selectors, sorting dropdowns, plugin widgets | Add labels in child-theme templates or use plugin settings that output proper labels |
| Form fields without a label (critical) | Checkout, account and search forms; form and checkout plugins | Add labels in child-theme templates or use plugin options that output real `<label>` elements |
| Low text contrast (serious) | The active theme or page builder | Change colours in the customizer or global styles, or override them in child-theme CSS |
| Images without alt text (serious) | Media Library images, sliders, plugin images | Fill in the Alternative Text field in the Media Library and check that the theme outputs it |
| Links that do not say where they go (serious) | Header icons, the mini-cart, social-icon plugins | Add text labels in the child theme or choose plugin settings that output accessible labels |
| Hidden elements reachable by keyboard (serious) | Mobile menus, sliders, pop-up and cookie plugins | Fix it in child-theme code or report it to the plugin author |
| Heading levels that skip a step (moderate) | Page-builder widgets, theme widget titles, product loop titles | Set the level in the block editor or builder (it is separate from the size); change theme titles in a child theme |
| Targets too small to tap (moderate) | Variation swatches, quantity inputs, icons | Increase size or padding in child-theme CSS |


## Fix it so updates do not undo it

- **Theme:** use a child theme, the customizer or global styles. Edits made directly in the parent theme disappear with the next update.
- **Page builder:** most heading, button and image widgets have settings for the level, the label and the alt text.
- **Plugins:** if a problem sits inside a plugin's output, report it to the author with the finding from the report, or look for a setting that changes the markup.
- **Content:** alt text in the Media Library, link texts and headings in product descriptions are yours to write.

## The free WordPress plugin

Our [WordPress plugin](https://pandus.online/en/wordpress-accessibility-plugin) works with WooCommerce. It shows the problems next to every page, post and product in the WordPress admin, suggests fixes you review and approve, checks image descriptions and colours in the editor, and adds an accessibility information page and a "Report a barrier" form. It does not add an overlay widget and does not change the theme on its own.

## What the checker does not do

It does not change your shop or add an overlay. It finds the part of WCAG problems a machine can detect; whether an order can be placed with a keyboard and a screen reader, whether alt text is meaningful and whether error messages are clear needs a person. Our [WCAG 2.2 checklist](https://pandus.online/en/wcag-2-2-checklist-online-shops) lists what to test by hand.

On a paid plan we check every page of the shop every week and write reports for the owner in seven languages; agencies get them under their own brand. Selling to consumers in the EU? Take the [three-question EAA filter](https://pandus.online/en/who-does-the-eaa-apply-to) to see whether the European Accessibility Act applies. For a Shopify store, use the [Shopify accessibility checker](https://pandus.online/en/shopify-accessibility-checker).

## Frequently asked questions

### Is there a free WooCommerce accessibility checker?

Yes. Enter the address of a shop, category, product or cart page above. We test that one page against WCAG 2.2 A and AA for free, without an account, and show each problem with a WordPress fix.

### Is there a WooCommerce accessibility plugin?

Yes. Our free WordPress plugin connects the site to Pandus and shows the problems next to every page, post and product in the admin, suggests fixes you approve and adds an accessibility information page. It does not add an overlay.

### Why fix problems in a child theme?

Changes made directly in a theme are lost when the theme updates. A child theme, the customizer or global styles keep your fixes after updates.

### Can you check the WooCommerce checkout?

Partly. With an empty cart WooCommerce usually sends visitors from the checkout back to the cart, so the online scanner sees the cart page. To test the checkout form, add a product to the cart in your own browser and run our free browser extension there.

### Does the result show that my shop meets the EAA?

No tool can show that. An automated check finds a part of WCAG problems; keyboard, screen reader and content checks by a person are still needed. It is not legal advice.

Q: Is there a free WooCommerce accessibility checker?
A: Yes. Enter the address of a shop, category, product or cart page above. We test that one page against WCAG 2.2 A and AA for free, without an account, and show each problem with a WordPress fix.

Q: Is there a WooCommerce accessibility plugin?
A: Yes. Our free WordPress plugin connects the site to Pandus and shows the problems next to every page, post and product in the admin, suggests fixes you approve and adds an accessibility information page. It does not add an overlay.

Q: Why fix problems in a child theme?
A: Changes made directly in a theme are lost when the theme updates. A child theme, the customizer or global styles keep your fixes after updates.

Q: Can you check the WooCommerce checkout?
A: Partly. With an empty cart WooCommerce usually sends visitors from the checkout back to the cart, so the online scanner sees the cart page. To test the checkout form, add a product to the cart in your own browser and run our free browser extension there.

Q: Does the result show that my shop meets the EAA?
A: No tool can show that. An automated check finds a part of WCAG problems; keyboard, screen reader and content checks by a person are still needed. It is not legal advice.