Developing an Accessibility Statement
Why provide an accessibility statement
Accessibility statements are important for several reasons:
- Show your users that you care about accessibility and about them
- Provide them with information about the accessibility of your content
- Demonstrate commitment to accessibility, and to social responsibility
In some situations, you may be required to provide an accessibility statement, such as public bodies in countries that implement the EU Web Accessibility Directive . The W3C list of Web Accessibility Laws & Policies can help you identify policies applicable to you.
What to include in an accessibility statement
Accessibility statements should contain at least the following:
- A commitment to accessibility for people with disabilities
- The accessibility standard applied, such as WCAG 2.1
- Contact information in case users encounter problems
It is also advisable to include the following information:
- Any known limitations, to avoid frustration of your users
- Measures taken by your organization to ensure accessibility
- Technical prerequisites, such as supported web browsers
- Environments in which the content has been tested to work
- References to applicable national or local laws and policies
Note that in some situations you may be required to provide particular content in your accessibility statements. For example, there are specific requirements for accessibility statements in relation to the EU Web Accessibility Directive .
How to write an accessibility statement
Accessibility statements are primarily for users of your content. Usually they will refer to accessibility statements when they encounter problems. Technical and jurisdictional language will likely lead to confusion and increase the frustration rather than help your users. It is important to write in simple language, and to provide information that is useful to the users, rather than use the language of developers and lawyers.
In particular, accessibility statements should explain functionality and known limitations in common terms. For example, rather than to say “WCAG Success Criterion 1.2.2 was not met”, it is better to say “videos do not have captions”. Accessibility statements are not technical assessments or declarations of conformity, though they ideally refer to such background to provide verification and increase credibility.
Where to put an accessibility statement
Accessibility statements should be easy to find. Linking them from several places, such as from the footer, help menu, sitemap, about page, and other prominent areas helps users to find them. Use consistent link names for your accessibility statements to help users recognize them. This includes link names across the content of your website and mobile applications, and across groups of related websites and mobile applications. For example, use the same link name on all web pages to refer to an accessibility statement for that website, and use that same link name to refer to the accessibility statement of the mobile application version of the website.
Examples of accessibility statements
The following examples of accessibility statements were created using this generator tool:
About this generator tool
This accessibility statement generator tool is designed for use in different contexts and jurisdictions. These situations can be so different that we cannot provide support for each one individually. For example, you may be subject to a particular organizational policy, quality assurance process, or law that requires you to provide certain information in your accessibility statement.
This generator tool allows you to enter different types of information to create accessibility statements for your particular situation. You can download the generated accessibility statement to further customize it for your own needs. You can also reuse the source code for this generator tool , for example to translate it or to customize it for your particular situation.
Generate an accessibility statementBack to Top