Accessible customer support: what § 12 BFSGV requires
Hotline, email, contact form or chat: what § 12 No. 4 BFSGV requires of support services and how to make accessibility answers and contact channels work.
The German Accessibility Strengthening Act transposes the European Accessibility Act into national law and, since June 2025, affects many digital consumer-facing services — online shops, booking flows, customer accounts, apps and certain services. The articles in this category clarify who falls within scope, which exemptions exist for micro-enterprises, which deadlines and transitional rules apply and what the required accessibility statement has to contain. We also describe how to take stock, the role of market surveillance, how to handle complaints and how requirements can be built into existing development and editorial processes without bringing operations to a halt. We also describe how to estimate effort realistically: which findings occur in almost every project, and which require a genuine rework of the interface?
On this page you will find all posts on the topic “German Accessibility Act”. The newest posts are at the top.
Below each title there is a short text about it. Click on a post. Then you can read the whole text.
Above the list you also see the other topics. At the bottom, a link takes you back to all posts.
Hotline, email, contact form or chat: what § 12 No. 4 BFSGV requires of support services and how to make accessibility answers and contact channels work.
Section 1(4) BFSG exempts five types of content. How to split a grown document stock - and how the exemption quietly comes to an end.
The duty does not end at acceptance. Which events trigger a re-test, which sample size holds up and how long the evidence has to stay on file.
German health app rules ask about accessibility in one line, the Accessibility Act measures it. How both duties fit together and what to test before filing.
Paid online courses fall under the BFSG, universities under BITV 2.0. How to make the learning journey from booking to certificate genuinely accessible.
Booking calendars, chat widgets and payment iframes are third-party code, yet BFSG duties stay with the operator. Evidence, testing and fallback routes.
E-books are a separate BFSG category: ten extra duties from Section 18 of the ordinance, EPUB Accessibility 1.1, metadata, testing and a backlist plan.
Section 17 BFSG is no free pass but a burden of proof: how to calculate, document and notify the Annex 4 assessment and keep it on file for five years.
ATMs, ticket and check-in machines fall under the BFSG. What applies to existing terminals until 2040 and why the accompanying service gets no grace period.
Cookie banners are the first interaction and fall under the BFSG. Where consent banners fail WCAG 2.2 and how to make them accessible and compliant.
Accessibility overlays promise one-click BFSG compliance but only change the surface. Why studies, the DBSV and authorities reject them and what truly works.
What a WCAG 2.2 audit costs in 2026: prices by scope, sampling versus full audit, monitoring, the BFSG fine ceiling, conversion ROI and funding at a glance.
What BFSG Annex 3 requires for an accessibility statement and what the EU model adds: conformance status, known barriers and a feedback mechanism.
How the BFSG is enforced: market surveillance, association lawsuits, defect reports, deadlines and statutory measures. Explained factually, with an action plan.