An accessibility statement is a public page that explains how accessible your website or app is, which parts are not yet accessible and why, how people can get content in another format, and how to report a problem. In the UK, public sector bodies are legally required to publish one. In the EU, the European Accessibility Act, in force since 28 June 2025, requires many private businesses to publish accessibility information for covered services. For everyone else, it is a clear signal of trust.
Key takeaways
- An accessibility statement explains how accessible your site is, what is not, and how people can get help.
- UK public sector bodies must publish one; many private businesses serving EU consumers need equivalent information under the European Accessibility Act.
- Base the statement on a real test against WCAG 2.2 AA, not on assumptions.
- Be honest about known issues and give a date for fixing them.
- Review and update the statement at least once a year.
What is an accessibility statement?
It is a page, usually linked from your footer, that tells disabled visitors and everyone else how well your site meets accessibility standards. A good statement is specific: it names the standard you test against, lists the known problems in plain language, explains what you are doing about them and gives a real contact route. It is not a promise that everything is perfect.
Who needs an accessibility statement?
| Organisation | Rule | Requirement |
|---|---|---|
| UK public sector bodies | Public Sector Bodies Accessibility Regulations 2018 | Must meet WCAG 2.2 AA and publish an accessibility statement |
| EU public sector bodies | Web Accessibility Directive (EU) 2016/2102 | Must publish an accessibility statement, based on the EU model |
| Private businesses serving EU consumers | European Accessibility Act, from 28 June 2025 | Covered services, such as e-commerce and banking, must be accessible and publish information on how they meet the requirements |
| Microenterprises providing services | European Accessibility Act exemption | Fewer than 10 staff and annual turnover or balance sheet of 2 million euros or less are exempt from the service requirements |
| Other UK private businesses | Equality Act 2010 | No statement required, but a duty to make reasonable adjustments applies |
This is a summary, not legal advice. Check how the rules apply to your organisation and the countries you serve. Our European Accessibility Act guide covers the EU rules in more depth.
Why publish one even if you do not have to?
A clear statement tells this audience you take access seriously and tells them how to get what they need today. It also shows procurement teams, who increasingly ask about accessibility, that you have tested your product and have a plan.
What should an accessibility statement include?
| Section | What to write |
|---|---|
| Commitment and scope | Who you are, which website or app the statement covers |
| Compliance status | Fully, partially or not compliant with WCAG 2.2 AA |
| Known issues | Each problem in plain language, the WCAG criterion it fails and when you plan to fix it |
| Exemptions | Content outside scope or a disproportionate burden, with reasons |
| Alternative formats | How to request content as large print, audio, easy read or another format |
| Feedback and contact | An email, phone number and expected response time |
| Enforcement | In the UK, the Equality and Human Rights Commission, or the Equality Commission in Northern Ireland |
| How you tested | Who tested, when, and which pages or journeys |
| Dates | When the statement was prepared and last reviewed |
How to write an accessibility statement
- Audit first. Test your key pages and journeys against WCAG 2.2 AA with automated tools and manual testing, including keyboard and screen reader checks.
- Decide your compliance status. Fully compliant means no failures; most sites are partially compliant.
- List known issues honestly. Describe each problem in terms of what a user cannot do, not only the technical criterion.
- Add a fix plan. Give dates or quarters for fixing each issue, and name any disproportionate burden claims with reasons.
- Offer alternatives and a contact. Tell people how to get content in another format and how quickly you will reply.
- Publish and link it. Put it on its own page and link it from the footer of every page.
- Review regularly. Update it after major releases and at least once a year.
Accessibility statement template
Copy the structure below and replace the text in brackets.
Accessibility statement for [website name]
- This accessibility statement applies to [website address]. It is run by [organisation]. We want as many people as possible to be able to use this website.
- For example, you should be able to change colours and fonts, zoom in up to 400% without text spilling off the screen, navigate using just a keyboard or speech recognition, and listen to most of the site using a screen reader.
How accessible this website is
- We know some parts of this website are not fully accessible: [list, for example: some older PDFs are not accessible to screen readers; some images lack text alternatives].
Feedback and contact information
- If you need information in a different format, or find a problem not listed on this page, contact [email] or [phone]. We will reply within [number] working days.
Compliance status
- This website is [fully / partially / not] compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the issues listed below.
Non-accessible content
- [Issue, the user impact, the WCAG criterion it fails, and when you plan to fix it.]
How we tested this website
- This website was last tested on [date] by [who]. We tested [pages or journeys] using [tools and methods].
Preparation of this statement
- This statement was prepared on [date]. It was last reviewed on [date].
Accessibility statement example: vague vs useful
| Vague | Useful |
|---|---|
| We are committed to accessibility | This site is partially compliant with WCAG 2.2 AA; the issues are listed below |
| Some content may not be accessible | Our pricing table cannot be read by screen readers; we will fix it by March |
| Contact us with any issues | Email access@example.com and we will reply within 5 working days |
| Updated regularly | Last tested on 12 September 2026 by an external auditor |
Do you need an accessibility audit first?
Yes. A statement is only as good as the testing behind it. An accessibility audit checks your key journeys against WCAG with automated scans and manual testing, then gives you a prioritised list of fixes. It is the evidence your statement relies on, and the roadmap that makes the next version shorter. Our UX audit checklist shows where accessibility fits into a wider review.
Frequently asked questions
What is an accessibility statement?
An accessibility statement is a public page that explains how accessible a website or app is, lists the parts that are not yet accessible and why, tells people how to get content in another format, and explains how to report a problem.
Is an accessibility statement a legal requirement in the UK?
It is a legal requirement for UK public sector bodies under the Public Sector Bodies Accessibility Regulations 2018. Private businesses are not required to publish one, but they have duties under the Equality Act 2010, and one is expected by many procurement teams.
Does the European Accessibility Act require an accessibility statement?
The European Accessibility Act requires providers of covered services, such as e-commerce and banking, to publish information explaining how their service meets the accessibility requirements. Many businesses do this through an accessibility statement. Microenterprises providing services are exempt.
What standard should an accessibility statement refer to?
Most statements refer to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. The European standard EN 301 549 is based on WCAG and is used for compliance with EU rules.
How often should I update my accessibility statement?
Review it at least once a year and after any major redesign or release. Update the list of known issues as you fix them, and record the date of the latest test and review.
Where should the accessibility statement go on my website?
Publish it on its own page and link it from the footer of every page, so it is easy to find from anywhere on the site. Some organisations also link it from the header or from a help page.
Can I write an accessibility statement without an audit?
You can, but it will not be accurate. The statement has to describe real known issues and how you tested the site, so it should be based on an audit against WCAG 2.2 AA with automated and manual testing.