Accessibility is not a widget
Since June 2025, Germany's BFSG has applied to many shops and digital services. Why overlay widgets are not enough, what I check first in projects, and why understandable content often does more than an additional tool.
Since June 28, 2025, accessibility is no longer just a good intention for parts of the private sector. The Barrierefreiheitsstärkungsgesetz (BFSG, Germany's accessibility act) covers, among other things, e-commerce services for consumers: typically online shops, bookings and similar ordering flows. In parallel, notary offices, medical practices and other businesses are asking for websites that explain services clearly and can be used without a mouse.
Accessibility has been on my mind in projects for some time. What the blog lacked so far was the practical view: what I actually look at first in projects, and why an "accessibility widget" bolted on afterwards is rarely the answer.
What the law covers, and what it does not
Briefly and without legal advice: the BFSG mainly covers offerings through which consumers order something, book something or conclude a contract online. Purely informational sites or purely internal B2B tools are often not covered. For services there is also an exemption for micro-enterprises (fewer than ten employees and at most two million euros in annual turnover or balance sheet total).
Whether your shop or your booking system falls under it cannot be derived from a blog headline. That gets settled on the concrete case, with a chamber, a consultancy or an internal review. As a developer I therefore plan the scope in early, instead of laying an overlay over it at the end.
Technically, much of it follows well-known web standards: perceivable, operable, understandable, robust. In practice that is often WCAG 2.1 AA or the corresponding standards for ICT. For you as an operator that means less "buying a certificate" and more: navigation, forms, error states and content have to work with a keyboard and assistive technology too.
Why widgets alone are not enough
A button that toggles contrast or reads text aloud looks like the quick fix on paper. In practice I check something else: Can I get through the ordering process with the keyboard alone? Are error messages at the field understandable? Do images have meaningful alternative texts? Are headings and labels set so that a screen reader can follow the flow?
If these basics are missing, a widget covers up the gaps at best. Sometimes it even makes things harder to use, because it brings its own layers, focus traps or additional scripts. Accessibility lives in markup, structure and content, not in a third-party script that you "switch on".
The same goes for the obligation to provide the information on accessibility in an accessible way itself. A statement that only exists as an inaccessible PDF or does not match the actual state of the site helps nobody, neither users nor a later audit.
What I check first in projects
In client projects I rarely start with the full WCAG checklist. I go through the places where people fail or drop off:
- Entry and navigation: skip link, sensible order, visible focus, no mouse-only controls.
- Forms and ordering flow: labels, error messages, required fields, confirmation steps. This is where it is decided whether a shop is accessible under the BFSG in a way that actually works in practice.
- Content and language: clear headings, readable paragraphs, explained technical terms. For a notary office project I planned for supplementary versions in Leichte Sprache (easy-to-read German) and an accessibility statement; the service pages were meant to work for first contacts as well as for experienced clients.
- Media and contrast: alternative texts, sufficient contrast, reduced motion when
prefers-reduced-motionis set. - Migration: existing addresses have to keep leading somewhere. For the notary office website that was 28 known URLs, every redirect checked individually. Accessibility without findability is half done.
I choose technology so that these points do not fight the framework. For the website mentioned, for example, Astro with my own hosting in a container: little unnecessary JavaScript on content pages, clear HTML structure, operations under control. That is not a cure-all, but it is a stack that does not actively make accessible pages harder.
Understandability is part of accessibility
Accessibility does not end at contrast values. Anyone preparing a notarization, looking for a treatment or ordering a product needs texts that explain the next step. On the industry page for notary offices exactly that is the focus: factual information instead of advertising volume, contact channels with as few services involved as possible, taking different levels of prior knowledge into account.
Leichte Sprache is not a decorative feature here. It is a deliberate second version for people who cannot read technical language, or only with effort. Whether and to what extent it makes sense depends on the audience and the brief, but the question belongs in planning, not in the hotfix after launch.
The same pattern applies to shops: product information, shipping costs and error messages have to be in the right place. If you only polish the design and leave the checkout unclear, you build a pretty hurdle.
What you can do next
If you run a shop or a bookable website, an honest pass with the keyboard and, if possible, a screen reader is worth it. Note where the focus disappears, where errors are unclear and where content only exists as an image. In parallel, clarify the legal scope; I am no substitute for advice here.
If you are planning a relaunch or a new ordering flow, we build accessibility and data protection in from the start, not as an appendix. On danielgtmn.com you will find the process and the industry pages; for a short first conversation, a message to hello@danielgtmn.com is enough.
Note: The legal assessments in this text reflect the state of my knowledge and are not a substitute for legal advice.
Common questions
- Is an accessibility widget enough for an accessible website?
- An accessibility widget alone is not enough. If basics such as keyboard operation, understandable error messages, meaningful alternative texts and properly set headings and labels are missing, a widget covers up the gaps at best. Sometimes it even makes things harder to use, because it brings its own layers, focus traps or additional scripts.
- Who does the BFSG apply to?
- The BFSG mainly covers offerings through which consumers order something, book something or conclude a contract online. Purely informational sites or purely internal B2B tools are often not covered, and for services there is an exemption for micro-enterprises. Whether your shop or booking system falls under it is something you settle on the concrete case, and this is not a substitute for legal advice.
- What should I check first for the accessibility of a website?
- I first go through the places where people fail or drop off: entry and navigation, forms and ordering flow, content and language, media and contrast and, in a migration, the existing addresses. To begin with, an honest pass with the keyboard and, if possible, a screen reader is worth it.
- Is Leichte Sprache part of accessibility?
- Understandability is part of accessibility. Leichte Sprache (easy-to-read German) is a deliberate second version for people who cannot read technical language, or only with effort. Whether and to what extent it makes sense depends on the audience and the brief, but the question belongs in planning.