Imagine trying to operate your smartphone without being able to see the screen. This may sound challenging, but it is everyday life for many people. This is exactly what our two team leaders from the Public business unit experienced at the German Testing Night in Nuremberg on 11 March 2026. It made us rethink a lot of things we thought we knew.
The event focused entirely on digital accessibility in IT. The excellent host was the Federal Office for Migration and Refugees (BAMF), an authority that has already firmly integrated accessibility into its software processes. The highlight was the practical, interactive and impressive "Introduction to accessibility 80 in 80 minutes" world café tutorial.
The evening showed the following: Accessibility is not an abstract compliance issue, it can be experienced and implemented. It is often closer than expected.
Three points stand out in particular:
Practical insights: the workshop emphasized the importance of involving those affected and integrating accessibility into software processes from the outset, rather than as an afterthought.
Courage to use methods: Even with the right tools, it is possible to get started with accessibility testing, often faster than you might think.
Blind operation using the example of an iPhone: The experience with speech output at high speed impressively showed where there are still hurdles - and how much a well thought-out, inclusive design can achieve.
The BAMF uses a structured mix of automated and manual testing methods that are based on established standards such as the Web Content Accessibility Guidelines (WCAG) and the Barrier-free Information Technology Ordinance (BITV 2.0). Selected examples from practice:
Chrome Lighthouse: A quick initial check to get an overview of the accessibility status of a project.
Axe-Core: Use in code reviews and tests — a proven tool for automated accessibility testing.
Accessible PDFs: It is essential to create and check accessible documents, but this is often underestimated in practice. A structured Word document alone is not enough; exports must also be accessible.
Internal resources: The BAMF uses existing resources, such as BLUU (Barrier-free, Solution-oriented, User-centred, Universal), an internal framework that supports teams in the practical implementation of accessibility.
Automation as a lever: Many checking steps can be automated, saving time and creating space for the more complex manual checks that no tool can replace.
At the various stations of the World Café format, our team leaders were not only able to understand accessibility, but also experience it first-hand. The most important impressions:
After visiting the individual stations, all participants took the opportunity to share their experiences. It became clear that accessibility in software development is already common practice in many projects, while in others, it is becoming increasingly important and urgent as a result of the German Accessibility Improvement Act (BFSG).
The central conclusion of the evening was that dialog with those affected and the integration of accessibility right from the start are crucial. Starting early benefits users, the quality of the project and your own organisation. Accessibility is not optional. It is a legal requirement, a quality feature, and above all a question of attitude.
Would you like to integrate digital accessibility into your software projects?
Get in touch with us. We will support you from the initial check through to sustainable implementation.