Accessibility statements that mean something

What an accessibility statement is

An accessibility statement explains how accessible your website is. It tells users what works, what does not, and how to get help [1]Source 1 .

For public sector sites in the UK, accessibility statements are legally required [3]Source 3 . For other sites, they show commitment and help users understand what to expect.

Why most statements fail

Many accessibility statements are generic templates that say nothing useful.

• They claim full compliance without evidence.
• They list standards without explaining what was tested.
• They do not explain known problems or how to work around them.
• They make it hard to report issues or request alternatives.

What a useful statement includes

1. Standards and compliance level

State which standard you aim for, usually WCAG 2.2 Level AA [5]Source 5 . Be honest about your current status.

• If you are fully compliant, say so and explain how you know.
• If you are partially compliant, explain what works and what does not.
• If you are working towards compliance, explain your timeline.

2. What was tested and when

Explain your testing approach [6]Source 6 . This builds trust.

• List the pages or journeys that were tested.
• Explain the testing methods, such as automated tools, manual testing, or user testing.
• State when testing happened and when it will be reviewed again.

3. Known problems

List accessibility issues you know about. This is honest and helpful.

• Describe each problem clearly.
• Explain the impact on users.
• Provide workarounds where possible.
• State when you plan to fix each issue.

4. How to report problems

Make it easy for users to report accessibility issues.

• Provide a clear contact method, such as email or a form.
• Explain what information helps, such as the page URL and what happened.
• Set expectations for response times.

5. Alternative formats

Explain how users can access information in other ways.

• Offer to provide content in alternative formats.
• Explain how to request alternatives.
• State response times for requests.

6. Enforcement procedure

For UK public sector sites, you must include an enforcement procedure [3]Source 3 . This explains what users can do if they are not satisfied with your response.

Legal requirements for UK public sector

Public sector bodies in the UK must publish an accessibility statement [3]Source 3 . The statement must meet specific requirements.

• It must be published on your website.
• It must explain how you meet accessibility regulations.
• It must include an enforcement procedure [2]Source 2 .
• It must be reviewed and updated regularly.

GOV.UK provides guidance on what to include [2]Source 2 . The W3C also provides a statement generator tool [1]Source 1 .

What to avoid

Generic claims

Avoid statements such as we are committed to accessibility without explaining what that means. Be specific about what you have done and what you plan to do.

Overstating compliance

Do not claim full compliance unless you have evidence from proper testing [6]Source 6 . Overstating compliance creates legal risk and damages trust.

Hiding problems

Do not hide known accessibility issues. Users will find them anyway. Being honest builds trust and helps users work around problems.

Making it hard to contact you

Do not hide contact information or make reporting issues difficult. Users need a clear way to get help.

How to write it in plain language

Write your statement in clear, simple language. Avoid jargon and technical terms where possible.

• Use short sentences and paragraphs.
• Explain technical terms when you must use them.
• Use headings to break up content.
• Make the statement itself accessible [5]Source 5 .

Where to put it

Make your accessibility statement easy to find.

• Link to it from your footer on every page.
• Include it in your main navigation if space allows.
• Mention it in your contact or about pages.
• Use a clear, consistent link label such as Accessibility statement.

Keeping it current

Accessibility statements must be reviewed and updated regularly.

• Review the statement when you make significant changes to your site.
• Update it when you fix known problems.
• Review it at least annually, even if nothing changes.
• Update the last reviewed date when you make changes.

Testing your statement

Test your accessibility statement like any other page [6]Source 6 .

• Check it works with keyboard navigation.
• Test it with a screen reader.
• Verify all links work.
• Check it is readable at 200% zoom.
• Make sure contact forms or email links work.

Example structure

A useful statement might follow this structure:

1. Introduction explaining your commitment to accessibility.
2. Standards and compliance level, with honesty about current status.
3. Testing approach, explaining what was tested and how.
4. Known problems, listed clearly with workarounds and fix dates.
5. How to report problems, with clear contact information.
6. Alternative formats, explaining how to request them.
7. Enforcement procedure, if required [3]Source 3 .
8. Last reviewed date and next review date.

Legal considerations

In the UK, the Equality Act 2010 requires reasonable adjustments for disabled people [4]Source 4 . Public sector bodies have additional requirements under the Public Sector Bodies Accessibility Regulations [3]Source 3 .

An honest, useful accessibility statement helps demonstrate your commitment to accessibility. It also helps users understand what to expect and how to get help.

Next step

If you do not have an accessibility statement, start with the W3C statement generator [1]Source 1 . Then customise it with your specific information, known problems, and contact details. Make it honest, useful, and easy to find. Review it regularly and update it when things change. If you need help creating an accessibility statement or conducting an accessibility audit to identify issues, get in touch to discuss your needs. For more on what accessibility audits should include, see what an accessibility audit includes. For more on writing accessibility statements, see accessibility statements done properly.