The Barrierefreiheitsstärkungsgesetz (BFSG), Germany's accessibility act, has applied since 28 June 2025, and some vendors advertise “accessibility by plugin”. The short version: often it doesn't affect you at all – and if it does, no plugin helps, but a cleanly built website does.
Since when does the BFSG apply – and to whom?
The BFSG implements EU Directive 2019/882, the European Accessibility Act, and has applied since 28 June 2025. It protects consumers. For websites, “e-commerce services” matter: offerings through which consumers conclude a contract online – an online shop, for example.
Who it doesn't affect
- Micro-enterprises with fewer than ten employees and an annual turnover or balance sheet total of at most two million euros – even with an online shop (section 3(3) BFSG).
- Purely business-to-business offerings: if you sell exclusively to other businesses, you're not covered.
- Pure information websites where no contract is concluded. Borderline cases such as a form for specific quote requests are a grey area – have them checked if in doubt.
Who it does affect – and what then applies
If you're not a micro-enterprise and sell to consumers online or make things bookable, your offering has to be accessible: “perceivable, operable, understandable and robust”. Auditors orient themselves on the WCAG, level AA, and the European standard EN 301 549. With intent or negligence, fines of up to 100,000 euros are possible – no reason to panic, but also no reason to sit the topic out.
Overlay plugins: why the shortcut doesn't hold
An overlay is a third-party script on top of your page, promising to repair errors automatically. But the law asks for your offering itself to be accessible. The professional community sees this consistently:
- In the Overlay Fact Sheet ↗, more than a thousand signatories state that an overlay alone cannot achieve full compliance.
- The federal and state monitoring bodies ↗ (in German) write in March 2025: “Overlay-Tools können Funktionen von Hilfstechnologien nicht ersetzen” – overlay tools cannot replace the functions of assistive technologies.
- In the US, the trade regulator FTC approved a final settlement of one million dollars in April 2025 with a vendor whose promise of automatic WCAG compliance it considered misleading (FTC ↗).
An overlay also loads scripts from a third-party server – the opposite of what this website stands for: no third-party scripts, no cookies, no cookie banner.
What helps instead: semantic HTML and clean contrast
Accessibility is built in, not glued on:
- real headings, lists, buttons and links, labelled form fields
- alternative text for images that say something
- contrast: normal text at least 4.5:1, large text and controls at least 3:1
- a visible keyboard focus, the whole page operable with Tab
- the page language in the HTML, text that can be enlarged to 200 percent
A clean form field looks like any makeshift solution – keyboard, screen reader and autofill understand it right away:
<label for="email">Email</label>
<input id="email" name="email" type="email" autocomplete="email" required>
<button type="submit">Send enquiry</button>That costs hardly any extra effort when building. On this website, a test suite checks some basics automatically – that doesn't replace a test with a real keyboard and a real screen reader.
Five questions before you spend money
- Do I sell or book online to consumers – or am I a micro-enterprise anyway?
- Are headings, forms and controls marked up cleanly?
- Does the text have enough contrast everywhere – and has anyone measured it?
- Can everything be operated with the keyboard, including menu and form?
- Does a vendor promise me “accessibility by plugin”? Then ask for an audit report, and for which scripts it loads from which server.
Where does your website stand, and are you affected at all? We'll clarify that in a first call. More about my work: Web design & relaunch.
Sources and status
Status: October 2026. This is not legal advice – whether your offering falls under the BFSG depends on your individual case; if in doubt, ask a lawyer.
- The BFSG in full ↗ (in German): sections 1 to 3 and 37
- Ordinance to the BFSG ↗ (in German): requirements for websites
- Assessment of the monitoring bodies on overlay tools ↗ (in German, status March 2025)
- Overlay Fact Sheet ↗
- FTC on an overlay vendor ↗