What a accessibility statement is for
An accessibility statement tells visitors what you do to make your site usable by people with disabilities, which standard you aim for and how to report problems. Some laws require one, and it helps users even where none does.
Who needs one
Public bodies, many EU businesses under accessibility law, online shops and anyone who wants to show they take access seriously. It must be truthful: do not claim more than you have done.
What your accessibility statement covers
What the wizard asks you
These are the kinds of questions. Each one explains why we ask it, and you can skip what does not apply.
- Question 1Which standard do you aim for?
- Question 2Have you tested the site, and how?
- Question 3What known issues remain?
- Question 4How can people report a barrier?
- Question 5When did you last review it?
A sample clause
Your real text is built from your answers. This is an example of the plain style we aim for, with the parts you fill in shown in brackets.
We aim to meet WCAG 2.2 level AA. If you find something on this site that you cannot use or read, please email [email] with the page address and what went wrong. We will reply within [5] working days and tell you what we plan to do.
Sample text for illustration. Your page is written from your own answers.
Mistakes we see most
- Claiming full compliance without testing. Be specific about what you checked.
- Using an overlay widget as proof of accessibility. Overlays do not replace fixing the site.
- Not responding to reports. A feedback route is only useful if someone reads it.

