I think that wraps up my thoughts on accessibility statements.
My own accessibility statement points to WCAG 2.2 AA, explains how I tested things and is upfront about the fact that I'm not perfect.
In some places, like public sector sites under EU law, you're legally required to have one. But honestly, even if nobody's forcing you, it's just a decent thing to do.
The best statements are plain and honest. It's best you skip the jargon and the legal language and instead write for the person who needs help. A good statement covers what you're aiming for, how you tested it, how people can contact you and any known issues they should be aware of. Admitting known issues matters a lot. If something's broken, just say so.
Keep it updated too. If you fix something or find a new problem, the statement should reflect that. And make it easy for people to report issues. Include a direct email address dedicated for accessibility issues. Don't reuse your info@ email.
Don't claim you fully comply with everything. That's a red flag. It's way better to admit where you are, what you know is still off and offer ways to get help.
To make it easy for you, I've compiled a list of what to do and what not to do.
Do:
- State your accessibility commitment clearly in plain language
- Mention the standard you are targeting, like WCAG and the conformance level
- Explain how you test accessibility, including automated and manual methods if you use both
- List known accessibility issues and, where possible, alternatives or workarounds
- Provide a direct contact method for accessibility feedback or support
- Update the statement when the product changes or when testing reveals new information
- Keep the language simple, direct and user-friendly
- Be honest about limitations and progress
Don't:
- Don't write the statement as a legal or technical document full of jargon
- Don't say the site is "fully accessible"
- Don't leave the statement go stale
- Don't hide known problems or pretend they don't exist
- Don't make users hunt for a way to contact you about problems
- Don't use vague generic copy that could describe any website
- Don't over-promise perfection
I hope these help!