What the German BFSG requires from online stores, what the Shopware standard covers for accessibility, and where themes, extensions and content need work.
Germany’s Accessibility Strengthening Act (Barrierefreiheitsstärkungsgesetz, BFSG) has applied to online stores since June 28, 2025. If you sell to consumers in Germany and you are not a microenterprise, your store has to be usable by people with disabilities without particular difficulty and, as a rule, without outside help. The regulation that accompanies the act requires websites to be perceivable, operable, understandable and robust.
Shopware covers a lot out of the box, but not everything. Shopware states WCAG 2.1 at level AA as the goal for its Storefront. The improvements arrived step by step from Shopware 6.6 and have been active by default since Shopware 6.7. That applies to the standard Storefront. It does not automatically apply to your theme, your extensions and your content.
Most of the work is in the theme, the extensions and the content. Low-contrast colors, overridden templates, images without alternative text and unstructured PDFs make an accessible standard inaccessible again. Test the path from product to order first, with a keyboard and a screen reader. If you would rather not run the store yourself, the solution25 shop subscription covers build and operation for a fixed monthly price. Accessibility still has to be tested and maintained there as well.
This article is for managing directors, ecommerce leads and store owners who sell to consumers with Shopware 6. It explains the duties under German law, the state of the Shopware standard and a sensible order of work. It describes German law and is not legal advice. Whether and how the act applies to your company is a question for a lawyer.
The Barrierefreiheitsstärkungsgesetz transposes Directive (EU) 2019/882 into German law. The directive is also known as the European Accessibility Act (EAA). For the first time it obliges private companies to offer certain products and services in an accessible way. Every EU member state has its own national implementation. This article uses the German one as its reference.
One point matters for stores: the act applies to services provided to consumers after June 28, 2025. These explicitly include “ecommerce services”. The act defines them as services provided through websites and mobile applications, electronically and at the individual request of a consumer, with a view to concluding a consumer contract. An online store where consumers can place orders falls under that definition.
Under section 3(1) BFSG, products and services are accessible if people with disabilities can find, access and use them in the generally customary way, without particular difficulty and, as a rule, without outside help. The details are set out in the regulation on the act (BFSGV).
Section 1(4) BFSG exempts certain website and app content. This includes time-based media and office file formats published before June 28, 2025, third-party content, and archives whose content is not changed after that date. An old product video or an old PDF manual does not necessarily have to be reworked. Everything you publish or change now falls under the requirements.
The act affects companies that run a store for consumers. Under the act, a consumer is any natural person who acts mainly for purposes outside their trade or self-employed profession.
Under section 3(3) BFSG, the requirements do not apply to microenterprises that offer or provide services. The act defines a microenterprise as a company with fewer than ten employees and either annual revenue of no more than 2 million euros or an annual balance sheet total of no more than 2 million euros. Both conditions have to be met together. A store with twelve employees is not a microenterprise, even if revenue is below 2 million euros.
The exemption covers services. A company that itself places products on the market that fall under the act, such as e-book readers, cannot rely on it. That concerns very few store owners, but it is worth checking.
The act regulates offers for consumers. Germany’s Federal Accessibility Agency (Bundesfachstelle Barrierefreiheit) writes in its FAQ on the BFSG that services offered exclusively in B2B are not affected. The key word is “exclusively”. If a private person can also order in your store, assume the act applies and have that checked by a lawyer.
Sections 16 and 17 BFSG contain two further exemptions: if the requirements would fundamentally change the offer, or if they would lead to a disproportionate burden. The company assesses both itself. The assessment has to be documented, kept and reported to the market surveillance authority. This is not a free pass. For an ordinary store with standard functions, the argument will be hard to make.
For retailers in the United States: The BFSG and the European Accessibility Act are European rules. They do not govern sales within the United States. They become relevant when you sell to consumers in the EU, for example with a German-language storefront. US accessibility law is a separate topic that this article does not cover. Two practical notes: most Shopware partners are based in Europe, so meetings usually take place in the morning Eastern time. Sales tax is normally calculated through a tax service integration. Test that part of the checkout with the keyboard as well. Euro amounts in this article remain in euros.
The German federal states have founded a joint authority for enforcement: the Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF), based in Magdeburg. According to the Federal Accessibility Agency, it started work when the state treaty came into force on September 26, 2025.
Section 12 of the BFSGV requires websites, including the related online applications and mobile apps, to be perceivable, operable, understandable and robust. Section 19 BFSGV adds for ecommerce: identification, authentication, security and payment functions have to meet the same four requirements. The store also has to provide information on the accessibility of the products it sells, as far as the manufacturer or another responsible economic operator supplies it.
The four terms come from the Web Content Accessibility Guidelines (WCAG) of the W3C. The table below translates them into typical places in a store. Criteria and thresholds are taken from WCAG 2.2.
| Principle | Meaning | Examples in a store |
|---|---|---|
| Perceivable | Information and user interface components must be presentable to users in ways they can perceive. | Alternative text for product images (1.1.1). Text contrast of at least 4.5:1, and 3:1 for large text (1.4.3). Contrast of 3:1 for interface components such as input field borders (1.4.11). Text can be resized to 200 percent without loss of content (1.4.4). |
| Operable | User interface components and navigation must be operable. | All functionality works with a keyboard (2.1.1). The keyboard focus is visible (2.4.7). Click targets are at least 24 by 24 CSS pixels (2.5.8, new in WCAG 2.2). Time limits in the checkout can be turned off or extended (2.2.1). |
| Understandable | Information and the operation of the user interface must be understandable. | Every form field has a label (3.3.2). Errors are detected and described in text (3.3.1). If a correction is known, it is suggested (3.3.3). Before an order is submitted, the customer can review and correct the input (3.3.4). The language of the page is set in the code (3.1.1). |
| Robust | Content must be interpreted reliably by browsers and assistive technologies. | Buttons, toggles and select fields have a name and a role that a screen reader can identify (4.1.2). Status messages such as “Item added to cart” are announced without moving the focus (4.1.3). |
Almost all criteria meet in the checkout: forms, error messages, login, payment. Three points often fail in practice.
Accessible forms help every customer. The points overlap strongly with what we describe for the checkout in our article on conversion optimization for online stores.
Neither the act nor the regulation names a technical standard. Section 3 BFSGV requires companies to observe the state of the art and refers to a list of the most important standards published by the Federal Accessibility Agency.
For websites and apps, the agency names the European standard EN 301 549 as the current central technical reference. Section 9 of the standard describes the requirements for websites. Version V3.2.1 from 2021 refers to the success criteria of WCAG 2.1. A revised version is in progress and, according to the agency, will refer to WCAG 2.2.
Under sections 4 and 5 BFSG, an offer is presumed to meet the requirements if it complies with harmonized standards whose references have been published in the Official Journal of the European Union. When we checked in November 2026, the agency did not yet list a published harmonized standard for this area. Until then, EN 301 549 and WCAG are the practical guide. You may reach accessibility in another way, but then you have to prove conformity yourself.
WCAG 2.2 has been a W3C Recommendation in its current version since December 12, 2024. New compared with 2.1 are, among others, criteria on the minimum size of click targets, on focus that is not obscured, on accessible authentication and on avoiding redundant entry. Criterion 4.1.1 was removed. Our recommendation: treat WCAG 2.1 level AA as the mandatory program and include the new AA criteria from 2.2 right away. The extra effort is small, and you will not have to start again once the standard is revised.
Shopware writes in its developer documentation that the Storefront is meant to fulfill the WCAG 2.1 guidelines at level AA. The improvements did not come in one big release but across several versions.
From Shopware 6.6, improvements shipped in the regular minor versions. Changes that could break existing themes or extensions sat behind the feature flag ACCESSIBILITY_TWEAKS and were not active by default. Anyone who wanted them had to set the flag and recompile the theme. Examples from the documentation:
According to Shopware, version 6.7.0.0 was released in June 2025. Since this version the improvements have been active by default. Shopware mentions optimized templates, adjusted font sizes and semantic HTML. According to the documentation, there is no accessibility support for Shopware 5.
Shopware also offers the standard documents invoice, delivery note, credit note and cancellation invoice as HTML, because the generated PDF files do not meet accessibility standards. Customers can retrieve the HTML version in their account. Generation is switched on in the document settings.
If your store still runs on 6.5 or an early 6.6, the update is the first step. Our article on Shopware updates and versions explains what to watch out for. A current standard is the foundation, not proof. When we checked, the table in the developer documentation itself still listed open items, such as text alternatives for icons and suggestions for error correction. Shopware tests the core automatically. That does not amount to a promise that your specific store is compliant.
The standard Storefront is only part of what your customers see. Three layers sit on top of it, and each of them can make an accessible standard inaccessible again.
A theme overrides templates and colors. Shopware describes the risk in its documentation with an example: a list in the standard was changed from div elements to a real list with ul and li. If a theme overrides only the old block, the result is broken HTML. Older themes built before these changes often carry such spots.
Every extension that displays something in the Storefront brings its own HTML: filters, product configurators, wish lists, pop-ups, reviews, chat. According to Shopware, developers can label their extension as accessible themselves. Do not rely on that alone. Test the extension in your store.
The consent banner is a topic of its own. It is the first element a visitor has to operate. If it cannot be closed with the keyboard, a keyboard user never reaches the store. Our article on Cookiebot in Shopware describes how to integrate a banner properly. The same goes for mandatory elements such as the withdrawal button required under German law: it has to be reachable by keyboard and carry a name that a screen reader announces.
In daily work, content accounts for the largest share, because it is created every day and nobody checks it technically.
Clean headings, meaningful link text and alternative text also help search. The overlap with search engine optimization for online stores is large.
A test has two parts. Automated tools quickly find the technical errors. Manual testing shows whether a person can actually complete the purchase.
In its documentation, Shopware names Lighthouse, axe DevTools and WAVE as well as the accessibility features of Chrome DevTools. The Federal Accessibility Agency names, among others, the ARC Toolkit, HeadingsMap and the Colour Contrast Analyser. These tools reliably find missing alternative text, missing field labels, insufficient contrast of text on a plain background, duplicate IDs and missing language attributes.
What they do not find:
A result without errors in the automated test therefore does not mean that the store is accessible.
Put the mouse away. Use Tab, Shift and Tab, Enter and the space bar to go through this path: home page, navigation, search, category with filter, product page with variant selection, cart, login or guest order, address, shipping, payment, order overview. Check whether you can always see where the focus is, whether you can reach every element and whether you can get out of every dialog again.
Shopware names NVDA for Windows and VoiceOver for macOS. Both are available free of charge. Test the same path: are headings, buttons and fields announced in a meaningful way? Do you hear when an item lands in the cart? Is an error message in the checkout read out?
Zoom the page to 200 percent in the browser and check whether content is cut off. WCAG requires content to be usable at a width of 320 CSS pixels without scrolling in two directions (1.4.10).
Record the results in a list: page, element, problem, affected criterion, cause (standard, theme, extension, content). The last column decides who fixes the error.
Under section 14 BFSG, a service may only be offered if it meets the requirements and the provider has prepared the information listed in Annex 3 and made it available in an accessible way. In practice this page is usually called the accessibility statement (Erklärung zur Barrierefreiheit).
Annex 3 requires the information to be given in the general terms and conditions or in another clearly perceivable way. At a minimum it has to contain:
The information has to be kept for as long as the service is offered. In Shopware you create a shop page for it and link it in the footer next to the legal notice and the privacy policy. Our article on data protection in online stores explains how the other legal texts belong in the store.
Write the statement honestly. State when the store was tested, the known limitations and a contact through which customers can report barriers. A statement that claims full conformity while the checkout cannot be operated with the keyboard helps nobody. Have the text reviewed by a lawyer.
Overlay tools are scripts that are placed on top of the finished page. They usually show a menu that lets visitors change font size, contrast or spacing. Some promise to fix errors in the code automatically.
The Federal Accessibility Agency advises against relying on them. In its assessment, overlays cannot make a website fully accessible and do not fulfill the duties under the BFSG. They often create additional barriers.
The reason is technical. A script cannot know what a product image shows, which heading should have which rank or what an error message in the checkout means. People who use a screen reader or screen magnifier already have their own settings in the operating system. An overlay can be a convenience for some visitors. It does not replace the work on theme, extensions and content.
Accessibility is not a one-time project. Section 14(3) BFSG requires the requirements to be met at all times. Every new Shopping Experience and every new extension can introduce an error. A fixed order with an ongoing part at the end makes sense.
Most new errors arise in daily maintenance. Whoever creates products and builds Shopping Experiences has to know what a good alternative text looks like, why text does not belong in the image and how headings are ordered. This can be taught in a few hours, for example as part of a Shopware training.
The following figures are assumptions for an imagined store. They are not an offer and not an empirical value from a specific project. The effort depends on the theme, the number of extensions and the volume of content.
| Step | Assumed effort |
|---|---|
| Test of the purchase path with report | 2 days |
| Corrections to the theme | 5 days |
| Testing and adjusting 10 extensions | 3 days |
| Statement, briefing of the editors, retest | 2 days |
| Total | 12 days |
At an assumed day rate of 1,000 euros net, that would come to 12,000 euros. Work on the content is not included. Assume an alternative text takes one minute and the store has 3,000 product images: that is 50 hours for your own editors. With an individually developed theme and many extensions the effort can be much higher, with a current standard theme much lower.
If you are starting fresh anyway, you save the rework on an old theme. With the solution25 shop subscription, our team builds and runs the store. The Scale package costs 299 euros per month, the Pro package 499 euros per month, and Enterprise is available on request. The minimum term is 24 months in each case, and there is no setup fee. According to the offer page, Scale and Pro are meant for stores with up to 1 million euros in annual revenue. Important for this topic: the offer page does not promise BFSG conformity. A new store on a current version is a good starting point. Testing the purchase path, maintaining the content and writing the statement remain tasks that you should agree on with us explicitly.
No. Shopware 6.7 ships a Storefront in which the accessibility improvements are active by default. Whether your store meets the requirements also depends on the theme, extensions, payment methods and content. Only a test can establish that.
Not if you are a microenterprise: fewer than ten employees and no more than 2 million euros in annual revenue or no more than 2 million euros in annual balance sheet total. If you are above that and sell to consumers in Germany, the act applies. If in doubt, have the classification checked by a lawyer.
The act does not name a WCAG version. The Federal Accessibility Agency names EN 301 549 as the central technical reference. Its current version refers to WCAG 2.1, and the revised version is expected to refer to WCAG 2.2. If you work to WCAG 2.1 AA and take the new AA criteria from 2.2 into account, you are prepared for both cases.
Not according to the Federal Accessibility Agency. Overlays cannot make a website fully accessible and do not fulfill the duties under the BFSG. The errors have to be fixed in the theme, in the extensions and in the content.
The market surveillance authority can check the store, also at the request of consumers or associations. It first asks for correction. If that has no effect, it can order the offer to be discontinued. Section 37 BFSG provides for fines of up to 100,000 euros for offering a non-compliant service.
solution25 is a Shopware Platinum Partner from Bremen, Germany, and has worked with Shopware since 2017. We test your purchase path with tools, keyboard and screen reader, sort the errors by cause and fix what lies in the theme and the extensions. We brief your editors on maintaining the content.
What we do not do: we do not give legal advice and we do not issue a certificate that your store is legally compliant. We deliver a traceable test report and clean technology. The legal assessment and the text of the statement belong in the hands of your legal counsel.

Besar Bilalli is co-founder and Co-CEO of solution25, the Shopware agency based in Bremen. Before founding the agency in 2017, he and Besnik Bilalli built their own online store without any startup capital and grew it to more than 500 orders a day. Since then, he has guided merchants through Shopware projects, from platform selection to day-to-day operations. He’s happy to answer questions about this article personally: get in touch.
Responsible for content and updates: Besar Bilalli. Last updated: November 2026. Next content review: February 2027.