Accessibility Plugins for WooCommerce Stores Selling into the EU (2026)
Ecommerce is explicitly within the scope of the European Accessibility Act, and if you ship to EU consumers you are covered regardless of where your business sits. That much most store owners have now heard. What they have not heard is which part of a WooCommerce store actually fails, and it is almost never the blog.
It is the variation selector, the faceted filter sidebar, and the checkout. Those three components fail accessibility more reliably than anything else in WordPress, they are the components that carry your revenue, and they are largely determined by your theme and your plugins rather than by anything you wrote. This article covers the specific failures, then the tools that find them.
Verified August 2026. Our EAA compliance guide covers the legal requirements and deadlines in full.
Where stores actually fail
- Variation selectors. Colour and size swatches are frequently built as unlabelled divs with click handlers, which means a keyboard user cannot reach them and a screen reader user does not know what they are. If your product page uses image swatches, test it first.
- Faceted filters. Filter sidebars that update results via AJAX usually announce nothing, so a screen reader user applies a filter and has no idea whether anything changed. This needs a live region and almost never has one.
- Checkout error handling. A validation error that appears visually but is not announced, or that does not move focus, leaves people stuck on a form they cannot complete. This is the single most expensive accessibility failure in ecommerce.
- Cart updates. Quantity changes and removals that update silently. The user hears nothing and cannot tell whether the action worked.
- Product gallery. Lightboxes that trap keyboard focus, or that cannot be closed with Escape.
- Cookie banner over the checkout. A consent banner covering the focused field is a WCAG 2.2 Focus Not Obscured failure and it happens on a startling number of stores.
The 6 options compared
1. Equalize Digital Accessibility Checker
The WordPress-native scanner, checking content in the editor across more than 40 checks. For a store its value is on product content at scale: alternative text on product images, heading structure in descriptions, and link text that says something other than “read more” across a catalogue of thousands.
There is a free version, and paid plans start at $190 a year with unlimited page scanning and no per-page or API fees, which matters enormously for a catalogue site where per-URL pricing would be punishing. It scans product pages as content, so it will find your missing alt text across 3,000 products. It will not tell you the variation swatch is unreachable by keyboard, because that is a rendered interaction rather than content.
- Pricing: Free version; paid from $190 a year, unlimited pages
- Finds: Product content issues across a large catalogue
- Best for: Catalogue-scale content problems
- Watch out for: Does not test interactive components
2. axe DevTools
The free browser extension that examines the rendered page, which is where store failures live. Run it on a product page with variations selected, on a category page with filters applied, and on each checkout step, because those are different DOM states and a scan of the default view misses most of what matters.
It reliably catches missing labels on form controls, ARIA misuse on swatches, and contrast failures in sale badges and error messages, all of which are common in WooCommerce themes. It also handles the WCAG 2.2 target size and focus appearance criteria that matter on mobile checkouts. The output is developer-oriented, which suits this job since the fixes are usually in theme templates or CSS rather than in your content.
- Pricing: Free extension; paid tiers for teams
- Finds: Rendered-page failures in variations, filters, and checkout
- Best for: The components that actually break
- Watch out for: Scan each DOM state, not just the default view
3. WAVE
WebAIM’s free extension, and the most useful of the scanners for a non-technical store owner because it annotates the page visually. Seeing a contrast icon sitting on your sale price tells you more, faster, than a rule identifier in a list.
Contrast is where it earns its place on a store specifically. Sale badges, discount percentages, stock warnings, and “only 2 left” messages are almost always low-contrast because they are designed to look urgent rather than to be readable, and they carry information a customer needs. Run WAVE across your product template, category template, and cart, and fix contrast first: it is the highest-frequency failure and usually a CSS change. API access from around $100 a month for 1,000 page credits exists if you want to scan a catalogue programmatically.
- Pricing: Free extension; API from around $100 a month
- Finds: Contrast failures in badges, prices, and warnings
- Best for: Store owners without a developer
- Watch out for: One page at a time in the free version
4. Your theme
The largest single determinant of whether your store is accessible, and the one nobody treats as an accessibility decision. Your theme supplies the markup for variation selectors, filters, cart, and checkout, which is precisely the list of things that fail.
Themes with a serious accessibility posture, including GeneratePress, Kadence, Astra, and Blocksy, ship cleaner markup and sensible focus handling than most premium multipurpose themes, and Twenty Twenty-Five as a default block theme is built to core standards. The practical test before you commit: install the theme on staging with WooCommerce, then buy something using only a keyboard. If you cannot select a variation or dismiss the gallery lightbox, no plugin will rescue that, and switching theme early is far cheaper than remediating one later.
- Pricing: Free to around $100 a year depending on theme
- Determines: Variation, filter, cart, and checkout markup
- Best for: Getting the baseline right before anything else
- Watch out for: Test with WooCommerce installed, not on a demo
5. Pa11y CI
Free and open source, and the way to stop a plugin update quietly breaking your checkout. Stores install more third-party code than any other WordPress site type, and every payment gateway, filter plugin, and upsell widget can introduce a failure into a template you already fixed.
Point it at a representative URL list, a product page, a category page, the cart, and the checkout, then fail the build when new issues appear. For a store that updates plugins weekly, this catches regressions at the point they are cheap to fix rather than after a customer complains. It needs a deployment pipeline and technical setup, so it suits stores with a staging workflow and rules out those editing production directly.
- Pricing: Free, open source
- Finds: Regressions introduced by plugin and theme updates
- Best for: Stores with a staging and deployment process
- Watch out for: Requires technical setup
6. Buying something with a keyboard
Free, takes twenty minutes, and finds more genuine problems than every scanner in this article combined. Unplug your mouse and complete a real purchase: find a product, select a variation, add to cart, apply a coupon, and check out.
Automated tools detect roughly 30% of WCAG issues, and the checkout failures that cost you money are mostly in the other 70%. You will discover whether focus is visible against your background, whether the cookie banner covers the field you are typing in, whether an error message moves focus to the problem, and whether you can escape the gallery lightbox. Do it again with a screen reader on the same journey if you can. This is the test that maps directly onto lost revenue, because a customer who cannot complete checkout does not file a bug report, they leave.
- Pricing: Free
- Finds: The failures that actually block purchases
- Best for: Every store, before spending anything
- Watch out for: Repeat after theme and checkout plugin changes
Comparison table
| Option | Cost | Catalogue scale | Interactive components | Checkout journey |
|---|---|---|---|---|
| Equalize Digital | Free, or $190/yr | Yes, unlimited | No | No |
| axe DevTools | Free | Per page | Yes | Per step |
| WAVE | Free; API ~$100/mo | Per page | Contrast | Per step |
| Your theme | Free to ~$100/yr | Determines markup | Determines markup | Determines markup |
| Pa11y CI | Free | By URL list | Partial | Yes, automated |
| Keyboard testing | Free | No | Yes | Yes, definitively |
A store remediation order that works
- Fix checkout first. It carries all your revenue and it is where failures are most costly. Everything else can wait a week.
- Then contrast, everywhere. Sale badges, stock warnings, error messages, and placeholder text. Usually one CSS pass, and it removes a large share of automated findings.
- Then variation selectors. If a keyboard user cannot choose a size, they cannot buy. Test with your most complex product.
- Then filters. Add a live region so results updates are announced, or accept that filtering is unusable non-visually.
- Then product content at scale. Alternative text across the catalogue, which is where an in-editor scanner earns its licence.
- Then hold the line. Automated checks in CI, or a keyboard pass after every checkout-adjacent plugin update.
That order is deliberately revenue-weighted rather than severity-weighted. A store that fixes its checkout and its contrast has addressed most of the practical barriers and most of the commercial risk, even before it has a complete conformance programme.
Related guides
Frequently asked questions
Does the EAA really cover my store?
Ecommerce is explicitly in scope, and it applies to businesses outside the EU that offer products or services to EU consumers. If you ship to Europe, assume you are covered and check the microenterprise provisions rather than relying on them.
Will an overlay widget cover this?
No, and it may worsen your position. accessiBe settled with the FTC for $1 million over automatic-compliance claims, and 456 of 2,014 US accessibility lawsuits in 2025 hit sites that already had one installed. Fix the checkout instead.
My theme is not accessible. Do I have to switch?
Not necessarily, since many issues are fixable with CSS and template overrides. But if variation selection or checkout is fundamentally broken, switching early costs less than remediating and re-remediating after every theme update.
How do I handle thousands of missing alt texts?
Prioritise by traffic: your top few hundred products first. Generated alt text is a reasonable starting draft for the long tail provided someone reviews the high-value pages, since a wrong description is worse than a considered one.
Does accessibility affect conversion?
Most of these fixes are usability fixes. Clear focus states, announced errors, readable stock warnings, and large enough tap targets help every customer on a phone, not only those using assistive technology.
What about my cookie banner?
Test the checkout with it showing. A banner that covers the focused field fails WCAG 2.2 Focus Not Obscured, and because it appears before consent it is present for exactly the visitors you have not yet converted.
The verdict
Before you spend anything: buy something on your own store using only a keyboard. Twenty minutes, no cost, and it will find the failures that are costing you sales right now.
For catalogue-scale content: Equalize Digital at $190 a year with unlimited page scanning, which is the pricing model that matters when you have thousands of product pages.
For the components that break: free axe DevTools and WAVE, run against product pages with variations selected, filtered category pages, and every checkout step separately.
And treat your theme as an accessibility decision. It supplies the markup for variations, filters, and checkout, which is the entire list of things that fail. Getting that right first makes everything after it cheaper.
