By platform · WooCommerce
You Control the WooCommerce Checkout, So Test It
WooCommerce hands you the whole purchase flow, so nothing is off-limits and nothing is somebody else's problem. Core got a great deal better in 2025. What breaks it now is usually a theme or a plugin overriding what core does.
Last reviewed August 30, 2026
For the store owner or developer running WooCommerce who needs the purchase flow to work for everyone.
WooCommerce sits on WordPress, so everything in our WordPress guide applies here first. The theme, the builder, the plugins, the media library full of blank alt text.
What is different is the stakes and the ownership. A blog with a barrier loses a reader. A checkout with a barrier loses a sale and can generate a complaint, and e-commerce is around 70 percent of US digital accessibility lawsuits. You also own every line of that checkout, which means there is nobody upstream to report anything to.
Before any of the detail, answer one question, because it decides which half of this page applies to you. Which checkout are you on? Stores built since late 2023 default to the Cart and Checkout blocks. Older stores are usually still on the classic shortcode, which is supported and still gets bug fixes, and which is not where the accessibility work went.
What breaks on WooCommerce
The failures we find most often on this platform, and the rule each one breaks.
Quantity selectors and variation dropdowns your theme restyled
Themes turn these into custom controls and lose the label and the state on the way. WooCommerce says the same thing about itself, that theme styles can override what WooCommerce sets, which makes your theme the first place to look rather than the last.
4.1.2 Name, Role, Value
Add-to-cart confirmation your theme swallowed
Core announces cart totals, variation changes and checkout interactions through ARIA live regions now, and that landed as part of 140 accessibility improvements in the year to July 2025. Themes and plugins that replace the cart markup drop the live region along with it, and the count starts updating in silence again.
4.1.3 Status Messages
Checkout validation, once a plugin has touched it
Core puts each error next to its own field and wires it to the input with ARIA attributes. Checkout field editors and one-page checkout plugins rewrite that markup, and the wiring is the first thing to go, because it is invisible in a browser and nothing complains when it disappears.
3.3.1 Error Identification
Payment gateway iframes
Stripe and PayPal fields load inside iframes that often carry no title, and focus handling across that boundary is inconsistent. This one is ours from auditing rather than documented by either company, so check yours rather than assuming.
4.1.2 Name, Role, Value
Third-party product filters
Core's own product filters got keyboard work in that same year of improvements. The price sliders and attribute filters most stores actually run come from plugins, and those are still usually mouse-only, with results that change without anything being announced.
2.1.1 Keyboard
The product gallery lightbox
The default gallery is three third-party libraries stacked together for swiping, zoom and the lightbox, which is why it is the weakest part of a WooCommerce product page. Core's modal work in 2025 may well have improved its behavior, and we have not retested it since. Test yours by keyboard rather than taking either of us at our word.
2.1.2 No Keyboard Trap
The plugin question, answered
WooCommerce inherits the whole WordPress plugin ecosystem, so the testing plugins in our WordPress guide apply here as well.
The store-specific advice runs the other way, though. The plugins most likely to break your checkout are the ones somebody added to improve it.
Accessibility Checker (Equalize Digital)
A checker running inside WordPress, page by page and product by product.
- What it does
- It checks product pages as they are created, which matters when a catalog grows every week and nobody is going back over last month's.
- What it cannot
- Automated rules only, and it cannot walk a purchase flow from product page to confirmation, which is the part that decides whether anyone can buy from you.
Checkout field editor plugins
Tools for adding, removing and reordering fields in the checkout.
- What it does
- Fewer fields means fewer chances to fail and a shorter flow for every customer, which is worth doing on its own merits.
- What it cannot
- They frequently output fields with no properly associated label, and they are one of the two things most likely to undo core's error wiring. Test every field you add and every error it can produce.
One-page checkout plugins
Plugins that condense the whole flow onto a single screen.
- What it does
- Fewer page loads can mean less to get lost in, particularly for somebody who finds navigation tiring.
- What it cannot
- They update content dynamically and frequently announce none of it, so a screen reader user does not learn that the shipping cost changed or that the total moved.
Overlay widgets (accessiBe, UserWay, AudioEye and the rest)
A script you paste into your template that draws a toolbar for visitors and claims to repair your pages automatically as they load.
- What it does
- The toolbar half is real. Bigger text, higher contrast, adjusted spacing and a reading guide are preferences some visitors use, and the field's own reference document on overlays says a non-trivial array of accessibility problems can genuinely be repaired this way.
- What it cannot
- It does not change the markup your server sends, and the categories it handles worst are the ones that decide whether a site works at all. Text alternatives, form labels and error handling, and keyboard access. More than 5,000 US digital accessibility lawsuits were filed in 2025, and the firm that compiles that dataset reads the filings the same way every year, which is that widgets do not materially reduce legal risk. Our overlays page has the documented record.
What to actually do
- Buy something from your own store using only the keyboard, start to finish. Do this before anything else on the list, because it tells you more in five minutes than a scan tells you in an hour.
- Repeat it with a screen reader running. Listen for the cart total, the shipping change and the error messages, and note anything that happens in silence.
- Check that every checkout field has a visible label that is programmatically connected to it, especially any field a plugin added.
- Make a payment fail on purpose. Confirm the error moves focus to the problem rather than only appearing in a notice at the top of the page.
- Test product filters and variation selectors by keyboard, including whether the result count is announced when the grid changes.
- Run the free 10-page scan across shop, category, product, cart and checkout pages to catch the mechanical failures underneath all of that.
On themes and templates
Storefront, WooCommerce's own theme, carries the accessibility-ready tag in the WordPress theme directory, which means the theme review team checked it against a published set of requirements. That tag is not a WCAG claim and WordPress says so itself. It is still a safer starting point than most commercial store themes, which tend to restyle the cart and the checkout with custom markup, and restyling is exactly where the damage happens. Whatever theme you run, WooCommerce's own sentence is the one to keep. Theme styles can override what WooCommerce sets.
One honest limit
The purchase flow is the part of your store that matters most and the part a scanner is worst at, because checking out is state changes, dynamic totals and validation, and a scan of the kind you run for free loads a page and reads what is already there. Automation can be scripted through a checkout, and teams do build that, but somebody has to write each step and decide what a correct result looks like, which is most of the work an auditor was going to do anyway. So it needs a person going through the whole thing from product page to confirmation, which is what our checkout audit does. WooCommerce publishes an accessibility conformance report for its own current release, which is more than most platforms manage, and it describes core rather than your store.
Keep reading
Other platforms
WooCommerce
We test all 55 WCAG 2.2 A and AA rules on your WooCommerce site, with an expert review and a real blind screen-reader user on your key journeys. Every finding screenshotted and mapped to its fix. $499, report in 5 business days.