vibrance
Book a call

Web accessibility: who the German BFSG applies to and what WCAG 2.2 requires in practice

Since 28 June 2025, Germany's Accessibility Strengthening Act (BFSG) has required certain providers to make their digital offerings accessible. This article explains its scope, the exemption for microenterprises, its relationship to the Web Content Accessibility Guidelines and the issues that, according to measurements, are found on almost every website.

by Kilian Dickmann, Founder and ownerPublished on 7 min read

For a long time, accessibility was a topic for public bodies and large companies. With the Accessibility Strengthening Act (Barrierefreiheitsstärkungsgesetz, BFSG), it has also had a legal dimension for private providers in Germany since 28 June 2025. At the same time, measurements show that the vast majority of websites fail even basic requirements. Small businesses therefore face two questions: am I legally affected? And what does accessibility mean technically, regardless of the law?

From the European Accessibility Act to the BFSG

The BFSG implements Directive (EU) 2019/882, known as the European Accessibility Act [1] [2]. The specific technical requirements are set out in an ordinance, the BFSGV [3]. Websites of public bodies in Germany have long been subject to separate rules, the BITV 2.0 [9]; these do not apply to private businesses.

Who is affected

The BFSG does not apply to all websites but to certain products (such as computers, smartphones, e-readers, ATMs and ticket machines) and certain services provided to consumers after 28 June 2025 [2]. For most business websites, the relevant category is services in electronic commerce: websites and apps through which consumers can conclude contracts, such as online shops, bookings with payment or paid orders.

This leads to an important distinction:

  • A purely informational website without contract conclusion, such as a trade business presenting itself with a contact form, is generally not covered by the act.
  • A website through which consumers order, book or buy can be covered.
  • Offerings exclusively for businesses (B2B) are not covered.

The exemption for microenterprises

The BFSG does not apply to services offered by a microenterprise (§ 3(3) BFSG) [2]. Microenterprises are businesses that employ fewer than ten people and whose annual turnover or balance sheet total does not exceed two million euros. The terms are based on the European SME definition [4]. Both conditions must be met together.

The exemption only covers services, not products. A small online retailer is exempt with its shop as a service but cannot rely on the exemption for the products it sells. Under this system, a hair salon with four employees and online appointment booking is not affected. If a business grows beyond the thresholds, the exemption no longer applies.

Supervision and consequences

In Germany, compliance is monitored by the market surveillance authority of the federal states for the accessibility of products and services (MLBF) based in Magdeburg, a joint body of all federal states [8]. It can order measures and impose fines for breaches; consumers and associations can ask it to take action. Whether competitors can additionally pursue breaches under unfair competition law has not yet been conclusively settled. Providers that are covered must also state in their terms and conditions or in another clearly perceptible way how their service meets the requirements [2].

The technical benchmark: WCAG

The BFSG itself does not contain a checklist. The BFSGV sets out functional requirements; in practice, compliance is demonstrated by meeting harmonised standards, which for digital offerings is the European standard EN 301 549 [6]. For web content, it refers to the Web Content Accessibility Guidelines (WCAG) of the World Wide Web Consortium at conformance level AA [5].

The current version is WCAG 2.2 from October 2023 [5]. It adds nine success criteria to WCAG 2.1, including on keyboard focus not being obscured, minimum target size, alternatives to dragging movements, consistently placed help, avoiding redundant entry and accessible authentication [10]. Anyone building something new today is well advised to aim for WCAG 2.2 AA, which also covers the requirements of 2.1.

The four principles

WCAG assigns every criterion to one of four principles [5]:

  1. Perceivable: information must be presented so that everyone can perceive it, for example through text alternatives for images, sufficient contrast and captions.
  2. Operable: all functions must be available without a mouse, using only the keyboard; users need enough time and must not be put at risk by flashing content.
  3. Understandable: text and operation must be comprehensible, and forms must detect and explain errors.
  4. Robust: content must be interpreted reliably by different browsers and assistive technologies such as screen readers.

What measurements show

The US project WebAIM runs an automated analysis of the home pages of the one million most visited websites every year. In the 2025 report, 94.8 percent of these home pages had detectable WCAG failures, with an average of around 51 errors per page. The most common error was low text contrast, found on 79.1 percent of pages. Six types of error together accounted for around 96 percent of all errors found [7].

Two limitations matter: automated tests only detect some of the possible barriers, so the actual share of fully conformant pages is likely to be even lower. And the concentration on a few types of error means, conversely, that a lot can be achieved with comparatively few measures.

The most common issues and how to fix them

Problem WCAG reference Solution
Low contrast 1.4.3 Contrast (Minimum) Body text at least 4.5 : 1 against the background, large text at least 3 : 1. Define colours once and measure them.
Images without a text alternative 1.1.1 Non-text Content Describe informative images; mark purely decorative images with an empty alternative text.
Form fields without labels 1.3.1, 3.3.2 Every field with a visible, programmatically associated label; placeholder text does not replace it.
Links without meaningful text 2.4.4 Link Purpose “More about our prices” instead of “click here”.
Missing page language 3.1.1 Language of Page Declare the language in the HTML so that screen readers pronounce text correctly.
Invisible keyboard focus 2.4.7, 2.4.11 A clearly visible focus outline that is not covered by fixed elements.
Targets that are too small 2.5.8 Target Size (Minimum) Click targets of at least 24 × 24 CSS pixels or sufficient spacing.
Motion with no way out 2.2.2, 2.3.3 Let users pause automatic motion and respect the “reduce motion” system setting.

A heading structure that organises the content logically (1.3.1) and a layout that works at 200 percent zoom and on narrow screens without horizontal scrolling (1.4.4, 1.4.10) are also among the basics [5].

Approach for small businesses

  1. Clarify whether you are affected. Are contracts with consumers concluded through the website? Is the business a microenterprise within the meaning of the BFSG? If in doubt, a short legal assessment is worthwhile.
  2. Test automatically. Freely available testing tools find a large share of the common errors, especially contrast, missing alternative text and labels.
  3. Test manually. Use the whole website once with the keyboard only: is every link and field reachable, is the focus always visible, can a form be submitted? In addition, listen to one page with a screen reader.
  4. Connect design and content. Accessibility does not only happen in code. Colours, font sizes, image descriptions and understandable text are decided during design and writing.
  5. Document. Record what was tested, when and with what result. For providers that are covered, such documentation is also the basis of the mandatory information.

Why it is worthwhile even without an obligation

Even businesses not covered by the BFSG benefit from an accessible website. Many requirements improve use for everyone: sufficient contrast in sunlight on a smartphone, understandable form errors, large touch targets, a clear structure. In addition, the scope may change in future, and experience shows that retrofitting accessibility is more work than considering it from the start.

Conclusion

The BFSG does not affect every business website. Purely informational sites and services provided by microenterprises are exempt. But anyone concluding contracts with consumers online and exceeding the thresholds has to meet the requirements, whose practical benchmark is WCAG 2.1 or 2.2 at level AA. Regardless of the legal obligation, the measurement data show that a few measures, above all sufficient contrast, text alternatives and labels, remove a large share of common barriers.

Frequently asked questions

Does the BFSG apply to every business website?
No. It mainly affects websites through which consumers conclude contracts, such as shops or bookings with payment. Purely informational sites and B2B-only offerings are generally not covered.
Are microenterprises exempt from the BFSG?
For services, yes: businesses with fewer than ten employees and an annual turnover or balance sheet total of no more than two million euros. The exemption does not apply to products.
Which technical standard applies to accessible websites?
In practice, WCAG at level AA, via the European standard EN 301 549. New websites are well advised to aim for WCAG 2.2 AA.

Sources

The numbers in square brackets in the text refer to this list. Online sources last checked in November 2026.

  1. [1]Directive (EU) 2019/882 on the accessibility requirements for products and services (European Accessibility Act). eur-lex.europa.eu/eli/dir/2019/882/oj
  2. [2]Act implementing the accessibility requirements for products and services (Barrierefreiheitsstärkungsgesetz, BFSG) of 16 July 2021. www.gesetze-im-internet.de/bfsg/
  3. [3]Ordinance on accessibility requirements for products and services under the BFSG (BFSGV). www.gesetze-im-internet.de/bfsgv/
  4. [4]Commission Recommendation 2003/361/EC concerning the definition of micro, small and medium-sized enterprises. eur-lex.europa.eu/eli/reco/2003/361/oj
  5. [5]W3C, Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation, 5 October 2023. www.w3.org/TR/WCAG22/
  6. [6]ETSI, EN 301 549 V3.2.1 (2021-03): Accessibility requirements for ICT products and services.
  7. [7]WebAIM, The WebAIM Million: The 2025 report on the accessibility of the top 1,000,000 home pages. webaim.org/projects/million/
  8. [8]Market surveillance authority of the German federal states for the accessibility of products and services (MLBF), Magdeburg. www.mlbf-barrierefrei.de
  9. [9]Accessible Information Technology Ordinance (BITV 2.0). www.gesetze-im-internet.de/bitv_2_0/
  10. [10]W3C Web Accessibility Initiative, What's New in WCAG 2.2. www.w3.org/WAI/standards-guidelines/wcag/new-in-22/

About the author

Kilian Dickmann, Founder and owner

Designs and builds websites for small businesses and writes here about design, technology, accessibility and data protection in practice.

More insights

Questions about your own site?

In a free thirty-minute call we look at it together.