Simplify Data Logo
  • Services
      • App Development
      • Web Development
          • Wordpress Development
          • Wordpress Support
          • Accessibility
      • Software Development
      • IT Consulting SME
          • Legacy modernisation
      • Business Analytics
          • Power BI
          • Metabase
      • Artificial Intelligence
      • SEO & AI visibility
      • Maintenance & Support
  • Managed Services
      • Zero-Trust Networking VPN
      • Managed email & groupware
  • Products
      • QRFlow
      • WooCommerce Interface
      • Open Source Projects
  • About us
      • Career
  • Blog
  • Contact
Web Development

BFSG after 17 months: typical defects, market surveillance and how an audit works

Simplify Data Team
November 16, 2026
5 Min. Read
BFSG after 17 months: typical defects, market surveillance and how an audit works
Simplify Data
Simplify Data GmbH
www.simplify-data.de
BFSG after 17 months: typical defects, market surveillance and how an audit works

Simplify Data Team • November 16, 2026 • 5 min Lesezeit

The German Accessibility Strengthening Act (BFSG) has applied since 28 June 2025. About 17 months have passed, and practice shows where websites and online shops fail most often: contrast, missing alternative texts, unlabelled forms, menus that cannot be used with a keyboard, and a missing accessibility statement. This article covers the typical defects together with their fixes, explains market surveillance and fines, and describes how an audit works (as of November 2026). If you first want to know whether the law applies to your offering, the basics are in our article "BFSG: What applies to websites and online shops now".

Please note: this article is not legal advice. Whether an exemption, for example for micro-enterprises, applies depends on headcount, turnover and balance-sheet total.

The most common defects in practice

The technical yardstick is the European standard EN 301 549, which refers to WCAG for web content, usually at conformance level AA. If you are building something new, take WCAG 2.2 into account from the start. Many findings can be found with automated tools, others only by hand.

Defect Typical example Fix
Insufficient contrast Light grey text on white, contrast below 4.5:1 Measure colour values and adjust them in the design system
Missing alternative texts Product images without a description Maintain alt texts in the CMS, mark decorative images as empty
Forms without labels Placeholder text instead of a label in login or checkout A real label per field, error messages at the field
Empty links and buttons Icon button without a name Visible text or a meaningful aria-label
Invisible focus Focus outline removed via CSS Define a visible focus style
No keyboard operation Mega menu, slider or cookie banner usable only with a mouse Ensure operation with Tab, Enter and Escape
Unstructured PDFs Download straight from Word without tags Core content as HTML, PDF only in addition and tagged

Example: online shop

In checkout, users often fail on details: error messages appear only as a red border, required fields are marked by colour alone, and the cart drawer does not trap keyboard focus. A few changes fix this, for example error text right at the field, a "required" hint in the label and a dialog that manages focus correctly and closes with Escape.

Example: WordPress site

With WordPress the causes often lie in the theme or page builder: headings are chosen for font size rather than structure, sliders flash without a pause, and plugins deliver forms without labels. A theme with clean markup, an editorial checklist for alt texts and a review of the plugins in use all help.

The accessibility statement: the quickest formal point

One of the information duties is the accessibility statement. It should be linked in the footer, describe the state of implementation, name known limitations and include a contact for feedback. A missing or outdated statement is a defect that can be spotted without technical knowledge, and it is just as quick to fix.

Market surveillance and fines

The body responsible for oversight is the market surveillance authority of the German states for the accessibility of products and services (MLBF), based in Magdeburg. A review can be triggered by spot checks, complaints from users or tips from recognised associations.

How a procedure unfolds

The procedure is staged. A request for information usually comes first, then the review and a deadline for rectification. Only after that come orders and, where applicable, fines. An immediate maximum fine is not the normal case in practice.

Fine range

Under Section 37 BFSG, fines of up to EUR 100,000 are possible, for example if a service is not offered in an accessible way or the required information is missing. A lower range applies to breaches of information and reporting duties. The authority may also restrict or prohibit the offering. Actual amounts depend on the individual case.

What an audit should deliver

A serious audit is more than an automated scan. It combines tools, manual testing and documentation of the results.

  1. Define the scope: which domains, page types, PDFs and which checkout are included?
  2. Automated scan with a sample of the most important user journeys.
  3. Manual testing: keyboard, focus, forms, contrast, alternative texts, screen-reader spot checks.
  4. Report with reproducible findings, priority and a suggested fix.
  5. Accessibility statement: create or update it.
  6. Retest after implementation.

What drives the cost

There is no flat price. Cost drivers are the number of page types and components, the complexity of checkout and customer area, the volume of PDFs and media, whether retests are included, and the state of the source code. It is usually cheaper to build accessibility into design and CMS from the beginning than to audit afterwards.

Checklist

  1. Link the accessibility statement in the footer and keep it current.
  2. Measure the contrast of your corporate colours instead of estimating it.
  3. Give every form field a real label.
  4. Make menus, sliders and cookie banners operable and closable by keyboard.
  5. Maintain alt texts editorially and mark decorative images as empty.
  6. Offer core content as HTML, PDFs only in addition and tagged.
  7. Test again after every relaunch and major rebuild.

How Simplify Data can help

We review and build websites and WordPress sites to WCAG AA standard and help write the statement. We do not provide the legal assessment of whether you are affected. More: accessibility, web development and WordPress development. To talk it through: get in touch.

Sources

  • Barrierefreiheitsstärkungsgesetz (BFSG), statute text (German)
  • Market surveillance authority of the German states for accessibility (MLBF)
  • Bundesfachstelle Barrierefreiheit
  • W3C: Web Content Accessibility Guidelines (WCAG) 2.2

This article is for general information only and is not legal advice; for your specific case, please consult a lawyer.

© 2026 Simplify Data GmbH www.simplify-data.de
Back to Blog

Table of Contents

  • 1.The most common defects in practice
  • –Example: online shop
  • –Example: WordPress site
  • 2.The accessibility statement: the quickest formal point
  • 3.Market surveillance and fines
  • –How a procedure unfolds
  • –Fine range
  • 4.What an audit should deliver
  • –What drives the cost
  • 5.Checklist
  • 6.How Simplify Data can help
  • 7.Sources

Actions

Our services
  • App Development
  • Web Development
  • Software Development
  • IT Consulting SME
  • Business Analytics
  • Artificial Intelligence
  • SEO & AI visibility
  • Maintenance & Support
  • IT services Kiel & Hamburg
Service & Legal
  • Legal notice
  • Privacy policy
Contact
  • Simplify Data GmbH
  • Königsweg 48, 24114 Kiel
  • Phone: 0431 705 770 24
  • Email: info@simplify-data.de

Copyright © 2026 Simplify Data GmbH