On June 28, 2025, the Barrierefreiheitsstärkungsgesetz (BFSG) became enforceable across Germany's private sector. This wasn't a surprise. The European Accessibility Act, which the BFSG implements, passed years ago. Yet many organizations treated June 2025 as a starting line rather than a deadline, now facing market surveillance investigations without the necessary controls.
This isn't just a hypothetical risk. It's a documented regulatory transition where the gap between legal obligation and operational readiness created compliance exposure. Here's what went wrong, which requirements applied all along, and what your team needs to do now.
What Happened
The BFSG extends accessibility requirements to private-sector businesses providing consumer products and services in Germany. Coverage includes e-commerce platforms, banking services, telecommunications, audiovisual media, self-service terminals, and consumer devices like smartphones and e-book readers.
The law doesn't introduce new technical standards. It mandates conformance with EN 301 549, the same European ICT accessibility standard that Germany's public sector has followed since the 2018 amendment to the Disability Equality Act (BGG). Organizations operating in both sectors should have been working from a unified baseline for years.
Instead, many private-sector entities treated the BFSG as a future problem. When enforcement began in June 2025, businesses that failed to comply became subject to investigations from market surveillance authorities. The law requires economic operators to keep technical documentation proving conformance and to design user interfaces that are perceivable, operable, understandable, and robust.
Timeline
2002: Germany enacts the BGG, establishing equal rights and nondiscrimination requirements for people with disabilities.
2018: The BGG is amended to incorporate provisions of the EU Web Accessibility Directive, mandating digital accessibility for public-sector websites and mobile applications. This marks the first time German law directly addresses web accessibility.
2019: The Barrier-Free Information Technology Ordinance (BITV 2.0) takes effect in May, requiring public-sector conformance with EN 301 549 and establishing detailed technical requirements.
2025: The BFSG becomes enforceable in June, extending EN 301 549 conformance obligations to private-sector consumer products and services.
The gap between 2018 and 2025 represented a seven-year window where your organization could have aligned its public and private-sector digital properties to the same standard. If you didn't, you're now operating with fragmented controls across jurisdictions and sectors.
Which Controls Failed or Were Missing
Organizations that struggled Assistive Technology the June enforcement threshold typically lacked three operational controls:
Unified conformance baselines across business units. Companies with both public-sector contracts and consumer-facing services often maintained separate accessibility programs. Public-sector teams followed EN 301 549 to meet BITV 2.0 requirements, while consumer product teams worked from internal guidelines or deferred accessibility work entirely. When the BFSG took effect, these organizations discovered they couldn't scale their existing conformance processes to cover newly regulated products and services.
Technical documentation proving conformance. The BFSG requires economic operators to maintain documentation showing how they meet applicable technical standards. This isn't a one-time audit report. It's an ongoing record of design decisions, testing results, and remediation efforts. Organizations without structured documentation workflows found themselves unable to demonstrate conformance when market surveillance authorities opened investigations.
Accessibility statements with functional feedback mechanisms. Both the BGG and BFSG require detailed accessibility statements. These must indicate whether the website or app conforms with EN 301 549, list any inaccessible content, include a feedback mechanism for users to report issues, detail how accessibility Web Accessibility Specialist reviewed, and provide contact information for dispute resolution. Organizations that published generic "we care about accessibility" statements without these elements failed to meet the regulatory requirement.
What the Relevant Standard Requires
EN 301 549 incorporates WCAG 2.1 Level AA as the accessibility baseline for websites and mobile applications. The standard extends beyond web content to cover hardware, software, documentation, and support services.
For digital interfaces, conformance means:
- Providing text alternatives for non-text content
- Ensuring all functionality is available from a keyboard
- Giving users enough time to read and use content
- Avoiding content that causes seizures or physical reactions
- Making all functionality available through various input modalities
- Helping users navigate, find content, and determine where they are
- Making text readable and understandable
- Making content appear and operate in predictable ways
- Helping users avoid and correct mistakes
- Maximizing compatibility with current and future assistive technologies
The BITV 2.0 encourages achieving "the highest possible level of accessibility" for home pages, central navigation, entry-level offers, and interactive areas such as fillable forms, user authentication, and payment processes. While Level AAA conformance isn't mandatory, your accessibility statement must document which requirements you meet and which remain inaccessible.
For German public-sector entities, the BITV 2.0 adds specific requirements: German Sign Language and Easy Language content on home pages, and accessibility statements updated annually or whenever significant changes occur.
Lessons and Action Items for Your Team
Map your regulatory obligations by business line, not by geography. If you operate in Germany, you likely face both BGG requirements (for public-sector interactions) and BFSG requirements (for consumer products and services). These laws reference the same technical standard but carry different statement and documentation obligations. Your compliance program should identify which products and services fall under each regime and maintain the appropriate controls for both.
Treat EN 301 549 as your unified baseline for European operations. The standard serves as the compliance floor across EU Member States. Germany's BITV 2.0 and BFSG both require it. Italy's Legge Stanca references it. The Web Accessibility Directive mandates it for public-sector bodies across all 27 EU countries. If you're building separate conformance programs for each jurisdiction, you're creating unnecessary complexity and compliance risk.
Build technical documentation into your development workflow. The BFSG's documentation requirement isn't satisfied by a post-launch audit. You need records showing how you designed for accessibility, what testing you performed, which issues you found, and how you remediated them. Integrate this documentation into your existing design review, testing, and release processes. When market surveillance authorities request evidence of conformance, you should be able to produce it without scrambling.
Publish accessibility statements that meet the regulatory standard. Your statement must include: conformance status against EN 301 549, a list of inaccessible content with explanations, a functional feedback mechanism, documentation of your review process, and contact information for dispute resolution. Generic statements don't satisfy the requirement. If you're unsure whether your current statement meets the standard, compare it against the specific elements listed in BITV 2.0 Annex 2.
Establish a cross-jurisdictional review process for multinational operations. If you serve both U.S. and European markets, you're working under different legal frameworks with overlapping technical requirements. The DOJ Final Rule (2024) requires WCAG 2.1 Level AA conformance for ADA Title II entities. EN 301 549 incorporates the same baseline. Your accessibility governance program should identify where these requirements align and where they diverge, then maintain controls that satisfy both without duplicating effort.
The June 2025 enforcement date wasn't the beginning of your BFSG obligations. It Web Accessibility Specialist the end of your preparation window. Organizations that treated it as a deadline rather than a milestone now face investigations without the documentation, statements, or conformance controls they should have built years ago.
