WooCommerce accessibility and the European Accessibility Act

EAA Comply · Updated 27 July 2026 · 7 min read

WooCommerce is more honest about accessibility than most platforms, and that honesty is exactly why a WooCommerce store needs auditing. Its own documentation tells you where its responsibility ends: your theme can override what WooCommerce sets, and third-party plugins that modify the checkout can break accessibility outright.

On a WordPress site you are running a theme, a page builder, WooCommerce, and usually fifteen to forty other plugins. Every one of them can put markup on your storefront. That is the audit problem in one sentence.

What WooCommerce gives you out of the box

Credit where it is due. WooCommerce states that its default configuration is designed to meet WCAG Level AA colour contrast and usability requirements, and it documents specific work on logical tab order through cart, checkout and forms, visible focus indicators, semantic HTML with ARIA roles, labelled inputs, errors announced close to the relevant field and linked programmatically, zoom to 400 %, and respect for reduced-motion preferences.

If you ran stock WooCommerce on a stock accessibility-ready theme with no other plugins, you would be in a decent position. Almost nobody does.

The barriers we find most often on WooCommerce stores

1. The theme overrides what WooCommerce got right

WooCommerce ships visible focus indicators. A theme that sets outline:none on links and buttons deletes them across the entire site, including checkout. This one line is probably the most common single cause of a keyboard-inaccessible WooCommerce store, and it is usually inherited from the theme rather than written by anyone at your company.

2. Page-builder markup that is not really markup

Elementor, WPBakery, Divi and similar builders can produce excellent output or terrible output depending on how they were used. What we see repeatedly: headings chosen for size rather than structure, so a page has four h1s and no h2; accordions and tabs built from divs with click handlers and no keyboard support; and icon-only buttons with no accessible name.

3. Checkout modified by a plugin

WooCommerce warns about this in its own docs, and it is accurate. Multi-step checkout plugins, one-page checkout, custom field managers, address autocomplete and payment gateway add-ons all rewrite the part of your store where a failure costs a sale outright. Whether you use the classic shortcode checkout or the newer checkout blocks, what matters is what the plugins left behind.

4. Product galleries and variation dropdowns

The default WooCommerce gallery uses a lightbox and zoom that depend on how the theme wires them up. Variation selects that reveal or hide content need the relationship announced, and swatch plugins that replace the native select with styled divs frequently remove keyboard access entirely, which means the product cannot be bought without a mouse.

5. Contact and review forms

Form plugins are their own category of risk: placeholder text used instead of a real label, error summaries that appear visually but are never announced, required fields marked only with a red asterisk, and CAPTCHAs with no accessible alternative. A CAPTCHA that cannot be completed is a total block, not an inconvenience.

6. Content added over the years

Images uploaded without alt text, PDF catalogues and size guides that were never made accessible, embedded videos without captions, and link text that reads “click here” twelve times on the same page. Content is usually the largest count of findings and the cheapest to fix, because most of it needs an editor rather than a developer.

The WordPress advantage nobody uses

Unlike a hosted platform, you own every line of your site. Nothing is locked away. A WooCommerce fix is almost always a change you or your developer can actually make: a child-theme stylesheet, a template override, a plugin setting, a swap to a better-maintained alternative.

That is why WooCommerce stores usually have the best fix-to-cost ratio of anything we audit. The findings are real, and the remedies are within reach rather than stuck behind a vendor roadmap.

Five things you can fix yourself this week

• Search your theme CSS for outline:none or outline:0 and remove it, or replace it with a visible custom focus style. This is the highest-value single change on most WooCommerce sites.
• Tab through checkout with no mouse. Every field reachable, every label read, every error findable. If you get stuck, so does your customer.
• Fix your heading order on the templates that matter: one h1 per page, no level skipped for visual reasons.
• Add alt text to product images in the media library, starting with your best sellers.
• Audit your plugin list. Anything inactive, abandoned or duplicated should go. Fewer plugins on the storefront means fewer sources of markup you cannot control.

What an audit looks like on a WooCommerce store

We test your real pages — home, a shop archive, a variable product, cart and the full checkout — on desktop and mobile, with axe-core plus a manual pass by a person. Every finding comes with the exact element and, where we can identify it, the theme template or plugin responsible, so your developer is not guessing. Ordered by what blocks a purchase first. Your accessibility statement, written against WCAG 2.1 AA, comes with it and is ready to publish. That is the €149 report; the fixes written out as code your developer can apply are €290.

Questions we get asked

Does using WooCommerce make my store EAA compliant?

No, and WooCommerce does not claim it does. The plugin ships accessible defaults for the parts it controls — contrast, tab order, focus visibility, labelled inputs, error messages linked to their fields. Your theme can override every one of those with a few lines of CSS, your page builder generates its own markup, and any plugin that touches the cart or checkout can undo the rest. Compliance is a property of the page a customer actually receives, not of the plugin that generated part of it.

Will an accessibility plugin fix this?

Not the overlay kind. A plugin that injects a toolbar into your site does not change the underlying HTML your theme and page builder produced, which is what a screen reader and a keyboard user are working with. In April 2025 the US Federal Trade Commission finalised a $1 million order against the largest overlay vendor over the claim that its product could make any website compliant. Plugins that help you author better markup — heading checkers, caption tools, skip links — are a different thing and genuinely useful.

Do you audit the checkout?

Yes, and on WooCommerce it is usually the most valuable page in the audit. We walk the full path — cart, coupon field, shipping selection, payment method, order review, place order — by keyboard and with a screen reader, because that is where a single unlabelled radio or an error message the browser never announces stops a sale. If you use the newer checkout blocks rather than the classic shortcode, we test whichever one your store actually serves.

How long does a WooCommerce audit take?

Five to seven working days from the moment we have the URL. That covers your home page, shop archive, a variable product, cart and the full checkout, plus whatever other templates matter on your store. You get the report with each barrier, the element and selector involved, and — where we can identify it — the theme template or plugin responsible, so your developer is not hunting for the source.

My store is small. Does the EAA actually apply to me?

Possibly not. The Directive exempts microenterprises providing services — fewer than 10 staff and under €2 million annual turnover — but the test is narrower than most people assume and each member state applies it through its own transposition. It is also no shield against a German competitor warning letter, or against a larger B2B buyer asking for your accessibility statement. If you are clearly exempt we will tell you so rather than sell you an audit you do not need.

• WooCommerce, accessibility features in WooCommerce (vendor documentation) — woocommerce.com
• Directive (EU) 2019/882 (European Accessibility Act) — eur-lex.europa.eu
• FTC, final order requiring accessiBe to pay $1 million, 22 April 2025 — ftc.gov
• W3C, Web Content Accessibility Guidelines (WCAG) 2.1 — w3.org