The Barrierefreiheitsstärkungsgesetz (BFSG) is Germany's national law implementing the European Accessibility Act. Since June 28, 2025, businesses selling digital products or services to consumers in Germany must meet strict accessibility standards based on WCAG 2.1 AA and EN 301 549. Non-compliance carries fines up to €100,000 and potential market bans. The law affects e-commerce sites, banking services, transport platforms, and more -- essentially any B2C digital offering from companies above the microenterprise threshold.
What Is the BFSG?
The Barrierefreiheitsstärkungsgesetz -- literally the "Accessibility Strengthening Act" -- is Germany's transposition of EU Directive 2019/882, better known as the European Accessibility Act (EAA). The German parliament (Bundestag) passed the BFSG on July 16, 2021, giving businesses a nearly four-year runway before enforcement began on June 28, 2025.
So why does this law exist? Roughly 7.8 million people in Germany live with a severe disability. Millions more have situational or age-related impairments that make navigating inaccessible digital interfaces frustrating or outright impossible. The BFSG aims to guarantee that everyday digital products and services -- from online shops to banking apps -- work for everyone.
The law does not reinvent the wheel. It builds on the well-established Web Content Accessibility Guidelines (WCAG 2.1 Level AA) and the European harmonized standard EN 301 549. If you already meet those standards, you are most of the way there. But the BFSG turns voluntary best practices into legally binding obligations, backed by real enforcement.
One critical distinction: the BFSG targets private-sector companies. Germany already had public-sector accessibility rules through the Behindertengleichstellungsgesetz (BGG) and the Barrierefreie-Informationstechnik-Verordnung (BITV 2.0). The BFSG extends those principles into the commercial world.
Who Must Comply with the BFSG?
The BFSG applies to economic operators who place products on the German market or provide services to consumers (B2C). This includes manufacturers, importers, distributors, and service providers.
The scope is broad, but there is a clear exemption for microenterprises: companies with fewer than 10 employees AND an annual turnover or balance sheet total not exceeding €2 million are exempt. Notice the "and" -- both conditions must be met. A nine-person startup generating €5 million in revenue? Not exempt.
For service providers specifically, only those providing services to consumers fall under the BFSG. Pure B2B operations are outside its scope. However, if your platform serves both businesses and consumers, the consumer-facing parts must comply.
What about non-German companies? If you sell digital products or services to German consumers, the BFSG applies to you regardless of where your headquarters are. A French e-commerce site shipping to Germany, an American SaaS platform with German users -- both fall within scope.
Microenterprise Exemption: Not a Free Pass
Even if your business qualifies as a microenterprise, the exemption only covers services, not products. If you manufacture or import hardware products covered by the BFSG (self-service terminals, computers, smartphones), you must still comply regardless of company size.
Also worth noting: the exemption can disappear quickly. Hire your 10th employee or cross the €2 million threshold, and you are immediately subject to the full requirements. Smart microenterprises build accessibility in from the start rather than scrambling later.
What Products and Services Are Covered?
The BFSG casts a wide net. It covers specific categories of both physical products and digital services that consumers interact with daily.
Covered Products
Hardware products under the BFSG include general-purpose computer hardware systems (desktops, laptops, tablets), smartphones and mobile devices, self-service terminals such as ATMs, payment terminals, ticket machines, check-in kiosks, and interactive information terminals, consumer equipment used for electronic communications (routers, modems), consumer equipment for accessing audiovisual media services (smart TVs, set-top boxes), and e-book readers.
These products must be designed so that people with disabilities can perceive, operate, and understand them. For self-service terminals, that means considerations like screen reader compatibility, sufficient contrast, tactile elements, and adjustable time limits.
Covered Services
The service categories are where most digital businesses need to pay attention. Covered services include e-commerce -- any website, app, or platform where consumers can browse and purchase products or services. This is the big one. If you run an online shop targeting German consumers, you are covered.
Banking services for consumers, including online banking, mobile banking apps, and related digital interfaces fall under scope. Electronic communications services such as email, messaging, VoIP, and internet access services are covered. Passenger transport services in air, rail, bus, and waterborne transport must make their websites, mobile apps, electronic tickets, and real-time travel information accessible. The exception here is urban, suburban, and regional transport.
Audiovisual media services and access to them are included. E-books and dedicated software for e-books round out the list.
The common thread? These are services that consumers use directly. A wholesale logistics platform used only by businesses would not be covered. But a consumer-facing booking portal for the same logistics company would be.
Technical Requirements: WCAG 2.1 AA and EN 301 549
The BFSG does not define its own technical standards from scratch. Instead, it relies on the European harmonized standard EN 301 549, which directly incorporates WCAG 2.1 Level AA for web content. Meeting these standards creates a "presumption of conformity" with the law.
EN 301 549 goes beyond web content alone. It covers software (including mobile apps), hardware, electronic documents, and non-web digital interfaces. For most businesses, though, the web-related requirements in Clause 9 of EN 301 549 -- which maps directly to WCAG 2.1 AA -- will be the primary concern.
The POUR Principles
WCAG 2.1 is organized around four principles, known by the acronym POUR.
Perceivable means all information and interface components must be presentable in ways users can perceive. Text alternatives for images, captions for videos, sufficient color contrast (at least 4.5:1 for normal text), and content that works without relying solely on color.
Operable means interface components and navigation must be usable. Full keyboard accessibility, no content that flashes more than three times per second, enough time to read and interact with content, and clear focus indicators.
Understandable means content and interface operation must be predictable and readable. Clear language, consistent navigation, input assistance on forms (labels, error messages, suggestions), and content that behaves in expected ways.
Robust means content must work reliably across different assistive technologies. Valid HTML, proper ARIA attributes where needed, and compatibility with screen readers, magnifiers, and other tools.
In practical terms, meeting WCAG 2.1 AA means passing 50 specific success criteria across these four principles. Some are straightforward (every image needs alt text). Others require careful technical implementation (ensuring custom JavaScript widgets are fully keyboard-accessible and announce state changes to screen readers).
Penalties and Enforcement
Germany does not rely on goodwill alone. The BFSG establishes a clear enforcement framework with real financial consequences.
Violations of the BFSG are classified as Ordnungswidrigkeiten (administrative offenses). Fines can reach up to €100,000 for serious or repeated violations. For standard infractions, fines up to €10,000 apply. But the financial hit does not stop there -- the market surveillance authority can prohibit the sale of non-compliant products on the German market entirely, or order the withdrawal and recall of products already placed.
For services, enforcement authorities can order the cessation of non-compliant service provision. Imagine having your e-commerce site effectively banned from operating in Germany until you fix accessibility issues. That is a real possibility.
Who Enforces the BFSG?
The primary enforcement body is the MLBF (Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen), a joint market surveillance authority of all 16 German federal states, headquartered in Magdeburg. This is a new institution created specifically for the BFSG.
The Bundesfachstelle Barrierefreiheit (Federal Office for Accessibility) serves as the central advisory body, providing guidance and information to businesses. The BFIT-Bund (Federal Monitoring Office for IT Accessibility) handles the technical oversight side.
Consumers and disability organizations can file complaints directly with the MLBF. This means enforcement is not solely top-down -- grassroots complaints can trigger investigations. Given the active disability rights community in Germany, businesses should expect scrutiny.
Timeline and Deadlines
The BFSG timeline has several key dates that businesses need to understand.
July 16, 2021: The BFSG was published in the Federal Law Gazette (Bundesgesetzblatt), giving businesses nearly four years to prepare.
June 28, 2025: The enforcement date. All products placed on the market and services provided to consumers from this date forward must meet BFSG accessibility requirements.
Products already on the market before June 28, 2025 may continue to be sold in their existing form until June 27, 2030 -- a five-year transition period for legacy products. But any new product placed on the market after June 28, 2025 must comply from day one.
For self-service terminals specifically, devices already in use on June 28, 2025 can continue operating until the end of their economic lifespan, with an absolute maximum of 15 years (until June 28, 2040).
Services have no such transition period. From June 28, 2025 onward, all consumer-facing services must be accessible. If you operate an online shop, the deadline has already passed. There is no grace period.
How to Achieve BFSG Compliance
Compliance is not a one-time checkbox exercise. It requires a systematic approach, ongoing monitoring, and organizational commitment. Here is how to approach it.
Step 1: Determine If the BFSG Applies to You
First, check whether your business falls within scope. Do you have 10 or more employees, or exceed €2 million in annual turnover? Do you offer products or services in the covered categories to consumers in Germany? If both answers are yes, you need to comply. If you are unsure, consult the Bundesfachstelle Barrierefreiheit's FAQ resources or seek legal advice. Getting this wrong in either direction is costly -- unnecessary compliance work wastes resources, but ignoring obligations invites fines.
Step 2: Audit Your Current Accessibility
Run a thorough accessibility audit against WCAG 2.1 AA criteria. Use a combination of automated scanning tools (which catch roughly 30-40% of issues) and manual expert testing (which catches the rest). Automated tools are good at finding missing alt text, contrast failures, and structural issues. They cannot evaluate whether alt text is actually meaningful, whether keyboard navigation flows logically, or whether screen reader announcements make sense in context.
Prioritize your audit by user impact. A completely inaccessible checkout process is more urgent than a contrast issue on a rarely-visited policy page.
Step 3: Remediate and Implement Fixes
Based on your audit findings, create a prioritized remediation plan. Common high-impact fixes include adding or improving alt text for all meaningful images, ensuring full keyboard navigability (especially for custom components like dropdown menus, modals, and carousels), fixing form labels and error handling so screen readers can announce them, meeting color contrast ratios (4.5:1 minimum for normal text, 3:1 for large text), adding captions and transcripts for video and audio content, and ensuring proper heading hierarchy.
Do not try to fix everything at once. Start with the highest-traffic, highest-impact pages -- your homepage, product listings, checkout flow, and account management.
Step 4: Test with Real Users
Automated tools and expert audits are essential but insufficient. Testing with people who actually use assistive technologies reveals issues that no automated scanner or sighted tester will catch. A screen reader user might find your navigation technically accessible but practically unusable due to verbose announcements. A keyboard-only user might get trapped in an interactive component.
Recruit testers with diverse disabilities: screen reader users, keyboard-only users, people with low vision using magnification, and people with motor impairments using switch devices or voice control.
Step 5: Document and Maintain
The BFSG requires economic operators to provide an accessibility statement and keep documentation showing compliance efforts. Create an accessibility statement that references EN 301 549 conformance and lists any known limitations with planned remediation timelines.
Accessibility is not a project with an end date. It is an ongoing process. Every new feature, content update, or design change can introduce new barriers. Build accessibility checks into your development workflow -- code reviews, CI/CD testing pipelines, and regular re-audits at least annually.
Step 6: Claim Disproportionate Burden Only If Genuinely Applicable
The BFSG allows an exemption where full compliance would impose a "disproportionate burden" (unverhältnismäßige Belastung) under Section 17. But this is not a blanket escape clause. You must document the specific requirements that cannot be met, conduct a formal assessment weighing costs against benefits, demonstrate that you have met all other requirements, and submit this assessment to the market surveillance authority. The MLBF will verify your claims. If they find the exemption unjustified, you face retroactive enforcement. Use this provision honestly and sparingly.
BFSG vs. EAA: Key Differences Between German Law and the EU Directive
The BFSG is Germany's implementation of the European Accessibility Act (EAA), but as with any EU directive transposed into national law, there are differences worth understanding.
The EAA sets minimum requirements that all EU member states must meet. Germany generally followed the directive closely, but the enforcement mechanism is distinctly German. While the EAA leaves enforcement structure to member states, Germany created the MLBF as a dedicated cross-state authority -- a centralized approach that other countries did not all follow.
Penalty levels vary significantly across member states. Germany's maximum €100,000 fine is actually moderate compared to Spain, which allows fines up to €600,000 for serious infractions under Ley 11/2023. France, through its own transposition, sets lower base fines (€7,500 for legal entities) but ARCOM exercises broad supervisory powers for companies above €250 million turnover.
The microenterprise exemption threshold is consistent with the EAA: fewer than 10 employees and under €2 million turnover. But Germany's treatment of legacy products and transition periods aligns precisely with the directive's framework, while some member states chose different transitional provisions.
Another difference: Germany's approach to the "disproportionate burden" exemption is handled through Section 17 BFSG with documentation requirements that the MLBF actively reviews. Some other countries have more or less stringent verification procedures.
For businesses operating across multiple EU countries, the practical advice is simple: comply with WCAG 2.1 AA and EN 301 549 across the board. That satisfies the EAA's core requirements in every member state, even if enforcement details differ. Country-specific differences matter mainly for documentation, reporting, and dealing with national authorities.
What Happens If You Already Comply with BITV 2.0 or WCAG?
If you are a German organization already meeting BITV 2.0 requirements (the public-sector accessibility regulation), you are in a strong position. BITV 2.0 also references WCAG 2.1 AA, so the technical overlap is substantial. However, the BFSG has its own documentation and conformity assessment requirements that go beyond BITV 2.0.
Similarly, if you are already WCAG 2.1 AA compliant, you meet the core technical requirements. But make sure your compliance extends to EN 301 549 aspects beyond web content -- particularly mobile apps, electronic documents, and any software interfaces your customers use. Also verify that you have proper accessibility statements and conformity documentation as required by the BFSG specifically.