Skip to main content

Accessibility

BFSG, WCAG 2.2 and EN 301 549: what applies to digital accessibility now

Germany's BFSG has applied since June 2025. Who is affected, how WCAG 2.2 and EN 301 549 relate, and how accessibility testing works in practice.

Braille-Tastatur

The BFSG at a glance

The Barrierefreiheitsstärkungsgesetz (BFSG), Germany's Accessibility Strengthening Act, transposes the European Accessibility Act (Directive (EU) 2019/882) into German law. Since 28 June 2025, certain products and services aimed at consumers must be accessible. The goal: people with disabilities and older people should be able to use digital services without help from others.

For businesses, this means that for many digital services, accessibility is no longer an optional improvement but a legal requirement – monitored by an authority and backed by possible fines. Other EU member states have adopted comparable laws based on the same directive.

Note: this article provides a professional overview and does not constitute legal advice.

Who is affected – and who is not?

The BFSG applies to offerings for consumers (B2C). The services covered include:

  • E-commerce services – websites and apps through which consumers conclude contracts, such as online shops, booking portals or subscriptions.
  • Consumer banking services, such as online banking.
  • Electronic communications services and messaging services.
  • Passenger transport: websites, apps, electronic tickets and real-time travel information.
  • E-books and dedicated software.

In addition, products such as computers, smartphones, e-readers, routers and self-service terminals like ATMs or ticket machines are covered.

Exemptions

  • Micro-enterprises providing services are exempt. This means businesses with fewer than ten employees and an annual turnover or balance sheet total of no more than 2 million euros. The exemption does not apply to products.
  • Purely B2B offerings are not covered by the law.
  • An exemption is also possible if the requirements would impose a disproportionate burden or fundamentally alter the product or service. This assessment must be documented and justified.

A website that is purely informational, without consumers concluding contracts through it, is generally not covered by the BFSG. Public sector bodies are subject to separate rules anyway (the Disability Equality Act and BITV 2.0). Whether a specific offering is covered should be assessed case by case.

Deadlines and transitional rules

  • Since 28 June 2025: new products and services must meet the requirements.
  • Until 27 June 2030: services may continue to be provided using products that were already in use before 28 June 2025. Contracts concluded before that date may continue unchanged until then.
  • Self-service terminals in operation before the deadline may remain in use until the end of their economic life, but no longer than 15 years after being put into service.

Important: the transition period until 2030 is not a free pass for existing websites. Every new feature and every relaunch should already meet the requirements.

What are the consequences of non-compliance?

Enforcement lies with the Market Surveillance Authority of the Federal States for the Accessibility of Products and Services (MLBF), based in Magdeburg. It can review offerings, demand corrections and, as a last resort, prohibit a product or service from being offered. Consumers and recognised associations can request action from the authority.

In addition, Section 37 BFSG provides for fines of up to 100,000 euros, and up to 10,000 euros for other violations. Whether competitors can also pursue violations under unfair competition law is under discussion. Regardless of that, a website people cannot use costs customers – and therefore revenue.

How the BFSG, EN 301 549 and WCAG relate

The three terms often appear together but play different roles:

  • The BFSG and its ordinance (BFSGV) define that something must be accessible and what. The ordinance describes the requirements in general terms, for example perceivable, operable, understandable and robust.
  • EN 301 549 is the harmonised European standard that specifies these requirements technically. It is published jointly by ETSI, CEN and CENELEC – contrary to a common label, it is not an ISO standard. Meeting the standard gives a presumption of conformity with the legal requirements.
  • WCAG (Web Content Accessibility Guidelines) are the W3C's internationally used guidelines for accessible web content. For websites and apps, EN 301 549 essentially refers to the WCAG success criteria at levels A and AA.

Which version applies?

The version currently cited in the Official Journal of the EU, EN 301 549 V3.2.1, refers to WCAG 2.1. In September 2026, the new edition EN 301 549 V4.1.1 was published. It is aligned with WCAG 2.2 and tailored specifically to the European Accessibility Act. It takes full legal effect once it is cited in the Official Journal of the EU.

Our recommendation: plan, build and test new offerings against WCAG 2.2 level AA now. This also covers the WCAG 2.1 criteria and prepares you for the new standard.

What WCAG 2.2 adds

WCAG 2.2 was published in October 2023 and adds nine success criteria to WCAG 2.1. Six of them are at levels A and AA and therefore relevant for the BFSG:

  • 2.4.11 Focus Not Obscured (Minimum) (AA): the element with keyboard focus must not be entirely hidden by other content, such as a sticky header or cookie notice.
  • 2.5.7 Dragging Movements (AA): anything that works by drag and drop must also be operable with simple clicks or taps.
  • 2.5.8 Target Size (Minimum) (AA): click targets must be at least 24 × 24 CSS pixels or have sufficient spacing between them.
  • 3.2.6 Consistent Help (A): help options such as contact details or chat appear in the same place on every page.
  • 3.3.7 Redundant Entry (A): information already entered in the same process must not be requested again, but pre-filled or offered for selection.
  • 3.3.8 Accessible Authentication (Minimum) (AA): logins must not require cognitive puzzles, such as transcribing characters from an image, without an alternative. Pasting passwords and using password managers must work.

Three further criteria belong to level AAA. At the same time, criterion 4.1.1 "Parsing" was removed because modern browsers and assistive technologies now handle faulty HTML reliably.

How accessibility testing works in practice

  1. Define the scope: which pages, templates and flows will be tested? For an online shop, this includes the home page, search, product page, cart, checkout, login and contact.
  2. Automated checks: tools such as axe or Lighthouse quickly find typical issues, like missing alternative text, insufficient contrast or unlabelled form fields. But they detect only some of the barriers.
  3. Manual testing against WCAG 2.2 AA: keyboard-only operation, screen readers such as NVDA and VoiceOver, 200% and 400% zoom, increased text spacing and testing on smartphones.
  4. Prioritised report: each barrier is documented with the affected criterion, its location, the impact on users and a concrete fix. The development team knows where to start.
  5. Retest: after the fixes, testing confirms the barriers are actually gone and no new ones have appeared.
  6. Embed it: accessibility becomes part of the definition of done, the component library and automated tests, so it is preserved in future changes.

For services, the BFSG also requires an explanation in the terms and conditions, or in another clearly perceivable way, of how the service meets the requirements. The test results provide a good basis for this.

Three common misconceptions

  • "An overlay plugin makes the website accessible." Tools that place a control bar over the page via script do not fix the causes in the code. Missing labels, wrong focus order or inaccessible forms remain – and some overlays even make things harder for screen reader users.
  • "The checking tool shows no errors, so we are compliant." Automated tests are a good start but do not replace manual testing. Whether a flow is understandable and usable with assistive technology can only be established by trying it.
  • "Accessibility automatically brings better Google rankings." Accessibility is not a direct ranking factor. However, many measures overlap with good SEO: a clean heading structure, meaningful link text, alternative text and fast, stable pages help people and search engines alike.

How we support you

We test websites, online shops, portals and apps for accessibility – against WCAG 2.2 level AA and EN 301 549, using automated tools and thorough manual testing with keyboard and screen reader:

  • Initial check of the most important pages and flows to assess what needs to be done.
  • Full accessibility test with a prioritised report and concrete fixes for your development team.
  • Retest after the fixes.
  • Project support, so accessibility is considered from the start and secured over time.

This is based on more than ten years of hands-on quality assurance and certification as an A4Q Certified Professional in Digital Accessibility.

You can find the process and scope of our audit on the page accessibility testing under the BFSG and WCAG 2.2.

Frequently asked questions

Does the BFSG apply to B2B websites?

No. The BFSG covers products and services for consumers. If an offering is aimed exclusively at businesses, it is not covered by the law. Accessibility still makes sense there, for example for employees with disabilities.

Does a purely informational website have to be accessible?

Generally not under the BFSG, as long as no contracts with consumers are concluded through the website. As soon as bookings, orders or subscriptions are possible, the website may be covered as an e-commerce service.

Which WCAG version should I test against?

WCAG 2.2 level AA. The new standard EN 301 549 V4.1.1 is aligned with WCAG 2.2, and meeting WCAG 2.2 also covers the WCAG 2.1 criteria referenced by the version cited so far.

Is EN 301 549 an ISO standard?

No. EN 301 549 is a European standard published jointly by ETSI, CEN and CENELEC. The label "ISO EN 301 549" is common but incorrect.

Is an automated test enough for the BFSG?

No. Automated tools detect only some barriers. A reliable assessment requires manual testing with keyboard, screen reader and magnification along the WCAG success criteria.

Industries

Industry expertise

Every industry has its own rules, risks and auditors. We know them from practice – and test so that your software not only works but stands up to every audit.

  • Financial services

    Online banking, core banking systems and regulated processes. We test against high security and compliance requirements – so releases stay predictable, traceable and auditable.

    • BFSG
    • DORA
    • BAIT
  • Public sector

    Specialist applications, citizen portals and SAP landscapes. Accessibility under BITV, clean acceptance testing and documentation that stands up to any audit.

    • BITV 2.0
    • EN 301 549
    • SAP
  • IT & Software

    For software vendors and IT service providers: test strategy, automation in the CI/CD pipeline and quality assurance of AI features – from MVP to release.

    • CI/CD
    • Test automation
    • EU AI Act