Anikto LLC

Should You Provide an Accessibility Statement on your Website?

When an organization takes the time and effort required to provide a fully accessible online experience, there is justifiable pride in detailing the many features that have been implemented on behalf of users with disabilities. The question remains as to whether it’s of value to list these operable benefits on a dedicated page within the website.

There are compelling arguments on both sides of the debate. A recent post on the Digital Web Magazine website investigates whether accessibility statements are truly necessary. The author goes on to propose that perhaps a standardization template be considered when crafting accessibility statements, with the following discussion points as guidance:

1. The term “Accessibility Statement” needs to be reviewed as it does not accurately define the content which it should contain. The term ‘statement’ promotes the listing of conformance information and accessibility features implemented. Perhaps ‘Help using this website’, ‘Using this website’ or ‘About this website’ would be more appropriate?
2. Is there a requirement for a universal accessibility statement template to ensure that information is provided in a consistent format? The template would provide a consistent design and format to website visitors, allowing key information to be located quickly.
3. Where should the accessibility link be located so that it is consistent throughout all websites, and is clearly visible and audible to website visitors?

Accessibility statements to me are sort of an either/or feature. I personally don’t know of any users with disabilities who will abandon a website because they cannot locate a statement; if the features of the site are accessible and usable, the experience is a good one. If a site cannot accommodate their needs or is difficult to use, they move on.

That said, I’m going to outline some attributes to help define whether the inclusion of an accessibility statement is a good idea:

Reasons to Include an Accessibility Statement

• Accessibility statements demonstrate that users with disabilities have been considered throughout the user-centered design process
• They can provide clues defining custom features and functionality, such as access keys
• They can address known barriers to content that remains inaccessible, as well as offer links to textual equivalents for rich media elements (such as video)
• Accessibility statements can provide a means to contact your organization’s “accessibility advocate”
• Statements can list the legal and technical criteria under which the site was developed

Reasons Why an Accessibility Statement Isn’t Necessary

• There is little evidence that statements are read by users with disabilities, who don’t spend a lot of time concentrating on a site’s accessibility features — they simply use the site as intended
• Accessibility statements can contain difficult technical jargon of little value to common users — again, most people don’t really care, they just want to use the site
• Statements can be difficult to find in a site’s architecture, as they aren’t universally included features such as a Search or Site Map
• If the site is not tested with actual users, a statement may contain inaccuracies and assumptions
• Accessibility is often considered an IT function, of whom it is perhaps a better use of effort cycles to develop and maintain compliance
• Until there is a consistent template from which to craft an accessibility statement, poorly-worded artifacts run the risk of being interpreted as a marketing tactic

It’s an interesting little debate. My feeling is this: if you’re going to provide an accessibility statement, keep it brief, keep it accurate, make it easy to find (perhaps a part of your site’s Help section), and provide some means of contact to report problems.