Skip to main content
Exostruction
Back to overview
Juljan Blischke4 min read

Accessible Websites under the BFSG: What Market Surveillance Checks

The BFSG has applied since June 2025. Who is affected, what market surveillance checks and what clients of websites and web apps should do now.

Guide
Accessible Websites under the BFSG: What Market Surveillance Checks

Yes: if your website or web app offers something to consumers, it has had to be accessible since 28 June 2025. The German Accessibility Strengthening Act (BFSG) mainly affects online shops, booking and ordering flows and other e-commerce services. Pure B2B offerings and micro-enterprises are exempt. In practice, the benchmark is the EN 301 549 standard and therefore WCAG 2.1 at level AA. This article explains who is covered, what is checked and what clients should do now.

Who is covered by the BFSG

The law explicitly protects consumers. Section 1 of the BFSG lists exhaustively which products and services are in scope. For websites and apps, the relevant category is services in electronic commerce, meaning offerings through which consumers conclude contracts online. The general duty to provide accessible services is set out in section 3 BFSG.

SituationCovered?
Online shop for end customersYes
Booking or ordering flow for consumers in a web appYes
Pure B2B platform without consumer accessGenerally no
Service provider with fewer than 10 employees and no more than EUR 2 million annual turnover or balance sheet totalNo, micro-enterprise exemption for services (section 3 (3) BFSG)
Page that encourages consumers to conclude a paid contractMay be covered, case-by-case review

Two notes: the micro-enterprise exemption applies to services only, not to products. And when in doubt, assume a consumer connection, because the mere possibility that consumers use the offering points towards coverage. This is a professional assessment, not legal advice.

What market surveillance checks

The legal basis is section 28 BFSG. Under it, the market surveillance authority checks a service when it has reason to believe the requirements are not met. It also reviews services without a specific trigger, using appropriate samples. For websites and mobile applications, it applies the requirements of Annex 1.

The technical criteria are not in the act itself but in the accompanying ordinance (BFSGV). For web content, it refers via the EN 301 549 standard to WCAG 2.1, conformance level AA. Typical test areas of these criteria are:

AreaWhat is requiredTypical mistake
Images and iconsMeaningful alternative textAlt text missing or just "image1.png"
ContrastText stands out sufficiently from the background (4.5:1 for normal text)Light grey text on a white background
Keyboard operationAll functions usable without a mouse, visible focusDialogs or dropdowns that only work with a mouse click
FormsLabelled fields, understandable error messagesPlaceholders instead of labels, errors marked only by red colour
Structure and languageClean headings, page language setHeadings chosen for looks only
Zoom and reflowContent stays usable when enlargedCut-off content on small screens

How an inspection comes about

There are two routes: tips and complaints that prompt the authority to act, and samples without a trigger. Specialist portals report that inspections started in 2026. That is an assessment from secondary sources; the statute is what counts for you.

For violations, the act provides for market surveillance measures (section 29 BFSG) and a fine framework: under section 37 (2) BFSG, an administrative offence can be punished with a fine of up to EUR 10,000, and in certain cases up to EUR 100,000. Which range applies depends on the specific violation. In addition, legal commentary discusses whether competitors may also send cease-and-desist letters under competition law.

What clients should do now

  1. Clarify coverage: Does the offering target consumers? Does the micro-enterprise exemption apply? Document the decision.
  2. Assess the current state: Automated tests find only part of the problems. Add manual testing, especially for keyboard operation and forms.
  3. Critical flows first: Ordering, booking and contact flows take priority over side pages.
  4. Mind the information duties: Besides the technical implementation, the BFSG requires certain information about the accessibility of the offering.
  5. Plan it in from the start for new builds: Accessibility belongs in the requirements specification, not in rework.

Accessibility is considerably cheaper when it is part of the requirements specification than when it is retrofitted after launch.

This statement is an assessment from a development perspective, not a legal quotation. The reason is technical: contrast, focus order, form labels and heading structure are basic decisions in the design and components of an application. Made early, they apply everywhere. Corrected late, many places have to be touched one by one. Anyone commissioning a web application should therefore fix the requirement before the start and bundle it with other obligations, such as those from the Cyber Resilience Act. For help assessing which obligations apply to your project, IT consulting can also support you.

Conclusion

The BFSG is no longer a side issue: it applies, it is enforced, and the technical benchmark is clearly defined. First check whether your offering is covered, then secure the flows through which consumers conclude contracts.

Share

Frequently asked questions

  • What matters is the consumer connection and the conclusion of contracts. Pure B2B offerings are not the target of the law. Pages that encourage consumers to conclude a paid contract may be covered. When in doubt, the individual case should be reviewed.

  • The act has applied since 28 June 2025. Since then, covered e-commerce services must be offered in an accessible way.

  • The BFSGV refers via the EN 301 549 standard to WCAG 2.1, conformance level AA for web content. For new builds, the additional criteria from WCAG 2.2 can be taken into account right away.

Author of this article

JB

Juljan Blischke

Co-Founder & Engineering

Certified application developer. Has been building web applications, APIs and internal tools for years.

This article is for general information only and does not replace individual legal, tax, or business advice. Prices, timelines, and assessments are non-binding estimates provided without guarantee.