FAQ
FAQ – Answers to Common Questions About Digital Accessibility
This chapter addresses recurring questions from projects, training sessions, and audits. The answers help with typical everyday challenges and provide concrete guidance – especially for beginners, project managers, and technical teams.
What is the difference between BITV and WCAG?
The WCAG (Web Content Accessibility Guidelines) are international guidelines from the W3C. The BITV (Barrier-free Information Technology Ordinance) implements the EU Directive 2016/2102 into German law and references WCAG 2.1 as the minimum standard. WCAG is therefore the technical framework, while BITV is the legal implementation.
Which tools are suitable for manual testing?
For manual testing, these tools are commonly used:
- Keyboard navigation in the browser (Tab, Enter)
- Screen readers: NVDA (Windows), VoiceOver (macOS/iOS), TalkBack (Android)
- Accessibility checklists based on WCAG (e.g., from WAI, DIAAS, or mtc)
How do I test a mobile app for accessibility?
- With built-in screen readers like VoiceOver (iOS) or TalkBack (Android)
- Using Accessibility Scanner or integrated tools in Android Studio and Xcode
- Testing focus management, alternative texts, semantic structures, and gesture support
What should I do when design requirements conflict with accessibility?
- Early communication between design, development, and accessibility teams
- Suggest alternative visual solutions (e.g., contrast adjustments, focus indicators)
- Document decisions and compare them with success criteria (e.g., WCAG 1.4.3)
What requirements apply to PDFs?
- PDF documents must be tagged and have a proper reading order
- Alternative texts for images, labeled forms, correct heading structure
- Tools: PAC 2021, Adobe Acrobat Pro, axesPDF
When does the BFSG apply to my company?
The Accessibility Strengthening Act (BFSG) comes into effect on June 28, 2025. It affects many private providers of digital products and services. Micro-enterprises (<10 employees, <€2 million turnover) are exempt, provided they do not distribute systemically relevant products.
What does “partially accessible” mean in an accessibility statement?
It means that certain areas or functions of a website do not fully meet the requirements. These deviations must be identified and ideally accompanied by a plan for remediation.
How often should an accessibility statement be updated?
At least once a year or when significant changes are made to the website. The statement should also be revised after a comprehensive test run or relaunch.
What role does the target audience play in testing?
Involving real users with various disabilities is a central component of comprehensive accessibility testing. It reveals usage barriers that might not be detected in purely technical evaluations.
What are typical errors that are often overlooked?
- Missing or unclear labels for form fields
- Loss of focus in modal dialogs
- Controls that cannot be reached via keyboard
- Contrasts below WCAG thresholds
- Images without meaningful alternative text
Additional FAQs Welcome
FAQs thrive on active questions about the topic and will be gladly incorporated.