Since the German Accessibility Enhancement Act (BFSG) came into force in June 2025, digital accessibility is no longer a voluntary measure for many German companies, but a legal obligation. For the public sector, BITV 2.0 imposes even more far-reaching requirements. And in medical technology, accessibility and usability engineering are increasingly merging into a common regulatory task.
The challenge: Traditional automated testing tools only detect around 20 to 40% of the actual barriers in software and web applications. Newer AI-supported approaches, especially multimodal large language models, are beginning to push this boundary: they can check semantic aspects that remain hidden from traditional tools. Nevertheless, anyone who takes accessibility seriously needs a well-thought-out testing approach that combines automated and AI-supported checks with manual expertise and assistive technologies./p>
At sepp.med, we combine our experience in software testing for regulated industries with specialized accessibility expertise. We not only test your software for technical compliance with WCAG 2.1/2.2 and EN 301 549, but also ensure that it is accessible to all user groups in practice.
✅ Regulatory complianceYou receive documented proof of your software’s compliance status – whether according to BFSG, BITV 2.0, EN 301 549, or industry-specific requirements. A solid foundation for audits, procurement procedures, and declarations of conformity.
✅ Risk minimization before market entryAccessibility issues that only become apparent after launch result in high rectification costs. Early testing according to the shift-left principle identifies problems before they become expensive.
✅ Practicality instead of mere checklist complianceAutomated scans alone are not enough. Our experts use screen readers, keyboard navigation, and assistive technologies to check whether your software works in real-world use, not just on paper.
✅ Industry-specific expertiseAccessibility in a government portal has different requirements than in a medical device or banking app. We are familiar with the respective regulatory frameworks and provide the appropriate level of testing depth.
✅ Integration into your existing processesAccessibility testing can be seamlessly integrated into agile sprints, CI/CD pipelines, and existing testing strategies. We help you anchor accessibility testing where it brings the greatest benefit.
✅ Our solution:We analyze your product in the context of the relevant regulations – BFSG, BITV 2.0, EN 301 549, WCAG 2.1/2.2, or industry-specific requirements such as IEC 62366 in medical technology. You will receive a clear classification of which requirements apply and what level of testing is appropriate.
✅ Our solution:Automated tools such as axe or Lighthouse only reliably check a fraction of the WCAG criteria. We supplement automated scans with manual expert testing using screen readers (e.g., NVDA, JAWS, VoiceOver), keyboard navigation, and contrast analysis. This allows us to uncover barriers that tools cannot find.
✅ Our solution:We help you to embed accessibility testing early on in the development process as an integral part of your sprint planning or CI/CD pipeline. To do this, we integrate automated tests (e.g., axe-core, Pa11y) directly into your build processes and train your teams to recognize typical barriers.
✅ Our solution:Our test reports document the level of compliance in a systematic and traceable manner. They are suitable as a basis for declarations of conformity in accordance with BFSG, declarations of accessibility in accordance with BITV 2.0, and as evidence in procurement procedures.
Fast, reproducible scans with established tools (e.g., axe-core, Pa11y, Lighthouse, WAVE) identify technical violations such as missing alternative texts, insufficient contrast, or incorrect ARIA attributes. Automated tests are particularly suitable for regression testing in the CI/CD pipeline.
Experienced accessibility testers check your application using keyboards, screen readers, and other assistive technologies. They evaluate what machines cannot evaluate: the logical focus order, the comprehensibility of error messages, the meaningfulness of alternative texts, and the consistency of navigation.
In addition to software and web interfaces, we also check PDF documents, Office templates, and CMS-generated content for accessibility – using tools such as PAC 2024 for PDF/UA compliance and manual structure checks.
Upon request, we can train your developers, testers, and UX designers in accessible design and testing. After all, long-term accessibility is not achieved through one-off audits, but through team expertise.
Multimodal AI models significantly extend the degree of automation beyond what is possible with traditional rule-based tools. They evaluate the semantics of user interfaces. We use AI-supported analysis where it offers the greatest leverage: as an intelligent supplement to automated scans and to prioritize findings for manual review.
Accessibility meets usability engineering in accordance with IEC 62366 and regulatory requirements in accordance with MDR. We test the user interfaces of medical devices, telemedicine platforms, and digital health applications (DiGA) in terms of accessibility, patient safety, and compliance with standards.
German public authorities must comply with BITV 2.0. Its requirements go beyond those of the BFSG. We check citizen portals, specialist procedures, and administrative documents according to the standards of the BIK-BITV test and provide support in preparing the legally required accessibility statement.
Banking apps, online portals, and payment terminals are among the core areas of the BFSG. We check critical user paths—from authentication to contract conclusion—for accessibility, while also taking into account the requirements for understandable language in financial information.
From web HMIs in production to ticketing apps in public transport to infotainment systems in vehicles: we also test for accessibility where traditional web accessibility tests reach their limits—under real-world conditions.
Accessibility testing checks whether digital products – websites, apps, software – can be used by people with disabilities. It combines technical compliance testing (against standards such as WCAG and EN 301 549) with validation using assistive technologies such as screen readers and keyboard navigation.
The central technical standard in Europe is EN 301 549, which refers to WCAG 2.1 Level AA for web content. The Accessibility Enhancement Act (BFSG) references this standard for the private sector, while BITV 2.0 does so for the public sector. Internationally, the ADA (USA), Section 508, and industry-specific standards also play a role.
No. Experience shows that traditional automated tools only detect around 20 to 40% of barriers. AI-supported approaches can significantly increase this percentage for certain criteria, especially where semantic understanding is required. However, they do not replace human expertise: in particular, the evaluation of complex interaction processes, validation in real-world use with assistive technologies, and context-dependent judgments remain tasks for experienced accessibility testers. The optimal approach combines classic automated scans, AI-supported analysis, and manual expert review.
Most effective as an integral part of every sprint: automated checks in the CI/CD pipeline immediately catch technical setbacks. Manual tests are performed before major releases or when new features are added. In addition, an accessibility backlog can be maintained, which prioritizes findings and feeds into sprint planning.
Studies and practical experience show that subsequent corrections cost many times more than early consideration. Those who only address accessibility after launch risk high development costs as well as legal consequences. The BFSG provides for fines of up to €100,000 and sales bans.
Firstname:
Lastname:
E-Mail Address:
Phone:
Subject:
Your message:
Yes, I consent to my personal data being collected and stored electronically. My data will only be used for the purpose of responding to my inquiry. I have taken note of the privacy policy.
You are currently viewing a placeholder content from OpenStreetMap. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
You need to load content from hCaptcha to submit the form. Please note that doing so will share data with third-party providers.
You are currently viewing a placeholder content from Hubspot Embedded Content. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
You are currently viewing a placeholder content from HubSpot. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
You are currently viewing a placeholder content from Hubspot Meetings. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
You are currently viewing a placeholder content from Google Maps. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.