Accessibility
What is an accessibility statement and do I need one?
A published page stating which standard you target, how far the site currently conforms, what is known not to conform, and how to report a barrier. It is mandatory for UK and EU public sector bodies and good practice for everyone else.
What an honest statement contains
- The standard and level you target — normally WCAG 2.2 AA
- Current status: fully conformant, partially conformant, or not conformant
- Known issues, named specifically rather than gestured at
- A contact route for reporting a barrier, and how quickly you will respond
- The date of the last assessment and how it was carried out
Why partial conformance is the credible claim
Very few sites are fully conformant, and claiming to be invites the first counter-example. Naming the specific gaps, with a date for addressing them, demonstrates that someone actually tested rather than ran a scanner once.
What it does not do
It is not a defence. A statement documents intent and progress; it does not substitute for fixing the barriers it describes. Publishing one and changing nothing is worse than publishing none, because it is evidence you knew.
The longer version
This answer is deliberately short. If you want the full treatment, Website accessibility, without the compliance theatre covers it in about 5 minutes — free, ungated, written from client work.
Who answered this
Anas Bin Masud builds e-commerce sites and does technical SEO for businesses in the UK, Canada and Pakistan — fifteen live client sites, six of them stores taking real payments. These answers come from those projects rather than from a content brief. More about how I work, or ask me something directly.