Do I need an accessibility statement?

If you serve the public, it helps. It sets expectations and gives users a route to get help.

What should it include?

A clear status, known issues, contact details, response times, and the last review date.

Will it protect me legally?

No. It is not a shield. It should reflect reality and show progress.

Can you write it for us?

Yes. I base it on an audit and agreed scope, then help you keep it updated.

Accessibility statements that mean something

An accessibility statement sets expectations. It tells users how to get help. It tells your team what still needs fixing.

What a good statement includes

A clear claim. For example, “partially compliant with WCAG 2.2 AA”.
Known issues. Written in plain language, linked to key pages where possible.
A feedback route. Email, form, or phone, plus response times.
What you are doing next. Fix plan and review schedule.

GOV.UK guidance explains what public sector bodies must publish and why Source 1 . W3C’s statement generator helps structure a statement properly Source 2 .

Common mistakes

Vague language like “we aim to be accessible”.
No contact route for help.
No review date.
Copying a template without testing the site.

Sources

[1] GOV.UK. Accessibility requirements for public sector websites and apps. View source Back to article
[2] W3C WAI. Accessibility Statement Generator. View source Back to article