Are you from the public sector?
Are you from the public sector?
Test the complete functionality of AccessGO risk-free for 7 days free of charge.
The accessibility statement is a central element for the legally compliant design of websites. It transparently informs visitors about the current state of accessibility, identifies existing limitations, and describes how users can report barriers. In this way, the accessibility statement contributes significantly to user orientation and compliance with legal requirements.
On this page, you will receive a practical overview of the structure, mandatory content, and implementation of the accessibility statement. You will learn which common errors and challenges to avoid and what to pay particular attention to for different website types and industries.
An accessibility statement follows a clear structure and is systematically organized to comply with legal requirements. Mandatory components include information on the scope, a description of the current state of accessibility, references to non-accessible content, contact options for feedback, and information on the enforcement procedure. The exact structure is based on requirements such as BITV 2.0, WCAG 2.1 AA, and BFSG.
There are differences between public and private providers: for public bodies, the accessibility statement is mandatory and more strictly regulated in terms of content. Private providers are subject to different obligations depending on the scope of application and legislation, but should also provide a transparent accessibility statement if they fall under the relevant regulations. The accessibility statement stands independently alongside other mandatory information such as imprint or privacy policy and must not be mixed with these.
| Component | Description and Differences |
|---|---|
| Scope | Which parts of the website or application the accessibility statement covers; mandatory for public bodies, dependent on scope for private providers |
| State of Accessibility | Indication of whether the website is partially, fully, or not accessible; recommended for both provider groups, mandatory for public bodies |
| Contact and Feedback | Option for users to report barriers; mandatory for public providers, depending on legislation for private providers |
| Enforcement Procedure | Information on the complaints body; mandatory for public bodies, optional for private providers |
| Distinction from Other Mandatory Information | Accessibility statement is independent and not part of imprint or privacy policy |
The accessibility statement pursues the central goal of creating transparency about the current state of accessibility of a website. It does not serve as an advertising tool, but as factual information for users, thereby fulfilling an essential information obligation. Users thus gain clarity about which content is accessible, which barriers exist, and how they can receive support if needed.
Another guiding principle is traceability through self-assessment: the information in the statement is based on a systematic review of the website and also serves as evidence to supervisory authorities. In this way, the accessibility statement is clearly distinguished from purely promotional statements, as it is based on verifiable facts and comprehensible documentation.
7 days unrestricted access. No payment details required.
For an effective accessibility statement, traceability and verifiability are central requirements. The statement must be designed so that third parties—such as testing bodies or users—can easily understand and verify the information. This applies both to the description of the current state of accessibility and to the documentation of the underlying assessment.
Success criteria include the complete and correct presentation of all legally required content according to WCAG 2.1 AA, BITV 2.0, and BFSG. An evaluation system indicates whether a website is fully, partially, or not accessible, and specifically identifies which areas are affected. Examples of evaluation categories are “fully accessible,” “partially accessible,” and “not accessible.” The evaluation must be comprehensibly justified and supported by specific examples or test reports.
| Success Criterion | Evaluation Category/Reference |
|---|---|
| Completeness of Information | All mandatory content according to WCAG, BITV 2.0, and BFSG included |
| Traceability | Verifiable information, transparent evaluation methodology |
| Correctness of Evaluation | Categories: fully, partially, not accessible; based on current reviews |
| Justification and Examples | Specific references to barriers or fulfilled requirements |
| Documentation of Self-Assessment | Reference to test reports or evaluation date |
The review of an accessibility statement can be conducted internally by the company itself or externally by specialized testing bodies and authorities. Internal review focuses on independent and continuous monitoring of content, with all changes and evaluations carefully documented. External audits are typically conducted by monitoring bodies or testing authorities, which provide an independent assessment of the information and verify compliance with legal requirements.
Both internal and external reviews require comprehensive documentation and evidence obligations. The results of the reviews must be recorded in a traceable manner and be available for submission if required. Incomplete or incorrect information in the accessibility statement can lead to objections, requests for correction, or further consequences from supervisory authorities.
| Internal Review | External Review |
|---|---|
| Self-responsible monitoring by the company | Independent assessment by testing bodies/authorities |
| Ongoing updating and documentation required | One-time or periodic audits, usually with test report |
| Flexibility in methodology, but evidence obligation | Standardized procedures and legal testing standards |
| Risk of internal misjudgment | Objective identification of deficiencies and obligations for correction |
The practical implementation of the accessibility statement begins with a structured step-by-step approach: first, all relevant information on the website’s accessibility is collected and evaluated. Next, the statement is drafted editorially, with attention to clear, understandable language and a well-organized structure. After completion, the statement is technically integrated into the website, ideally in a highly visible location, such as in the footer or via a dedicated menu item. Regular updating is essential to reflect changes in accessibility status promptly.
Depending on the website type, the requirements and options for technical and editorial implementation differ. For extensive corporate websites, a central, easily findable accessibility statement with detailed information is recommended. For smaller websites or web applications, the statement can be more compact but must still cover all mandatory content. In any case, it is important that the statement itself is designed to be accessible so that it is available to all users.
| Website Type | Implementation Recommendation |
|---|---|
| Corporate Website | Detailed statement, central placement in footer, regular updating |
| Web Application/Portal | Integration via dedicated menu, technical notes on barriers, focus on usability |
| Small Website/One-Pager | Compact statement, direct link, yet complete mandatory content |
| Shop System | Notice in customer area, adaptation to dynamic content, clear language |
Schedule a free consultation and speak with one of our experts.
The regulatory classification of the accessibility statement is based on various legal foundations. In Germany, the Accessibility Strengthening Act (BFSG) and the Accessible Information Technology Regulation (BITV 2.0) are particularly relevant, while at the European level, EU Directive 2016/2102 provides the framework. These regulations determine who is obliged to publish a statement, what content is required, and which deadlines must be met.
In Germany, public bodies in particular are obliged to publish an accessibility statement. The BFSG extends the obligation from 2025 to many private providers of digital products and services. Differences from the EU exist particularly in transitional arrangements and the specific implementation obligation. The accessibility statement must be clearly separated from other legal information obligations such as imprint or privacy policy, as it is subject to separate content and formal requirements.
| Regulation/Region | Obligated Parties and Deadlines |
|---|---|
| BITV 2.0 (Germany) | Public bodies, from 2025 also many private providers; deadlines depend on website type |
| BFSG (Germany) | Private providers of digital products and services from June 28, 2025 |
| EU Directive 2016/2102 | All public bodies in EU member states; national deadlines and transitional arrangements |
| Distinction from Other Obligations | Accessibility statement is an independent obligation, no overlap with imprint/privacy policy |
In the creation and maintenance of an accessibility statement, typical challenges repeatedly arise in practice. The most common errors include incomplete or inaccurate information on exceptions, unclear wording, or outdated information. Technical integration is also often neglected, for example when the statement is difficult to find or is not designed to be accessible itself. Particularly problematic are missing or non-functioning contact options, as users are then unable to provide feedback on barriers.
To avoid these sources of error, a structured approach is recommended: content should be regularly reviewed and updated, exceptions clearly and comprehensibly described, and the statement implemented in a technically and editorially accessible manner. Contact options must be clearly and easily accessible so that users can receive support if needed. A checklist for editorial and technical implementation can help identify and remedy common errors early.
| Source of Error | Recommended Approach |
|---|---|
| Unclear or Missing Information on Exceptions | Describe exceptions concretely and comprehensibly, justify comprehensibly |
| Outdated Information | Schedule regular review and updating of the statement |
| Inadequate Technical Integration | Place accessibility statement prominently and accessibly |
| Missing Contact Options | Provide contact method clearly, simply, and functionally |
| Unclear Wording | Use simple, precise, and understandable language |
The accessibility statement must contain certain mandatory content, which is defined by legal requirements and standards such as WCAG 2.1 AA and BITV 2.0. Mandatory information includes the scope, the current state of accessibility, a list of existing barriers, contact options for feedback, and information on the enforcement procedure. This content ensures compliance with legal requirements and creates transparency for users.
Beyond the minimum requirements, optional information can usefully supplement the accessibility statement. This includes, for example, information on planned improvements, further information on accessibility, or explanations of the testing procedure. Indicating the version status and the date of the last update also increases traceability. Examples of wording are: “This statement was last updated on [date].” or “The website is partially compliant with the requirements of BITV 2.0.”
| Mandatory Content | Optional Addition |
|---|---|
| Scope of Statement | Information on planned improvements |
| State of Accessibility | Explanation of testing procedure |
| List of Existing Barriers | Reference to further support services |
| Contact Options for Feedback | Indication of version status/last update |
| Information on Enforcement Procedure | Additional explanations on accessibility |
7 days unrestricted access. No payment details required.
The requirements for an accessibility statement vary significantly depending on the type of website and industry. Public bodies are subject to particularly strict requirements, while companies and associations must adapt their statements to the respective legal framework and the needs of their target groups. Industry-specific characteristics, such as complex interaction options in online shops or the high information density on portals, require a differentiated approach in the formulation and design of the statement.
For online shops, for example, it is important to clearly identify technical barriers in the ordering process, while information sites often place a stronger focus on readability and comprehensibility. Portals with many user groups must design their accessibility statement to be particularly broad and accessible. Associations and smaller organizations benefit from practical, compact statements that nevertheless cover all mandatory content. The need for adaptation is always based on the actual barriers and the respective target group.
| Website Type/Industry | Special Requirements for Accessibility Statement |
|---|---|
| Public Bodies | Comprehensive mandatory content, detailed description of exceptions, regular updating |
| Companies (e.g., Online Shop) | Information on technical barriers in shop process, understandable language, information on support |
| Associations/Non-Profits | Compact statement, focus on core functions, simple contact options |
| Information Portals | Broad target group approach, understandable list of barriers, clear navigation to statement |
An accessibility statement should be reviewed at least once a year and updated as needed. Additional updates are always required when the technical conditions of the website change or new legal requirements come into force. It is advisable to document each adjustment internally and to indicate the version status and the date of the last update in the statement.
The accessibility statement is a central tool for making the digital accessibility of your website transparent and for meeting legal requirements in a structured manner. It informs users about the current state of accessibility, identifies existing barriers, and provides ways to get in touch. A carefully prepared and regularly maintained statement contributes significantly to building trust and improving usability.
Essential elements include the complete presentation of all mandatory content, clear and understandable language, and continuous updating and documentation. Requirements and implementation options vary depending on website type and industry, but a structured approach greatly facilitates practical implementation.
Check your homepage with the AccessGO quick check.
Identify risks and barriers according to WCAG standards.
If an accessibility statement is missing or contains incorrect information, monitoring bodies may raise objections and demand corrections. In addition, users have the option to file complaints or report violations. Depending on the severity of the violation, further measures by the competent authorities may follow, such as publication of the deficiency or a request for correction.
If an accessibility statement is missing or contains incorrect information, monitoring bodies may raise objections and demand corrections. In addition, users have the option to file complaints or report violations. Depending on the severity of the violation, further measures by the competent authorities may follow, such as publication of the deficiency or a request for correction.
The accessibility statement must be available at least in the main language of the website. For international websites, it is recommended to provide the statement in additional languages used by the main target groups. Legal requirements may impose additional multilingual requirements depending on the country, particularly for public bodies or Europe-wide services.
The responsible department or a designated contact person within the company is usually responsible for the accessibility statement, often from IT, web editorial, or compliance. It is important that exceptions in the statement are formulated transparently and comprehensibly. For example, permissible wording would be: “Certain PDF documents are currently not accessible.” Inadmissible would be: “Some content may contain barriers.” Clarity and comprehensibility for users are paramount.
Exceptions in the accessibility statement must be described in sufficient detail so that users can precisely understand which areas or functions are not accessible. The description should identify specific content, formats, or technical limitations. For precise presentation, collaboration between IT, editorial, and possibly data protection is recommended to list all relevant aspects correctly and comprehensibly.
