WooCommerce accessibility: make your store WCAG- and EAA-ready
WooCommerce doesn't decide whether your store is accessible — your WordPress theme, your plugins, and the content you publish do. Most WooCommerce accessibility failures are a handful of recurring issues in the theme and product content, not something WooCommerce itself got wrong. Since the European Accessibility Act became enforceable on 28 June 2025, those failures also carry real compliance risk for EU/UK stores. Here is what commonly breaks, and how to check yours.
Why WooCommerce accessibility is a WordPress question
WooCommerce is a plugin on top of WordPress, so “is WooCommerce accessible?” really means “is your WordPress setup accessible?” Three things you control decide the outcome:
- Your theme. The WordPress theme controls colours, focus styles, heading structure, and how product grids, menus, and carousels are built — the single biggest factor, and entirely your choice.
- Your plugins. Page builders (Elementor, Divi), review and pop-up plugins, sliders, and cookie banners each inject their own markup. One plugin can introduce keyboard traps or unlabelled controls across every page.
- Your content. Every product image, every custom colour, every “buy now” link you publish in the admin is a place accessibility is won or lost.
The accessibility issues that most often fail on WooCommerce stores
These are the WCAG 2.1/2.2 AA checks that most commonly flag on WordPress e-commerce storefronts — and exactly what an automated scan (including Curbcut's) looks for:
| Issue | Where it shows up on a WooCommerce store | Who fixes it |
|---|---|---|
| Images missing alt text | Product gallery images, category banners, media-library uploads, logos | You (in the admin) |
| Text fails colour contrast | Sale badges, “add to cart” buttons, page-builder text over images, muted prices | You (theme colours) or developer |
| Links with no readable name | Cart and account icons, “read more” links, social icons in the footer | Developer (theme) |
| Buttons with no accessible name | Quantity steppers, slider arrows, menu toggles, plugin widgets | Developer (theme or plugin) |
| Form inputs missing labels | Search, coupon field, checkout and billing fields, newsletter signups | Developer (theme or plugin) |
| Tap targets too small | Variation swatches, pop-up close buttons, pagination, footer links on mobile | Developer (theme) |
None of these are exotic. They are ordinary consequences of building a real store with a theme and a few plugins — and every one of them is something a screen-reader or keyboard user hits on the way to buying from you.
Why it matters now: the EAA and ADA reality
The European Accessibility Act has been enforceable since 28 June 2025, and consumer e-commerce is squarely in scope. If you sell to EU consumers and aren't a microenterprise (fewer than 10 staff and under €2M turnover), your store is expected to meet WCAG-level accessibility. In the US, thousands of ADA website-accessibility lawsuits are filed each year, and online retail is the most targeted sector. This isn't about a perfect score — it's about not being the store that quietly turns paying customers away and shows up on a demand letter.
How to check your WooCommerce store
You don't have to guess. An automated scan catches the mechanical failures above in under a minute, and it's the right first step before you spend a developer's time:
- Scan it. Paste your store URL into a WCAG scanner. Curbcut checks against WCAG 2.1/2.2 AA and returns each issue in plain English, with a screenshot showing exactly where it is on your page.
- Split the list. Fix the content issues yourself in the admin (alt text, some colours); hand the theme/plugin issues to whoever maintains your site.
- Keep a record. A report and a remediation history is the evidence that actually holds up — far more than any badge in your footer.
- Re-scan on a schedule. WordPress core, themes, and plugins all update; monitoring catches regressions before a customer or a regulator does.
See where your WooCommerce store stands right now — free, no account, no card. Curbcut scans it against WCAG 2.1/2.2 AA and hands you a plain-English fix list. No overlay, ever.
Run a free scan →
FAQ
- Is WooCommerce accessible by default?
- It depends on more than WooCommerce. WooCommerce is a WordPress plugin, so your store’s accessibility is decided by your WordPress theme, the other plugins you run, and the content you publish — product images, colours, page builders. Two WooCommerce stores can score very differently.
- Does the European Accessibility Act apply to my WooCommerce store?
- If you sell to consumers in the EU and are not a microenterprise (fewer than 10 staff and under €2M turnover), the EAA has applied since 28 June 2025. It expects your store to meet WCAG-level accessibility, and a WooCommerce storefront is squarely the kind of consumer e-commerce service it covers.
- Do accessibility plugins make WooCommerce compliant?
- An accessibility overlay or widget runs on top of unchanged code and does not make your store compliant — the FTC fined a leading overlay vendor $1M in 2025 over that claim. Fixing the real issues in your theme, plugins and content is what counts. Curbcut finds them; it will never sell you an overlay.
- Do I need a developer to fix WooCommerce accessibility issues?
- For some, yes — theme and template changes need someone comfortable in the WordPress/WooCommerce template hierarchy. But many issues are content in the admin: missing alt text on product images, low-contrast colours, unlabelled links. Curbcut explains each issue in plain English and shows where it is, so it’s usually clear which you can fix yourself and which to hand to a developer.
- How do I check my WooCommerce store’s accessibility?
- Run a free scan: paste your store URL and Curbcut checks it against WCAG 2.1/2.2 AA and returns a plain-English list of what’s wrong, where it is (with a screenshot), and how to fix it. No account, no card.
Sources: Directive (EU) 2019/882 (European Accessibility Act); FTC final order requiring accessiBe to pay $1M (April 2025); WCAG 2.1/2.2 AA success criteria (W3C).
See the data: we scanned 41 online stores — 93% failed accessibility