Your accessibility statement is a promise, not a certificate
Every kitchen I worked in had an allergen chart on the wall. The danger was never the day it went up. It was six months later, when a supplier changed a recipe and nobody updated the chart. Nothing on it was a lie when it was printed. It just quietly stopped being true, and everyone kept trusting it because it was written down. Accessibility statements go the same way.
The short answer
- A statement describes your site on the day someone checked it. With no date, no known issues and no testing method, it describes nothing.
- Councils, schools and businesses are publishing claims they can't back up, then treating the statement as proof that the job is done.
- An honest “partially compliant” statement serves your visitors, and protects you, far better than a confident one you can't support.
Written once, trusted forever
The pattern is always the same. Someone is told the organisation needs an accessibility statement. They find a template, or ask an AI tool, and publish something that says the site meets the Web Content Accessibility Guidelines (WCAG) at Level AA. Box ticked.
Then the statement becomes the evidence. When a disabled visitor complains, staff point to it. When a new manager asks whether the website is accessible, someone points to it. Nobody tests the site again, because it's written down, so it must be true.
Meanwhile the site changes. New pages go up, a booking system gets bolted on, the menu becomes a PDF. The statement stays exactly where it was.
Three kinds we keep finding
The tool score dressed up as a rating
An automated checker gives the site a clean result, and the statement turns that into a WCAG level. We've seen a public-sector site claim AAA this way, while failing basic Level A and AA checks. We've written that one up in full: why an automated AAA score isn't an accessibility audit.
The borrowed template
A pub's statement describing its “design, development, and content teams”, ongoing accessibility training, a completed audit and a roadmap of improvements. None of it is mentioned anywhere else. There are no findings, no date and no list of problems. A basic automated scan of the site flagged a long list of errors before any manual testing started.
This statement was almost certainly written for a different kind of organisation and pasted in. The people who published it probably believed they were doing the right thing. But the words are now a claim to every customer who reads them.
The set-and-forget statement
Council and school statements that were accurate once. They're years old, still quote WCAG 2.1, and were last reviewed before the site was redesigned. The known issues list, if there is one, describes a website that no longer exists.
| Red flag | What it usually means |
|---|---|
| No date, or a date older than the last redesign | Nobody knows when the claim was last true, or it describes an old site |
| Still quotes WCAG 2.0 or 2.1 | It hasn't been reviewed since WCAG 2.2 became the standard |
| “Fully compliant” with no mention of who tested it or how | The claim rests on a scanner, a template or a hope, not a manual test |
| An audit is mentioned, but no findings or known issues | Either the audit didn't happen, or its results weren't acted on |
| “Some older pages may not be fully accessible” | Someone knows there are problems but hasn't listed them, so visitors can't work around them |
| Teams, training and processes the organisation plainly doesn't have | The text was copied from somewhere else |
| The only way to report a problem is the website's contact form | If the form is inaccessible, the one route for help is blocked too |
Why it matters
Disabled visitors trust it. Someone who reads “we meet WCAG 2.2 AA” reasonably expects the booking form to work with their screen reader. When it doesn't, they've lost time, and often the booking, the appointment or the form they needed to submit.
It stops problems being reported. A statement that says everything is fine tells visitors their problem must be their own fault. Many won't bother getting in touch.
It stops the organisation looking. This is the biggest one. A false statement isn't just wrong; it's the reason nobody checks again.
What the rules say
Public-sector bodies, including councils, must publish a statement under the Public Sector Bodies Accessibility Regulations 2018. It must say whether the site is fully, partially or not compliant, list the content that isn't accessible, explain how to get it in another format, and be reviewed regularly. Sites are now monitored against WCAG 2.2 AA.
Schools and nurseries are partially exempt. The regulations only cover content needed for essential online administrative functions. If a school does publish a statement, though, parents and pupils will read it and rely on it like any other.
Private businesses don't have to publish a statement at all. If they do, it's a claim to customers, and that claim has to be true. Consumer protection law, now in the Digital Markets, Competition and Consumers Act 2024, treats misleading claims that could affect a customer's decision as unfair commercial practices. The Advertising Standards Authority's rules also cover marketing claims businesses make on their own websites. How these apply to accessibility statements hasn't really been tested, but a paragraph copied from a template isn't worth the risk.
And for everyone, the Equality Act 2010 applies whether or not you publish a statement. A statement doesn't create your duty to make reasonable adjustments, and it doesn't remove it. It does show you knew about it.
What an honest statement looks like
Honest doesn't mean long, and it doesn't mean admitting you've failed. It means telling visitors what works, what doesn't, and how to get help in the meantime. Here's a short example for a made-up venue.
Accessibility statement for The Example Inn
This statement was prepared on 14 October 2026. Our website was tested by an independent auditor using a keyboard, screen readers (NVDA and VoiceOver) and automated tools.
Compliance status: this website is partially compliant with WCAG 2.2 Level AA, because of the issues below.
Known issues:
- Our food and drink menus are images, so screen readers can't read them. We're replacing them with web pages by January 2027. Until then, phone us and we'll read the menu to you, or email it as plain text.
- The date picker on our booking form can't be used with a keyboard. You can book by phone or email instead.
- Some photos in our gallery don't have useful descriptions.
Tell us about a problem: email or phone us. We aim to reply within five working days.
Visiting us: step-free entrance by the side door, accessible toilet on the ground floor, and a hearing loop at the bar.
Three known issues, each with a workaround. A date. A real way to get in touch. Information about the building, which is what many people actually came looking for. That statement is more useful than any “fully compliant” claim, and it's one you can stand behind.
Check your own statement in ten minutes
- Find the date. If there isn't one, or it's older than your last redesign, the statement needs reviewing.
- Check the WCAG version. It should be 2.2.
- Test the claim. Unplug your mouse and try the Tab Test on your main pages. If you can't use them, “compliant” isn't true.
- Look for known issues. If you know about a problem, list it with a workaround.
- Check the contact route. Give an email address and phone number, not just a form.
- Put a review date in the diary. At least once a year, and after any redesign.
For why scanner results can't back up a compliance claim, read why an automated AAA score isn't an accessibility audit, or see how much a website accessibility audit costs.
Sources
- Legislation.gov.uk: The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018
- GOV.UK: Understanding accessibility requirements for public sector bodies
- GOV.UK: Sample accessibility statement
- Legislation.gov.uk: Digital Markets, Competition and Consumers Act 2024
Want a statement you can stand behind?
I test by hand with a keyboard, VoiceOver, NVDA and JAWS, then help you write an accessibility statement that says what's true, in plain English.
Email Clearsight AccessThis guide is general information, not legal advice. Back to all Web Accessibility Guides.