Skip to main content

30 steps to a more accessible website

Step 30: Creating an accessibility statement

If you've implemented any of the tips in this series, create an accessibility statement that lists the accessibility features of your site.

Who benefits?

  1. Bill benefits. He makes extensive use of the keyboard for navigation, and he would use your accesskey keyboard shortcuts if he knew what they were. Unfortunately, Mozilla does not announce them or make them visible in any way, so you'll need to list them yourself.
  2. Many other users benefit, by learning how to use their own software better. For instance, Lillian did not know that she could set her default text size in her browser until someone told her how to do it; now she can more easily read your site (that is, if you use relative font sizes). Netscape and Mozilla users may not know that they can turn on the Site Navigation Bar to take advantage of your LINK-based navigation aids. ("View" menu, "Show/hide", "Site Navigation Bar", "Show Only AS Needed". Unfortunately, this feature was pulled from Mozilla 1.0 final at the last minute, but it's back in 1.1.)
  3. Fellow web designers benefit, by learning more about accessibility and seeing that you've taken the time to implement these tips.

« Step 29: Making everything searchable | Contents

This guide is adapted from Dive Into Accessibility by Mark Pilgrim and is shared with the GNU Free Documentation License v1.1