European Accessibility Act and WCAG 2.1 AA
Since 28 June 2025, many private companies in Germany must make consumer-facing digital services accessible under the BFSG (implementation of the European Accessibility Act). The benchmark is WCAG 2.1 Level AA—also reflected in German BITV 2.0 for public-sector contexts. Non-compliance can lead to warnings and fines. New systems should be accessible at launch; legacy platforms often need a phased remediation plan.
Accessibility means your software works for people with visual, motor, hearing or cognitive impairments—roughly 13 million people in Germany alone. We support audits, implementation and CI integration. Related compliance topics: EU AI Act consulting and GDPR-compliant software development.
Our accessibility services
Accessibility audit (WCAG / BITV)
Systematic review with axe-core and Lighthouse, manual screen reader testing (NVDA, VoiceOver), keyboard-only navigation and contrast checks. You receive a prioritised report with effort estimates per category.
Inclusive development
We build new applications accessible from the start—based on our custom software development—or remediate findings in existing React/Next.js code: semantic HTML, ARIA, focus management and CI checks via DevOps pipelines.
Accessibility statement & VPAT
We prepare the technical basis for your public accessibility statement—conformance status, known exceptions and timelines—aligned with BFSG and BITV expectations.
Assistive technology testing
Automated scans miss most focus-order and live-region issues in SPAs. We add manual passes—embedded in our QA and testing practice—before release.
Accessibility audit
WCAG 2.1 AA review with axe-core, screen readers and contrast analysis—prioritised remediation roadmap included.
Accessible development
Semantic HTML, ARIA and keyboard navigation for React, Next.js and other modern stacks.
CI/CD integration
axe-core in your pipeline—accessibility regressions fail the build early.
Compliance documentation
Accessibility statements and VPAT-style documentation for BFSG and BITV contexts.
Frequently asked questions
FAQ: Accessible software development & WCAG
BFSG, WCAG and legal scope
What is the BFSG and who does it affect?
Germany’s Barrierefreiheitsstärkungsgesetz (BFSG) implements the European Accessibility Act (EAA). Since 28 June 2025 it applies to many B2C digital products and services—especially online shops, banking apps, telecom services and e-commerce platforms. Existing systems may have transition periods; new systems should comply from day one. We assess whether and how your software is in scope.
What does WCAG 2.1 AA mean for developers?
WCAG 2.1 Level AA is the reference standard for accessible web applications. It covers perceivable content (contrast, alt text, captions), operable interfaces (keyboard access, focus visibility), understandable UI (labels, error messages) and robust markup (semantic HTML, correct ARIA, assistive-tech compatibility). For React/Next.js that means semantic elements, focus management and automated checks in CI.
Who is affected by EU accessibility rules?
Beyond public-sector BITV requirements, private providers of consumer-facing digital services in the EU increasingly face accessibility obligations—online retail, financial services, transport apps and similar. WCAG 2.1 AA is the practical benchmark for audits and statements of conformance.
Implementation, audits and cost
How do you implement accessibility in React applications?
We work in layers: semantic HTML instead of div-only UI, purposeful ARIA (labels, live regions, describedby), keyboard navigation and focus traps in modals, and sufficient colour contrast. axe-core and Lighthouse run in CI so regressions surface in the build—not only before release. Manual NVDA and VoiceOver passes catch issues tools miss.
What does an accessibility audit and remediation cost?
A WCAG 2.1 AA audit for a mid-sized web application typically costs €3,000–€8,000 (automated scans, screen reader review, keyboard testing, prioritised findings). Remediation of legacy apps can run €20,000–€80,000 depending on debt. Building accessibility in from the start adds roughly 10–20% versus a non-accessible baseline but avoids expensive retrofitting.
Can accessibility be added later?
Yes, but retrofitting usually costs several times more than baking it into design and development. We audit existing systems, prioritise by compliance risk and effort, and plan incremental fixes without blocking releases.
Which tools do you use for automated checks?
axe DevTools, WAVE and Lighthouse catch a subset of issues (often 30–40%). Full compliance still needs manual screen reader and keyboard-only testing—we combine both and document results for your accessibility statement.
Accessibility as compliance and competitive edge
Accessible software reduces legal risk and opens markets. Good semantic structure also improves SEO and performance for all users—not only assistive technology users.
- ✓WCAG 2.1 AA: contrast, keyboard use, screen reader structure, scalable text
- ✓Automated plus manual testing before each release
- ✓Made in Germany—development and support from Ostfriesland
Request a free initial check of your key user journeys—we will outline scope, risk and next steps.
