WooCommerce Accessibility: Your Online Shop and the EAA
Information about the article

Author: Dmitry Dugarev
Do you run a WooCommerce shop that sells to consumers in Germany? Then WooCommerce accessibility is a legal requirement for you, unless you are a microenterprise. Most guides stop at the law. I audit shops by hand. In this guide, I walk you through the whole purchase path of an accessible online shop, from the search box to the invoice.
- Under the BFSG, Germany's implementation of the European Accessibility Act (EAA), an online shop for consumers is a "service in electronic commerce" [1].
- Payment and login have extra requirements under § 19 BFSGV [2].
- WooCommerce itself is a good foundation. But your theme and plugins can break accessibility again [3].
- Test the whole purchase path with a keyboard and a screen reader, not just the homepage.
Does the EAA apply to your online shop?
The European Accessibility Act (EAA) is the EU law. Germany implements it through the Barrierefreiheitsstärkungsgesetz (BFSG). The BFSG has applied since June 28, 2025 [1]. § 1 Para. 3 No. 5 BFSG lists "services in electronic commerce" [1]. § 2 No. 26 BFSG defines them. They are services on websites and in apps that a consumer uses with a view to a consumer contract [1]. A WooCommerce shop with a cart and a checkout is exactly that. This also applies if the products you sell are not covered by the BFSG themselves [4].
§ 3 Para. 1 BFSG requires these services to be accessible [1]. The rule does not apply to microenterprises that provide services (§ 3 Para. 3 BFSG) [1]. A microenterprise has fewer than 10 employees. In addition, its annual turnover or balance sheet total is €2 million or less (§ 2 No. 17 BFSG) [1]. The article on microenterprises under the BFSG has the details. The article Who must make their website accessible, and by when? explains exactly when the obligation applies and from what date.
What about B2B shops?
The BFSG protects consumers. A consumer buys mainly for private purposes (§ 2 No. 16 BFSG) [1]. So a pure B2B shop is usually not covered by the law. But as soon as a visitor lands on it, it must show clearly that it sells only to businesses [5]. If you sell to both businesses and consumers, the BFSG applies. The BFSG relevance check helps you find out whether the law affects you.
Extra requirements for online shops
The ordinance to the BFSG (BFSGV) has its own rules for electronic commerce in § 19 [2]:
- You pass on accessibility information about your products if the responsible economic operator supplies it, for example the manufacturer.
- Identification, authentication, security and payment functions must be perceivable, operable, understandable and robust.
- The same applies to identification and authentication methods, electronic signatures and payment services.
You also need an accessibility statement (Barrierefreiheitserklärung). § 14 Para. 1 BFSG requires the information listed in Annex 3 in an accessible format [1]. You can start from our accessibility statement template.
Violations can lead to fines of up to €100,000 (§ 37 Para. 2 BFSG) [1]. The article on risks and fines explains more. The article on the official inspection process describes how an authority proceeds.
E-commerce accessibility in practice: how do shops perform?
In 2025, the German charity Aktion Mensch and Google commissioned a test of online shops for the third time [6]. The testers checked 65 shops among the 500 most visited websites in Germany [6]. Only 20 of them could be used entirely with a keyboard [6]. The testers were people with disabilities who use a screen reader or eye control [7].
The report lists typical barriers [6], [7]:
- no visible keyboard focus
- low color contrast
- an illogical tab order
- banners and cookie overlays that cover the content
- form fields without labels
I see the same issues in my audits of WooCommerce shops. They rarely come from the WooCommerce core. Most of them come from the theme, the page builder or add-on plugins.
WooCommerce accessibility: the purchase path up to the cart
A customer goes through many steps. If they get stuck at any step, they cannot buy. That is why I test a shop along this path.
Open text description for "Flowchart: The purchase path in a WooCommerce shop"
The flowchart shows eight steps in this order:
- "Navigation and search"
- "Category with product filters"
- "Product page: images and variants"
- "Add to cart: notice and mini cart"
- "Cart and checkout" (marked red as a critical step)
- "Payment via the payment provider" (marked red as a critical step)
- "Order confirmation, email and PDF invoice"
- "Customer account"
A separate box "Cookie banner and CAPTCHA" (marked yellow as a possible blocker) points to step 1 and step 5 with dashed arrows. These elements can block the path at either point.
Let's go through the first four steps one by one. Checkout, payment and the steps after the purchase follow later.
Navigation and product search
Every function must work with a keyboard [8]. This includes your theme's mega menu. The tab order must preserve the meaning of the page [9].
The search needs a visible label. A "Search" button right next to the field can serve as that label [10], [11]. After a search, the screen reader should announce the number of results. The W3C gives "5 results returned" as an example of a status message [12]. Our pattern for accessible search shows how a search with suggestions works.
Product filters
Filters for size, price or color often update the product list without a page reload. A blind customer only notices this if the shop announces the change [13]. Changing a filter must not cause an unexpected change of context [14]. If the focus jumps to the top of the page after a click, that is a failure.
WooCommerce says it has added consistent ARIA roles to its filters. Keyboard support in the "Product Filters" block has also improved [15]. But many shops use third-party filter plugins. Test those separately.
Product images and alt text
Every product image needs a text alternative, called alt text [16]. The alt text describes what the customer should see: color, material, details. The product name alone is rarely enough.
Videos in the gallery need text as well. WooCommerce recommends giving the video's thumbnail alt text. Otherwise, WooCommerce uses the video title [17]. The article on alt text for images explains how to write good alt text.
Variants: dropdowns and color swatches
Variable products have selectors for size or color. The "Add to Cart + Options" block (still in beta) shows variants as a dropdown or as "pills" [18]. With an experimental feature, the pills can also show color swatches [18].
For swatches, I check three things:
- Does every swatch have a name that the screen reader reads out [19]?
- Can you tell the selected swatch by more than its color [20]?
- Does the swatch border have a contrast of at least 3:1 [21]?
Third-party swatch plugins often replace the native select field. When they do, my audits often find the name and the state missing.
"Add to cart": the notice for screen readers
After a click on "Add to cart", the customer needs to know that it worked. The focus should not jump. The W3C uses exactly this case as an example of a status message [12].
For the classic AJAX buttons, for example in product lists, WooCommerce creates a live region with role="status" [22]. It only announces something if the button carries a success message [22]. A comment in the code also notes that some themes and plugins trigger the event without a button [22]. The live region then stays empty.
Here is how to check this on a product list with your browser console. Reload the page first so that no old message is left over.
// Run 2 seconds after clicking "Add to cart" in a product list
document.querySelector('.widget_shopping_cart_live_region')?.textContent;
// Empty text or undefined: the screen reader announces nothing.
This test only works for these AJAX buttons. The script does not handle any other buttons [22]. On the product page and with blocks, use a screen reader to check whether it reads out the success message.
Mini cart
The mini cart opens as a side panel. The focus must move into it and return when it closes [9]. WooCommerce improved the "Mini-Cart" block in version 9.2 [23]. Its footer is no longer sticky when the viewport is less than 500 pixels high. So it no longer covers items at high zoom levels [23].
Cart and checkout: blocks or classic shortcode?
In the checkout, the customer enters their address and pays. If they get stuck here, you lose the sale. WooCommerce offers two options: the "Cart" and "Checkout" blocks and the classic shortcodes.
Since version 8.3 (November 2023), the blocks have been the default for new shops [24]. WooCommerce says the blocks were built with accessibility in mind [3]. With version 10.0, WooCommerce announced that the shop would fully meet WCAG 2.2 AA [25]. This is the vendor's own claim. It only holds with a default WordPress theme or an "accessibility-ready" theme [25].
WooCommerce itself warns: themes and plugins that change the checkout can break accessibility [3]. An example from version 9.1: with dark themes, fields in the Checkout block looked as if their labels were missing [26]. As a quick fix, WooCommerce recommended the "Dark Mode Inputs" setting in the block. WooCommerce then reverted the change [26].
If you switch to the classic shortcode, test the cart and the checkout again. WooCommerce recommends switching both at the same time [24].
What I test in the checkout
- Labels: Every field has a visible label [10].
- Errors: The shop describes every error in text [27]. The screen reader reads it out at the field.
- Order review: Before buying, the customer sees their details and can change them [28].
- Time limits: If the session is about to expire, the shop warns the customer first. The customer can then extend the time [29].
- Autocomplete: Fields for name, address and email have a matching
autocompleteattribute [30]. - No repeated entry: A checkbox such as "Use same address for billing" is a good example. The W3C names exactly this case [31], [32].
- Shipping methods: The focus stays on the shipping method while the shop recalculates the price. WooCommerce fixed this bug in version 9.2 [23].
Our pattern for accessible forms covers fields, errors and groups in more detail.
Payment, cookie banner and CAPTCHA
Check your payment provider
§ 19 BFSGV requires accessible payment services [2]. But the fields for cards or wallets usually come from the payment provider. You cannot change their code yourself.
WooCommerce publishes conformance reports for its own payment extensions. The report on "Stripe for WooCommerce" from July 2026 lists several criteria as only partially supported [33]. They include keyboard access, focus order and status messages. According to the report, these gaps affect the Stripe Link feature [33].
Stripe, not WooCommerce, controls many parts of the extension. If Link is turned off in Stripe, the report counts these criteria as supported [33]. The WooPayments report from August 2026 also lists gaps, for example in contrast [34].
This is no reason to drop these providers. It does show one thing, though: ask your payment provider for its conformance report.
Describe in your accessibility statement how payment works. Check with a lawyer how to present known gaps there. Offer at least one payment method that you have tested yourself with a keyboard and a screen reader. If you change your Stripe Link settings, test the payment again afterwards.
Cookie banner
A cookie banner appears before the first click. If you cannot close it with a keyboard, it blocks the whole shop. The Aktion Mensch test names cookie overlays as a typical barrier [6]. Also make sure a banner does not completely hide the focus [35]. The article on WordPress accessibility plugins shows how cookie plugins perform in a hands-on test.
CAPTCHA
Many shops protect the checkout, the login and the contact form with a CAPTCHA. A CAPTCHA needs a text description and an alternative that uses a different sense, for example hearing instead of seeing [36]. For the login, another rule applies: no puzzles, no memorizing and no transcribing without an alternative or help [37]. Recognizing objects is allowed at level AA [37]. The shop must not block pasting from a password manager [37]. For form plugins, also read the guide to Contact Form 7.
After the purchase: email, PDF invoice and customer account
The purchase path does not end with the "Place order" button. The order confirmation page needs a clear heading [38]. The email needs headings and enough contrast [39]. The logo needs alt text [16].
In my audits, PDF invoices from plugins are often untagged. A screen reader then reads only a block of text without structure. The W3C describes techniques for tagged PDFs, for example heading tags [40] and table tags [41]. The line items of an invoice form a table. So they need real table tags [41].
In the customer account, I test the login, the addresses and the orders. WooCommerce says it has added labels in the checkout, the login and account management [15]. The "Edit billing address" and "Add shipping address" buttons now also give screen readers their context [23].
Shopify and Shopware: same rules, different technology
The BFSG does not care which shop system you use. The rules apply to every shop that sells to consumers [1]. So the purchase path above applies to Shopify and Shopware too.
- Shopify accessibility: Themes in the Theme Store need an average score of at least 90 in the Lighthouse accessibility test [42]. This is an automated test. It does not replace a manual audit.
- Shopware accessibility: Shopware aims to meet WCAG 2.1 AA and BITV 2.0 (the German accessibility standard for public-sector websites) in its storefront [43]. Since version 6.7, the improvements have been on by default [43].
In both systems, just like in WooCommerce, barriers come from the theme, apps and plugins.
How to test your online shop
Start with the free BFSG check. It automatically tests 20 of the 55 WCAG 2.2 A and AA criteria, at least in part. The other 35 criteria can only be tested manually. The check covers exactly one page. Enter a product page, for example. The cart and the checkout need a session with items in it. The check cannot reach these pages. A tool also cannot tell whether the live region announces anything after "Add to cart".
For a smaller shop, the Basis-Audit for €490 plus VAT is a good fit. It covers your homepage and 4 subpages. I choose the pages along the purchase path based on Annex 1 BFSG, for example a product page, the cart and the checkout. I test all 55 criteria by hand with a keyboard and a screen reader.
Do you want me to test every step of the purchase path, including search, filters and the customer account? Then choose the BFSG-Prüfung, the audit of your entire shop, for €1,490 plus VAT. Not sure which package fits? Book a free 15-minute call.
If you want, I can fix the issues in your existing theme, without a relaunch. The page on remediation explains how. For an overview of WordPress, read the guide to WordPress accessibility.
Frequently asked questions (FAQ)
Does my online shop have to be accessible under the EAA?
Yes, if you sell to consumers and you are not a microenterprise. The BFSG covers services in electronic commerce (§ 1 Para. 3 No. 5 BFSG) [1]. Microenterprises with fewer than 10 employees and a turnover or balance sheet total of €2 million or less are exempt [1].
Is WooCommerce accessible?
The core is a good foundation. For version 10.0, WooCommerce claims full conformance with WCAG 2.2 AA [25]. This only holds with a default theme or an "accessibility-ready" theme [25]. You have to test your theme and your plugins yourself [3].
Does the BFSG apply to B2B online shops?
Usually not. The law protects consumers [1]. But as soon as a visitor lands on it, the shop must show clearly that it sells only to businesses [5]. If you also sell to consumers, the BFSG applies.
Is an accessibility plugin enough for my online shop?
No. Germany's federal and state monitoring bodies for public-sector accessibility are clear on this. A website is only accessible if it meets the requirements without an overlay tool [44]. This assessment applies to public bodies. For shops, it is a clear sign of how testers view overlays. I explain why in the article on overlays and compliance.
How much does an accessibility audit for an online shop cost?
The Basis-Audit costs €490 plus VAT for your homepage and 4 subpages. The BFSG-Prüfung for your entire shop costs €1,490 plus VAT. After the audit, I offer remediation at a fixed price. The article on the cost of an accessible website gives an overview of all cost items.
Disclaimer
The content of this article has been researched to the best of my knowledge and is for general information only. It is not legal advice and cannot replace individual advice from a lawyer who looks at your specific situation.
The details on WooCommerce, payment providers and shop systems come from the sources cited and are current as of September 2026. They may have changed since.
No guarantee is given for the accuracy, completeness or timeliness of the information. Any action you take based on the information provided here is at your own risk.