Once you have created an accessible textbook, you should provide an accessibility statement. While an accessibility statement is not required, it can be an important and useful addition to a resource for which you have worked to make accessible. This section will outline guidelines and recommendations about what to include in an accessibility statement and who the accessibility statement is for.

What is an accessibility statement?

An accessibility statement acts as resource for those who have questions about the accessibility features of your resource. It should provide an overview of accessibility features and contact information in case there are any problems.

Who are you doing this for?

When writing an accessibility statement, it is important to keep in mind who the statement is for. This will guide the language you use and the type of information you include. Ultimately, the accessibility statement is for people who have disabilities or are having problems accessing your resource for whatever reason.

Hassell Inclusion’s blog post on “How to write an effective Accessibility Statement” notes that many accessibility statements ignore who will be accessing the accessibility statement or why. Instead, they make statements about the organization’s commitment to accessibility, combined with technical jargon related to web development, accessibility, and accessibility legislation. Rather than acting as a helpful resource for people with disabilities, this type of accessibility statement “read[s] like a combination of a sales pitch on how socially responsible the organization is, a technology manual, and some legal small print.”^[1]

Chances are, the only time people will be interested in an accessibility statement is when they have trouble accessing content in the textbook or resource. Therefore, make sure your accessibility statement provides the information readers are looking for.

What do you need to do?

Here are tips for writing a useful accessibility statement:

• Use clear and simple language, avoiding jargon and technical terms
• Include information about how people can personalize their experience. This might include information about:
  • features of the platform used for the resource (e.g., if a book is in Pressbooks, mention the ability of users to increase the font size in the web book)
  • the ability to change browser settings
  • a link to each available file format
  • assistive technologies
• Outline specific accessibility features and how to use them when relevant
• Do not make false claims or ignore known accessibility issues. Be as transparent and open about accessibility barriers as possible. This means:
  • describing what is being done to fix the problem and a timeline
  • providing any temporary workarounds
• Include information about who is responsible for the accessibility of the content and their contact information so people can submit issues, suggestions, or complaints related to accessibility.
• Describe the organization’s accessibility policy, and the work that has been done to make the resource accessible. Here, you can provide information like:
  • accessibility guidelines you are following (e.g., WCAG 2.0)
  • any federal, provincial, or state legislation you are conforming to
  • any user testing you performed^[2]

Here is a sample accessibility statement that you can adapt for your own purposes:

Additional resources

For more information, refer to the following resources:

• Web Content Accessibility Guidelines: Conformance Claims
• Nomensa: How to Write an Accessibility Statement
• Access 8878’s Accessibility Statement

For sample accessibility statements, refer to the following pages:

• B.C. Government Website’s Accessibility Statement
• Hassell Inclusion’s Accessibility Statement