Accessibility Statements for Public Bodies
For federal public bodies, Section 7 BITV 2.0 governs the accessibility statement. This duty does not arise from the BFSG effective date of 28 June 2025. For state public bodies, check the relevant state law.
What is an Accessibility Statement and Why is it Crucial for Digital Inclusion?
The accessibility statement informs users and stakeholders about the current state of accessibility and describes known barriers, the assessment method and contact routes:
Current status of accessibility of your website or app
Compliance with WCAG 2.1 and DIN EN 301 549 – fundamental standards for
- digital accessibility
Identification of barriers and planned improvement measures
- Feedback options for users with disabilities
Complaint procedures and enforcement mechanisms under the rules applicable to the public body
Basic Requirements for the Accessibility Statement: Transparency & Traceability
-
Objective Assessment: The statement must contain an actual assessment of the extent to which accessibility requirements are met.
-
Indication of Limitations: If certain areas are not accessibly designed, the reasons must be comprehensibly explained.
-
Easy Accessibility: The accessibility statement must be findable from the homepage and all subpages of a website.
-
Regular Updates: A review and, if necessary, adjustment must occur at least once a year.
Content Requirements of the Accessibility Statement: Complete Transparency and Traceability
To meet legal requirements, the accessibility statement must include several important contents:
-
Easy Findability: The statement must be directly accessible from the homepage as well as all subpages.
-
Accessible Format: It must be accessible to all users and, if necessary, also be available in a machine-readable format.
-
Transparent Information on Accessibility:
-
Listing of non-accessible content.
-
Justification why certain content is not fully accessible.
-
If available: References to accessible alternatives.
-
-
Proof of Assessment: It must be disclosed which method was used to check accessibility.
-
Feedback Option: Users must be offered an electronic contact option to report barriers or request information.
-
Information on the Arbitration Procedure:
-
Explanation of how the conflict resolution procedure works.
-
Link to the responsible arbitration body for further information.
-
What a useful statement provides
A statement names known barriers, describes the assessment and explains how people can request help or report a problem. It records the findings; publishing it does not remove the barriers.
Collect the test evidence first: the website testing guide explains the process, and the WCAG hub covers technical criteria. Use the statement generator to draft from documented findings. Before publication, review the requirements and contact routes applicable to your public body.
Stay Updated
Get accessibility tips and updates.
Our Top Posts:
- •BFSG Checklist: How to Implement Website Accessibility for Your Business
- •navable MCP v0.2: Dual-Engine Scanning (axe-core + Pa11y/HTMLCS) in One Scan
- •Automate Web Accessibility with AI | navable MCP
- •Install the navable Widget in WordPress: Step by Step
- •BFSG: Which Companies Are Affected? Scope and Exemptions
- •Free Accessibility Testing Directly in VS Code with axe DevTools
- •Accessibility for Agencies: How navable Speeds Up Your Audits
- •Accessible Navigation & Structure according to BFSG | Checklist & Solutions for Accessible Websites
- •Accessible text design: WCAG rules and recommendations
