An accessibility statement is a page on your website that explains how accessible the site is, what you are doing to improve it and how visitors can get help if they run into a barrier. For public-sector bodies in some countries it is a legal requirement. For a business website, it is a sign of good faith that costs little and helps visitors who would otherwise give up.
The best statements are short, honest and specific. The worst are vague promises copied from another site, or claims of full compliance that the site doesn’t meet. This guide explains what to include and how to write one you can stand behind.
The short answer
A good accessibility statement includes:
- your commitment, in a sentence or two;
- the standard you aim for, usually WCAG 2.2 level AA;
- the current status: fully, partly or not yet conforming;
- known issues and what you are doing about them;
- how to contact you for help or to report a problem, with a reply time;
- how and when the site was assessed, and when the statement was last updated.
Keep it in plain language, link to it from the footer, and review it whenever the site changes significantly.
Why publish one
- It helps visitors. Someone who hits a barrier can find out whether there is a workaround and how to get the information another way.
- It shows honesty. Admitting known issues, with a plan to fix them, builds more trust than claiming perfection.
- It focuses your own work. Writing it forces you to check the site and decide on priorities.
- It may be required. Rules differ by country and sector. Public bodies in many places must publish statements, and rules such as the European Accessibility Act affect some businesses. Check what applies to you.
The W3C provides guidance and a free accessibility statement generator that walks you through the main sections.
What to include
| Section | What to write |
|---|---|
| Commitment | A short sentence about wanting the site to be usable by everyone |
| Standard | The guideline you aim for, such as WCAG 2.2 level AA |
| Conformance status | Fully conforming, partially conforming or non-conforming |
| Known limitations | Specific issues, where they occur and any workarounds |
| Feedback and contact | Email and phone for accessibility issues, with a reply time |
| Assessment approach | How you checked: self-assessment, external audit, user testing |
| Compatibility | The browsers and assistive technologies you tested with, if any |
| Date | When the statement was prepared and last reviewed |
Describing conformance honestly
WCAG uses three conformance terms:
- Fully conforms: the content meets every success criterion at the stated level, without exceptions.
- Partially conforms: some parts don’t yet meet the standard.
- Doesn’t conform: much of the site doesn’t meet it.
Most real websites partially conform. Saying so, with a list of what is still being fixed, is accurate and respectable. Claiming full conformance without an audit is risky and misleading. Our guide to WCAG 2.2 explains the levels and criteria.
Writing the known limitations
This is the most useful part for visitors and the part most statements leave out. Be specific:
- What: “Some older PDF price lists are not tagged for screen readers.”
- Where: “On the downloads page.”
- Workaround: “Email us and we will send the information in an accessible format.”
- Plan: “We are replacing these with web pages by March.”
Avoid vague phrases such as “we are working hard to improve accessibility” on their own. Pair them with specifics.
The contact section
Make it easy to report a problem:
- give an email address and, if possible, a phone number;
- say how quickly you will respond;
- offer to provide information in another format;
- make sure the contact method itself is accessible, for example not an inaccessible form.
Then make sure someone actually reads and replies to these messages.
A short example
Here is the kind of opening a small business might use, adapted to its own situation:
We want everyone to be able to use this website. We aim to meet WCAG 2.2 level AA. The site partially conforms: most pages meet the standard, but some older downloadable documents do not yet work well with screen readers. If you have difficulty using any part of the site, email us and we will reply within two working days and provide the information in a format that suits you. We last reviewed this statement on 1 November 2026, using automated checks, keyboard testing and a screen reader on our main pages.
That paragraph is short, but it answers every question a visitor with a barrier is likely to have. The rest of the statement then adds the detail: the list of known issues, the plan and the full contact options.
How to assess your site first
You need some evidence before you can write an honest statement:
- Run automated checks on key pages to catch common issues such as missing alt text and low contrast.
- Test with a keyboard, as in our guide to keyboard accessibility testing.
- Try a screen reader on your main journeys, such as finding a service and sending an enquiry.
- Consider an expert audit for larger or higher-risk sites. Our guide to website accessibility audits explains what one involves.
Record what you found and what you fixed. That record becomes the basis of the statement.
Where to publish it
- Create a dedicated page, for example
/accessibility/. - Link to it from the footer of every page, next to the privacy policy.
- Publish it in each language your site supports, with contact details that work for each audience.
- Write it in plain language, and make sure the page itself is accessible.
Keeping it current
A statement dated years ago suggests nobody is checking. Review it:
- after a redesign or major new feature;
- when known issues are fixed or new ones are found;
- at least once a year.
Update the date each time you review it, even if little has changed, and note what was checked.
Frequently asked questions
Is an accessibility statement legally required for my business?
It depends on your country, sector and size. Public-sector bodies are often required to publish one; some private businesses are affected by laws such as the European Accessibility Act. Check the rules that apply to you, and take advice if you are unsure.
Can I copy another website’s accessibility statement?
You can use the structure, but the content must describe your own site. A copied statement that lists the wrong issues, or none, is misleading.
Does publishing a statement mean my site is accessible?
No. The statement describes the situation; it doesn’t fix anything. Its value comes from being honest and from the work behind it.
What to do next
Run a quick keyboard test and an automated check on your three most important pages, then draft a short statement using the sections above. Be honest about what isn’t fixed yet and give a clear way to get help.
Accessibility is built into every site we design through our website design and development service, from layouts and colours to forms and navigation. For a wider introduction, see our web accessibility guide.