The Law Is in Effect – And Enforcers Are Active
Since June 28, 2025, Germany's Barrierefreiheitsstärkungsgesetz (BFSG) – the Accessibility Strengthening Act – has been mandatory. Online retailers who haven't adapted their shops face fines up to €100,000 and competitive cease-and-desist letters. This guide shows you the path to compliance – and why accessibility also improves your SEO ranking.
- Introduction: Why Accessibility Is Now Mandatory
- What Is the BFSG? Background and Legal Framework
- Who Is Affected? Thresholds and Exemptions
- Concrete Requirements: WCAG 2.1 AA in Practice
- BFSG Enforcement: Risks, Fines, and Defense
- Accessibility as an SEO Turbo: Why Google Favors Inclusive Shops
- The BFSG Checklist: 12 Points for Your Online Shop
- Implementation Roadmap: 6 Steps to Compliance
- Tools and Tests for Accessibility Auditing
- The Accessibility Statement: What Must Be Included?
- Frequently Asked Questions (Glossary)
Introduction: Why Accessibility Is Now Mandatory
In Germany alone, approximately 7.8 million people live with a severe disability – and millions more experience temporary or age-related impairments that make navigating an online shop a daily challenge. Whether visual impairment, motor limitation, hearing loss, or cognitive disability: for all these people, digital commerce has been an obstacle course of inaccessible interfaces and insurmountable barriers.
The European Union responded with the European Accessibility Act (EAA), creating a unified legal framework that Germany has implemented as the Barrierefreiheitsstärkungsgesetz (BFSG) – the Accessibility Strengthening Act. Since June 28, 2025, it applies without transitional periods for digital services. This means: online shops targeting consumers (B2C) must be accessible now.
But the BFSG is far more than a regulatory checkbox. It's a strategic opportunity. Accessibility doesn't just improve the experience for people with disabilities – it improves the experience for everyone. And Google rewards exactly that with better rankings. In this article, you'll learn everything online retailers need to know: from the legal foundations through concrete technical requirements to a battle-tested implementation roadmap.
"Accessibility is not a feature you bolt on at the end of a project. It's a design philosophy that must be woven into the DNA of a digital product from the very beginning – like security or performance."
What Is the BFSG? Background and Legal Framework
The Barrierefreiheitsstärkungsgesetz (BFSG) is Germany's implementation of EU Directive 2019/882 – the European Accessibility Act (EAA). The law's goal is to ensure that products and services in electronic commerce are perceivable, operable, understandable, and robust for people with disabilities.
These four principles are not arbitrary – they originate from the Web Content Accessibility Guidelines (WCAG), the internationally recognized standard for digital accessibility. The BFSG references WCAG 2.1 Level AA as the technical benchmark through the harmonized standard EN 301 549.
The Four WCAG Principles (POUR)
Perceivable: All content must be presented in ways that can be perceived by all senses – even without sight or hearing.
Operable: The entire interface must be operable via keyboard, voice control, or assistive technology.
Understandable: Text, navigation, and error messages must be clear and predictable.
Robust: Content must be compatible with various user agents and assistive technologies.
Timeline and Transitional Period
The BFSG is published in Germany's Federal Law Gazette. A 3-year transitional period begins.
The BFSG takes full effect. All B2C services in electronic commerce must be accessible from this day forward.
First waves of cease-and-desist letters are documented. Market surveillance authorities begin inspections. Competitors and associations take action against non-compliant shops.
Authorities intensify enforcement. WCAG 2.2 gains importance. Accessibility becomes a standard SEO factor and conversion lever.
Who Is Affected? Thresholds and Exemptions
The BFSG essentially applies to all services in electronic commerce targeting consumers (B2C). This includes:
- Online shops (regardless of product range)
- Booking portals (travel, events, accommodations)
- Digital customer portals and self-service areas
- Websites that enable the conclusion of a contract
- E-banking and financial services
The Microenterprise Exemption
There is an important exemption: Microenterprises providing services are exempt from the obligation. The thresholds are:
Fewer Than 10 Employees
The company employs fewer than 10 people (full-time equivalent).
Max. €2M Revenue
Annual revenue or annual balance sheet total does not exceed 2 million euros.
Caution: Products Are Not Exempt!
The microenterprise exemption only applies to services. If you sell products that themselves fall under the BFSG (e.g., e-book readers, certain IT hardware, banking terminals), these must meet accessibility requirements even as a microenterprise. Additionally: even if your company qualifies for the exemption, implementing accessibility is still strongly recommended, as it expands your audience, improves Core Web Vitals, and eliminates legal risk.
B2B vs. B2C: A Common Misconception
Pure B2B companies are generally not directly affected by the BFSG, as the law focuses on consumer transactions. However, there are two important caveats: First, even a "primarily B2B" website may be affected if it contains consumer-facing areas (e.g., a publicly accessible web shop). Second, B2B companies are indirectly forced to demonstrate accessibility through supply chain requirements from their customers – similar to the NIS2 Directive in the cybersecurity space.
Concrete Requirements: WCAG 2.1 AA in Practice
WCAG 2.1 AA consists of 50 success criteria. For online retailers, the following areas are particularly critical, as they see the most frequent violations and create the biggest barriers for users:
Every product image must have a descriptive alt text that describes the content. Decorative images receive an empty alt attribute (alt=""). Without alt texts, screen reader users are blind to product photos.
The entire shop – including navigation, search, filters, cart, and complete checkout – must be operable without a mouse. Every interactive element must be reachable via Tab and activatable via Enter/Space.
Text must have a contrast ratio of at least 4.5:1 against its background (3:1 for large text). Information must never be conveyed through color alone (e.g., red error messages must also be identifiable through text).
All input fields in checkout must be correctly labeled with <label> elements. Error messages must be clearly formulated and programmatically linked to the erroneous field (aria-describedby).
Correct heading hierarchy (H1→H2→H3), semantic elements (<nav>, <main>, <footer>), landmark roles, and logical tab order. Screen readers navigate primarily through page structure.
Content must remain usable without information loss at 200% text magnification. No content may be cut off when zoomed. Mobile views must be equally accessible as desktop.
Product videos must have subtitles. Purely visual information in videos (e.g., product demos) should be supplemented with audio description. Live streams are currently exempt from subtitling.
The keyboard focus must be visible at all times (focus indicator with at least 2px contrast). For modals, overlays, and dynamic content, focus must be correctly set and returned when closing.
The Checkout Process: The Most Critical Area
The checkout is the nerve center for e-commerce accessibility. This is where contracts are concluded – and where the greatest legal risks lie. An accessible checkout includes:
- Correct Input Types:
type="email",type="tel",autocompleteattributes for address fields - Error Handling: Clear, understandable error messages with concrete hints for correction
- Progress Indication: An accessible multi-step indicator with ARIA attributes
- Payment Options: All payment methods must be selectable via keyboard
- Order Confirmation: ARIA live regions for dynamic status messages
BFSG Enforcement: Risks, Fines, and Defense
Since the BFSG came into effect in June 2025, the feared wave of enforcement actions has materialized. Numerous online retailers have received cease-and-desist letters – some generic and standardized, others targeted and detailed. The legal risks are real and significant:
Regulatory Sanctions
State market surveillance authorities
Up to €100,000Fines for non-compliance. In cases of severe or repeated violations, a sales ban for the digital offering may also be imposed.
Competitive Cease-and-Desist
By competitors, associations, or chambers
€2,000 – €25,000Per letter: legal fees, contractual penalties for recurrence, injunction proceedings. Serial enforcement can become existentially threatening.
Who Can Take Legal Action?
- Competitors: Direct competitors can issue warnings under competition law
- Qualified Associations: Consumer associations and trade associations have the right to sue
- Chambers of Commerce: IHKs (in Germany) can also prosecute violations
- Market Surveillance Authorities: Official controls with the power to issue fines
How to Respond to a Cease-and-Desist Letter
Don't pay or sign immediately. Review the set deadline and have the letter evaluated by a specialized IT and competition law attorney.
Not every cease-and-desist letter is legally valid. Check whether the sender actually has standing and whether the alleged violations are specifically enough formulated.
Simultaneously conduct an accessibility audit and begin fixing legitimate issues. Document all measures thoroughly.
Your attorney can draft a modified declaration that better protects your interests than the version provided by the claimant.
Accessibility as an SEO Turbo: Why Google Favors Inclusive Shops
Accessibility and SEO in the AI era are not separate disciplines – they are two sides of the same coin. Google has strongly evolved its ranking algorithms toward user experience in recent years. Accessibility measures improve almost every aspect that Google evaluates:
Semantic HTML → Better Indexability
Correct heading hierarchies, ARIA labels, and semantic elements don't just help screen readers – they help Google's crawlers better understand and evaluate page content, directly improving your E-E-A-T signals.
Alt Texts → Image Search Traffic
Descriptive alt texts for product images are a direct SEO factor for Google Image Search. A "Blue Women's Winter Coat Size M" generates organic traffic – an "IMG_3847.jpg" does not.
Responsive Design → Mobile First
The BFSG requirement for zoom capability and mobile accessibility aligns with Google's Mobile-First Indexing. An accessible shop is automatically mobile-optimized.
Reduced Bounce Rates → Better Rankings
Accessible shops have 15-30% lower bounce rates on average because navigation is more intuitive and content more understandable. Google interprets this as a positive user engagement signal.
Structured Data → Rich Snippets
The semantic markup required for accessibility greatly facilitates Schema.org implementation. The result: more rich snippets, higher click-through rates in SERPs.
Larger Target Audience → More Traffic
About 15% of the world's population lives with a disability. An accessible shop opens up an audience that competitors have been excluding – a direct competitive advantage.
"What's good for accessibility is good for SEO. What's good for SEO is good for all users. This equation is no coincidence – it's the result of a shared design philosophy that puts people at the center."
The BFSG Checklist: 12 Points for Your Online Shop
Use this checklist as a guide for an initial self-assessment. Each point corresponds to a critical WCAG 2.1 AA requirement relevant to BFSG compliance:
All Images Have Alt Texts
Product images have descriptive alt texts. Decorative images have empty alt attributes. Icons with function have ARIA labels.
Complete Keyboard Navigation
All interactive elements are reachable via Tab. The focus indicator is visible. No keyboard traps (can't be exited).
Contrast Ratios Met
All texts meet the 4.5:1 contrast ratio (3:1 for large text). Buttons and links are recognizable without color.
Forms Correctly Labeled
All input fields have associated labels. Required fields are clearly marked. Error messages are understandable and screen reader accessible.
Heading Hierarchy Correct
Each page has exactly one H1. The hierarchy H1→H2→H3 is logical and complete. No skipped levels.
Links Are Descriptive
No "Click here" links. Every link describes its destination. "View all winter jackets" instead of "Learn more."
Zoom to 200% Works
At double magnification, no content is lost. No horizontal scrolling at 1280px viewport.
Videos Have Subtitles
All embedded videos have synchronized subtitles (open or closed captions). Audio-only content has transcripts.
Language Is Defined
The HTML lang attribute is correctly set. Language changes within text are marked with lang attributes.
Skip Navigation Present
A "Skip to content" link is placed as the first focusable element on the page.
ARIA Correctly Implemented
Custom widgets (sliders, tabs, modals) have correct ARIA roles, states, and properties. Dynamic content uses ARIA live regions.
Accessibility Statement Published
An easily findable accessibility statement is linked on the website, describing the degree of conformance and a feedback mechanism.
Implementation Roadmap: 6 Steps to Compliance
Implementing BFSG requirements doesn't have to be an overwhelming mega-project. With a structured approach, compliance can be achieved incrementally and with minimal risk:
Step 1: Accessibility Audit
Conduct a comprehensive audit of your online shop – ideally both automated (WAVE, axe DevTools, Lighthouse) AND manual (keyboard testing, screen reader testing with NVDA or VoiceOver). Document all found barriers by severity.
Step 2: Risk-Based Prioritization
Start with the highest risks: the checkout process, navigation, and product pages. These areas carry the greatest legal exposure and have the most impact on user experience. Create a prioritized action plan.
Step 3: Implement Quick Wins
Many accessibility improvements require minimal effort: add alt texts, adjust contrasts, activate focus styles, add skip navigation, set lang attributes. These quick wins can fix 40-60% of violations.
Step 4: Structural Adjustments
Revise page structure: semantic HTML, correct heading hierarchy, ARIA landmarks. If your shop runs on outdated technology, consider a migration to a modern framework.
Step 5: Accessibility Statement
Create and publish an easily findable accessibility statement. It must describe the current level of conformance, transparently name remaining limitations, and offer a feedback mechanism.
Step 6: Monitoring and Training
Accessibility is not a one-time project but an ongoing process. Integrate accessibility checks into your CI/CD workflow, train content creators, and conduct audits regularly (at least quarterly).
Tools and Tests for Accessibility Auditing
Accessibility testing requires a combination of automated tools and manual tests. Automated tools can detect approximately 30-40% of all barriers – the rest requires human verification.
Automated Testing Tools
Browser WAVE (Web Accessibility Evaluation Tool)
Free browser plugin that visually marks barriers directly on the page. Ideal for a quick first overview. Shows alt text errors, contrast problems, and structural deficiencies.
DevTools axe DevTools (Deque)
Chrome extension for in-depth accessibility analysis. Provides specific WCAG references for each error found and concrete correction hints. CI/CD pipeline integration possible.
Google Lighthouse Accessibility Audit
Integrated into Chrome DevTools. Evaluates accessibility on a scale of 0-100. Based on axe-core. However, a score of 100 does not mean WCAG AA compliance – it only covers automated rules.
BITV BIK-BITV-Test
German standard test that checks BITV 2.0 (the German standard). Particularly relevant for official controls. Includes 60 test steps – 25 automated, 35 manual.
Manual Tests: What Automation Cannot Replace
Navigate the entire shop using only the keyboard (Tab, Enter, Space, Arrow keys, Escape). Can you find all products, add them to cart, and complete an order – without a mouse?
Test with NVDA (Windows, free) or VoiceOver (macOS/iOS, built-in). Are product names, prices, and reviews correctly readable? Is the checkout process understandable?
Zoom the page in the browser to 200% (Ctrl/Cmd + +). Does the layout still work? Is all content visible without having to scroll horizontally?
The Accessibility Statement: What Must Be Included?
The BFSG requires an easily findable accessibility statement. It must contain the following information:
Describe the extent to which your offering meets accessibility requirements: "fully conformant," "partially conformant," or "non-conformant."
Transparently list which areas are not yet accessible and why (disproportionate burden, technical limitation, work in progress).
Provide an email address or contact form through which users can report barriers. Respond demonstrably within 4 weeks.
Reference the competent arbitration body that users can contact if the feedback mechanism does not lead to a satisfactory resolution.
Do you have questions about digital accessibility?
Book a free consultationHave a vision?
Let's check together how we can make your idea take flight.
Book your free strategy call nowFrequently Asked Questions (Glossary)
Barrierefreiheitsstärkungsgesetz (BFSG)
Germany's Accessibility Strengthening Act, implementing the European Accessibility Act (EAA). It requires providers of B2C services in electronic commerce to make their digital offerings accessible. In effect since June 28, 2025.
WCAG (Web Content Accessibility Guidelines)
The internationally recognized standard for digital accessibility, published by the W3C. WCAG 2.1 Level AA defines the minimum technical requirements referenced by the BFSG through the EN 301 549 standard.
EN 301 549
The harmonized European standard for accessibility requirements for ICT products and services. It bridges the legal BFSG framework with the technical WCAG standards.
ARIA (Accessible Rich Internet Applications)
A W3C specification providing HTML attributes to make interactive web elements accessible to assistive technologies. ARIA roles, states, and properties supplement missing semantic HTML.
Screen Reader
An assistive technology that converts screen content into speech or Braille. Popular screen readers include NVDA (Windows, free), JAWS (Windows, commercial), and VoiceOver (macOS/iOS, built-in).
Accessibility Statement
A document required by the BFSG that transparently informs about the degree of accessibility of a digital offering, names existing limitations, and provides a feedback mechanism for users.
European Accessibility Act (EAA)
EU Directive 2019/882, creating a unified legal framework for accessibility of products and services in the EU. The BFSG is the national implementation of this directive in Germany.
Alt Text (Alternative Text)
An HTML attribute for images providing a textual description of the image content. Alt texts are read aloud by screen readers and indexed by search engine crawlers – a dual benefit for accessibility and SEO.