Accessibility statements: what they are and who needs one
What an accessibility statement must contain, who is legally required to publish one, and why an honest statement beats a claim of full conformance.
The short answer
An accessibility statement is a published page describing how accessible a website is, what does not conform, how to report problems and how to get information in another format. For public sector bodies in the European Union it is a legal requirement under the Web Accessibility Directive, following a prescribed model: the conformance status, the non-accessible content with reasons, the date of preparation and last review, the method of assessment, a feedback mechanism, and the enforcement procedure to escalate to. For businesses there is generally no obligation to publish one, though organisations in scope of the European Accessibility Act have their own information obligations about how a service meets the requirements. Many businesses publish a short statement voluntarily, and it is worth doing where real work has been done, because it signals the commitment and invites the feedback that finds problems testing missed. What matters most in either case is accuracy: an honest partially conformant statement with named issues and dates is credible, and a blanket claim of full conformance that fails a five-minute keyboard test is not.
What a statement contains
| Element | Public sector requirement | Business practice |
|---|---|---|
| Conformance status | Fully, partially or non-conformant against the standard | Same wording is useful |
| Standard referenced | The harmonised standard, aligned with level AA | Level AA |
| Non-accessible content | Listed with reasons and, where relevant, alternatives | List known issues honestly |
| Disproportionate burden | If claimed, with the assessment behind it | Rarely relevant |
| Preparation and review dates | Required | Date it and review annually |
| Assessment method | Self-assessment or third-party evaluation | Say which |
| Feedback mechanism | Required, with a response expectation | Include; staff it |
| Alternative formats | How to request information another way | Include if relevant |
| Enforcement procedure | The national escalation route | Not applicable |
| Improvement plan | Good practice | Dates for known issues |
Writing one
- Test first: automated checks, keyboard navigation, screen reader on key journeys, contrast, forms.
- List what fails and why, with an owner and a target date for each.
- Choose the status honestly: fully, partially or non-conformant.
- Write it in plain language, not in standards jargon.
- Name the feedback route and the person or team behind it, with a response time.
- Date it and set the review reminder.
- Link it from the footer alongside the other legal pages.
- Update it when issues are fixed or new ones are found, and at least annually.
Why a business might publish one anyway
It tells disabled customers that they were thought about, which is itself useful information when choosing a supplier. It invites the feedback that reveals problems automated testing never finds. It answers the accessibility questions in enterprise and public procurement before they are asked. And writing it forces the testing that produces the improvements, which is the real reason we recommend it to clients who have done the work.
What this means for you
Public sector bodies must publish an accessibility statement in the prescribed model with conformance status, known issues, feedback route and enforcement procedure. Businesses generally need not, and benefit from a short honest one where accessibility work has been done. Test before writing, name the failures with dates, staff the feedback route, date and review it annually. Accuracy is the whole value; a false claim of conformance is worse than none. This is general information rather than legal advice.
Frequently asked questions
Do we need an accessibility statement?
If you are a public sector body under the Web Accessibility Directive, yes, in the prescribed model with the required elements. If you are a business, generally no, unless a contract or a sector rule requires it, though organisations in scope of the European Accessibility Act have information obligations about how their service meets the requirements. Many businesses publish one voluntarily, and we recommend it where accessibility work has been done.
What should it say if we are not fully conformant?
The truth, specifically. Name the parts that do not conform, explain why, give a date for fixing them or the reason they cannot be fixed, and offer an alternative way to get the same information or service. A partially conformant statement with named issues and dates is credible and useful; a blanket claim of full conformance that a five-minute test disproves damages trust and, for public bodies, is a compliance failure in itself.
Who handles the feedback route?
A named person or team with the time to respond. The statement must include a way for people to report accessibility problems and request information in an accessible format, and for public bodies there is an enforcement procedure to point to if the response is inadequate. A feedback address that nobody monitors is worse than none, because it invites a complaint and then ignores it.
Sources
- EUR-Lex: Directive (EU) 2016/2102 on the accessibility of websites and mobile applications of public sector bodies (accessed 2026-09-12)
- W3C WAI: Developing an Accessibility Statement (accessed 2026-09-12)