
BFSG and Magento: What This Year’s Warning Letters Look For, and How to Fix It
Selling to consumers in Germany from a Magento shop? Then the Barrierefreiheitsstärkungsgesetz (BFSG), Germany’s accessibility law, has applied to you since 28 June 2025. The only way out is being a microenterprise, which means fewer than 10 staff and no more than €2 million in turnover or on the balance sheet.
Last year’s warning letters were mostly about a missing accessibility statement. This year they’re about things that are actually broken. A checkout nobody can finish with a keyboard. A focus outline nobody can see. Error messages that are nothing more than a red border. Your developer can fix most of that in the theme.
Plenty of shop owners don’t get past the cookie banner. Some make it to the mini-cart and then can’t get out again. If you get stuck, so do customers who can’t use a mouse. So do the crawlers some law firms now run to find shops worth writing to.
Below you’ll find who has to comply and what the current letters complain about. After that come the ten faults that show up most in Magento themes, each with a fix your developer can put in place.
Key takeaways
- The BFSG has applied since 28 June 2025 to every Magento shop that sells to consumers, unless you’re a microenterprise.
- The 2026 warning letters come with evidence of real faults: keyboard traps, invisible focus, unlabelled fields and errors shown only in red.
- Overlay widgets don’t fix anything and now draw warning letters of their own.
- Most fixes sit in your theme. Start with an automated scan and a keyboard test on the checkout.
Does the BFSG cover your shop?
The BFSG is a consumer protection law. So start with one question: can a private person buy something from your shop?
Shops that sell to consumers: yes. If a private customer can place an order, the law treats your shop as an e-commerce service. What you sell makes no difference.
Business-only shops: usually not, as long as it’s obvious. The BFSG doesn’t cover shops that only sell to other companies. A note in the footer saying “B2B only” won’t help you much, though. If a private person can still sign up and buy, a court could decide your shop is open to consumers after all. These steps make your position much stronger:
- Ask for a VAT ID or company registration number when people sign up, and check each account before you approve it.
- Show prices and the checkout only to approved customers.
- State plainly, on the homepage and in your terms, that you sell to businesses only.
Very small companies don’t have to comply. If you have fewer than 10 employees and your annual turnover or balance sheet total is €2 million or less, you count as a microenterprise. For services like an online shop, the BFSG doesn’t apply to you. Grow beyond that and it does.
Shops that sell to both. Plenty of Magento stores serve trade buyers and private customers from one storefront. In that case the rules cover the whole public shop, so you can’t limit the work to the pages private customers use.
The law itself doesn’t define “accessible” in detail. In practice, everyone works with the European standard EN 301 549, which refers to WCAG 2.1 at level AA. The testers check against that list, so you should too.
What the 2026 warning letters actually complain about
The first letters came in August 2025, only weeks after the law took effect. Most were pretty vague: your shop doesn’t meet the BFSG, here’s a screenshot, please pay. Retail associations like the Händlerbund said many of them were very likely unjustified. They still told retailers not to ignore them.
This year the letters look different. Legal and agency blogs describe letters that come with proper evidence, such as code excerpts, screenshots and screen-reader logs. Crawlers collect it by clicking through the entire checkout. These complaints come up again and again:
One agency blog says the dispute value runs at €15,000–50,000 per issue, and each fault is counted on its own. That’s the blog’s estimate, not data from the courts. Even so, it explains why this round costs more than the last one.
The authorities have a say as well. BFSG enforcement sits with the Marktüberwachungsstelle der Länder für die Barrierefreiheit (MLBF) in Magdeburg. Before anything else, it has to ask you to fix the problem. Ignore that request and you could face a fine of up to €100,000.
Two mistakes that make things worse:
Overlay widgets
That small accessibility icon promising a one-click fix leaves your HTML exactly as it was. Legal blogs report that these widgets now draw warning letters of their own.
An accessibility statement that lists every barrier
You do need a statement. But a long list of problems you haven’t fixed hands a claimant their to-do list. Do the fixes first, then write down what you changed.
Ten accessibility faults that keep showing up in Magento themes
You’ll find these in Luma-based shops and in older custom themes. The WCAG number in brackets tells your developer which rule to look up.
1. Keyboard focus is invisible (WCAG 2.4.7)
Lots of themes switch the outline off because someone thought it looked ugly. Bring it back, just for keyboard users:
:focus-visible {
outline: 3px solid #1a56db;
outline-offset: 2px;
}2. Form fields have no label (WCAG 1.3.1, 3.3.2)
A placeholder such as “Email address” vanishes the moment someone starts typing, and screen readers don’t count it as a label. Check the newsletter box in the footer and the search field first.
<label for="newsletter-email" class="sr-only">Email address</label>
<input id="newsletter-email" type="email" name="email"
placeholder="Email address" autocomplete="email">3. Buttons that are just an icon (WCAG 4.1.2)
The cart, wishlist, account and search icons often come without any text. A screen reader then announces nothing more than “button”.
<button type="button" aria-label="Open cart, 3 items">
<svg aria-hidden="true" focusable="false">…</svg>
</button>4. Product images lack proper alt text (WCAG 1.1.1)
Magento takes the alt text from the image label in the admin. Leave that field empty and the image gets no description, or only its file name. Fill in the labels for your key products and give purely decorative icons alt="".
5. The mini-cart traps keyboard users (WCAG 2.1.2)
The mini-cart opens, but the focus stays behind it, or Escape won’t close it. Move the focus into the mini-cart when it opens, and back to the cart button when it closes.
const cartButton = document.querySelector('[data-cart-toggle]');
const miniCart = document.querySelector('#minicart');
function openCart() {
miniCart.hidden = false;
miniCart.querySelector('a, button').focus();
}
function closeCart() {
miniCart.hidden = true;
cartButton.focus();
}
miniCart.addEventListener('keydown', (e) => {
if (e.key === 'Escape') closeCart();
});6. Checkout errors are only shown in red (WCAG 1.4.1, 3.3.1)
A red frame on its own doesn’t tell anyone much. Put the error into words, connect it to the field and mark the field as invalid.
<input id="postcode" aria-invalid="true" aria-describedby="postcode-error">
<p id="postcode-error">Please enter a 5-digit postcode.</p>7. Text contrast is too low (WCAG 1.4.3)
Pale grey on white turns up all over the place: crossed-out prices, placeholder text, footer links. Normal text needs a contrast ratio of 4.5:1 or more, and any browser contrast checker will give you the number in seconds.
8. Colour and size swatches don’t work with a keyboard (WCAG 2.1.1)
Swatches are often div elements that only react to a mouse click. Swap them for real buttons or radio inputs, so people can reach them with Tab and pick one with Space or Enter.
9. The cookie banner blocks the whole page (WCAG 2.1.1, 2.4.3)
If nobody can close or reject the banner with a keyboard, the rest of the page is out of reach too. Make the banner the first stop in the tab order and make sure every button in it can be reached.
10. The page language is wrong (WCAG 3.1.1)
If your German store view tells the browser the page is in English, screen readers will read German text with an English accent. Check that the <html> tag says lang="de" on the German store view. Magento sets it from each store view’s locale.
Luma or Hyvä: which is easier to make accessible?
A theme alone won’t make your shop compliant. Content, extensions and your own changes count just as much. The two themes do give you a different head start, though.
More work, more files
Luma dates from 2015, and much of it, the checkout in particular, is built from Knockout.js components. Fixing focus and screen-reader output there means editing JavaScript templates scattered across many files. Some of those fixes then disappear with the next upgrade.
Usually one file
Hyvä works with plain HTML templates and small Alpine.js components. Adding a label, an aria- attribute or a focus rule is usually a change in one .phtml file. The Hyvä team has also put work into accessibility in its latest releases.
So if moving away from Luma is already on your list (see our Hyvä post), accessibility gives you one more reason. Staying on Luma for now? The ten fixes above work there too. They just take longer.
Keep an eye on your extensions as well. A payment widget, a review plugin or a chat bubble loaded from someone else’s server can undo keyboard fixes your team has already made.
A test plan to start this week
Finding the first problems doesn’t take an expensive audit. Begin with the pages that bring in money: the homepage, one category page, one product page, the cart, the checkout and the customer login.
Step 1: automated scan (one hour)
Run axe over each of those pages. On the command line it looks like this:
npx @axe-core/cli https://shop.example.com/checkout \
--tags wcag2a,wcag2aa,wcag21aaLighthouse in Chrome DevTools also gives you a quick accessibility score. Keep in mind that automated tools only find some of the problems. They’ll spot a missing label or weak contrast. They can’t tell you whether a blind customer can actually get through your checkout.
Step 2: keyboard test (30 minutes)
Unplug the mouse and go from the homepage to a finished test order with nothing but Tab, Shift+Tab, Enter, Space, the arrow keys and Escape. Note every spot where you get stuck or lose track of where you are.
Step 3: screen reader test (one afternoon)
Switch on NVDA on Windows (it’s free) or VoiceOver on a Mac, and listen to the product page and the checkout. Does every button have a name? Are errors read out? Does the price still make sense when you only hear it?
Step 4: fix, then write the statement
Work through what you found, checkout first. Then put your accessibility statement in the footer. Stick to the facts: what you tested, which standard you follow, how customers can reach you and which authority is responsible.
Step 5: repeat after every release
New features and extension updates have a habit of breaking things. Add the axe scan to your deployment pipeline so it runs on every release, and do the keyboard test again before any big campaign.
Frequently asked questions
+Does the BFSG apply to my online shop?
+Do B2B-only shops have to be accessible?
+Which standard should my Magento shop meet?
+Will an accessibility overlay widget protect me?
+What happens if I get a BFSG warning letter?
Want someone to look over your shop?
Ingold Solutions builds and looks after Magento shops on both Luma and Hyvä. We’ll run the automated scan and the keyboard test on your most important pages, show you what turned up with screenshots, and fix the issues in your theme. Legal advice isn’t something we give, but your lawyer will get a clear report of what we checked and what we changed.



