BITV and BFSG Accessibility Readiness Guide
BITV and BFSG readiness planning connects German public-sector and product-service accessibility work with technical website signals.
This guide is for general accessibility-readiness planning. It is not legal advice, a certification, or a substitute for manual accessibility and compliance review.
Who this may apply to
- German public-sector websites and services
- Digital products and services preparing for BFSG-related review
- Teams aligning accessibility remediation with European expectations
- Vendors supporting German public or regulated digital platforms
WCAG relationship
German accessibility requirements commonly connect to WCAG-aligned technical criteria through European standards and public-sector rules. Scope and process need separate review.
What the readiness check can surface
- Heading, landmark, and content-structure readiness signals
- Form-label and error-message issues
- Keyboard, focus, and skip-link readiness gaps
- Image alternative and link-purpose issues
- Contrast and mobile interaction signals
What still needs manual review
- Whether BITV, BFSG, or procurement expectations apply
- Task-based assistive-technology testing
- Documents, media, and third-party tool review
- Statement, reporting, and governance requirements
Common readiness issues
Forms that do not explain required inputs or errors
Navigation and overlays that need keyboard review
Service content without clear structure or link purpose
Low-contrast controls, banners, or status messages
Responsive layouts that obscure important actions
Official sources
FAQ
How do BITV and BFSG relate to website checks?
They connect German accessibility expectations with technical and service-readiness work. Website checks can help identify likely remediation priorities.
Does WARC decide which German rule applies?
No. WARC surfaces readiness signals only. Scope and process should be reviewed with appropriate internal or external expertise.
Why include WCAG-aligned checks?
WCAG-aligned checks provide a practical technical baseline for many structure, form, keyboard, contrast, and mobile issues.
What needs manual review?
Manual review should cover full journeys, assistive technology, documents, service context, and governance requirements.
Related standards
Start with the Website Accessibility Readiness Check
Scan a public URL to find practical accessibility, usability, forms, navigation, and mobile interaction signals before planning manual review.
Run the Website Accessibility Readiness Check