Deconstructing Accessibility Statements
Don’t read legal-ese? This will help you understand what accessibility statements actually say, and more importantly, why.
Authors note: Because of Medium’s refusal to address its accessibility issues for both authors and readers, I’ve moved my last three years of blogs to Substack. Please sign up there for notices of all new articles. Also, I will be updating older articles (like this one) and the updates will only be published on Substack. Thank you for your continued readership and support.
This is MY interpretation of accessibility statement legal-ese. I am not your lawyer. You need to make up your own mind. With your own lawyer. Who is not me.
I received the following question after writing an article called “10 things that indicate people have no clue about accessibility” where one of the “10 things” was the lack of an accessibility statement being indicative of “no clue.” It started with “I would like to start putting a11y statement on our sites and wonder whether this is okay”
We are actively working to ensure our sites are WCAG 2.0 AA-compliant.
Please contact us if you are facing accessibility issues when using our sites
In processing my answer to the questioner, I realized that I had the privilege of having been to law school which allows me to translate legal-ese into accessibility-ese (and vice-versa). So I told the questioner that I would write a comprehensive article rather than give them a quick two-sentence LinkedIn message about what should go into their accessibility statements.
Where should accessibility statements go?
The first question that needs to be asked and answered concerning accessibility statements is not what is in them, but where should they appear. Accessibility statements should always:
- have the shortest URL possible, something like:
where foo.com is your domain and .ext is the extension of your default framework such as…