WCAG 2.2 audit
- Assessment against WCAG 2.2 AA and EN 301 549
- Contrast, keyboard, screen readers, forms, focus
- Prioritised action plan with effort estimates
- Clear for decision-makers, concrete for developers
Accessible Software: Audit, Implementation, Compliance
Since June 2025, the German Accessibility Act (BFSG) requires accessible apps and web services, mirroring the European Accessibility Act. We audit your application against WCAG 2.2, retrofit what exists and build new software accessible from the start, pragmatic rather than paper-heavy.
Retrofit instead of rewrite
- Targeted fixes for the barriers found
- Web, desktop and mobile apps
- Usually possible without a rewrite
- Regression-safe implementation with tests
Build accessible from day one
- New applications follow WCAG 2.2 from the start
- Semantics, keyboard operation and focus management as standard
- Accessibility statement included
Anchor the knowledge in your team
- Training for developers and designers
- Testing tools in the development process
- Checklists for future releases
Accessibility is built in here, not bolted on
Our app platform Kinster has WCAG contrast checking firmly integrated: anyone designing an app there sees immediately whether colours and contrast meet the requirements. And our own website documents its status openly in the accessibility statement, held to the same standards we apply to client projects.
Frequently asked questions about accessibility
What does the German Accessibility Act (BFSG) require?
Since 28 June 2025, many consumer products and services must be accessible, including web shops, apps, banking and booking services. The benchmark for software is WCAG 2.2 and the European standard EN 301 549.
Does the BFSG apply to our company?
It primarily covers offerings aimed at consumers; micro-enterprises are exempt for services. Even without a direct obligation, public-sector clients have long required accessibility in tenders. We provide initial orientation but do not replace legal advice.
What happens in a WCAG audit?
We examine your application against WCAG 2.2 (level AA): contrast, keyboard operation, screen reader compatibility, forms, focus management and understandable error messages. You receive a prioritised action plan with effort estimates, not a hundred-page paper report.
Can existing applications be retrofitted?
Yes, in most cases without a rewrite. Many barriers come down to contrast, missing labels, keyboard traps and forms, and can be fixed in a targeted way. The audit shows what delivers quick impact and what needs structural work.
How does needful-apps handle accessibility itself?
Our website follows WCAG 2.2 AA, and our accessibility statement documents the current status openly. Our app platform Kinster has WCAG contrast checking built in, so accessible design does not depend on chance.