Accessibility is mandatory from 2025 (BFSG). What WCAG 2.2 AA means in practice — and how we make sure of it in the build.
Category · Frontend & UI
Mandatory from 2025.
Under the German Accessibility Strengthening Act (BFSG), many digital products must be accessible from 28 June 2025 — not voluntarily, but by law. The benchmark is essentially WCAG 2.2 at conformance level AA.
In practice that means: sufficient colour contrast, full keyboard operability, sensible structure for screen readers, labelled forms, a visible focus.
How we secure it in the build.
Accessibility isn't an afterthought for us — it's part of the Definition of Done. Semantic HTML instead of div deserts, accessibility checks (such as axe) in the CI pipeline, contrast tokens in the design system, and tests with real keyboard and screen-reader operation.
What tools won't do for you.
Depending on the study, automated checks catch only around a third of the issues. Meaningful alt text, a logical reading order and operable components don't come from a linter — they need decisions in design and a manual check. Leave it to the end and you'll pay extra.