Why an Accessibility Statement Matters

An accessibility statement is a published declaration of your website's current accessibility status: what standards it meets, what known issues remain, and how users who encounter barriers can get in touch.

For public sector bodies, a published accessibility statement is a legal requirement under the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. Most charities are outside them. The Regulations reach only a "public sector body" as regulation 3 defines it, and regulation 4 then excludes non-governmental organisations unless their services are essential to the public or meant for disabled people. GOV.UK's guidance puts it more simply, as three triggers: a charity is caught if it is mostly financed by public funding, provides services essential to the public or provides services aimed at disabled people. If you meet one, treat the statement as a duty and, as GOV.UK says, check with a legal adviser if you are not sure. If you meet none, it is voluntary, and still something funders may look for.

Whether or not the Regulations reach you, the Equality Act 2010 still applies to services you provide in Great Britain (the Disability Discrimination Act 1995 in Northern Ireland). A service provider must make reasonable adjustments for disabled people, and for services that duty is owed to disabled persons generally, not only to someone who has already asked, so it applies before anyone hits a barrier. GOV.UK is explicit that an organisation exempt from the 2018 Regulations is still legally required to make reasonable adjustments when they are needed. A statement does not discharge that duty, but it records what you have tested and gives people the route to ask. If you sell goods or services to consumers in the EU, a third regime may apply: see What the European Accessibility Act Means for NGO Websites.

An accessibility statement also serves a practical governance function: it documents what testing has been done, when, and by whom. If an accessibility complaint is made or a funder asks for evidence of compliance, the statement is the starting point for that conversation.

This post provides a template in plain language, because the statement has to be readable by the people it most directly serves. If the 2018 Regulations apply to you, do not use this template. Regulation 8 requires a statement in accordance with the model, and parts of the wording are legally required. Start from GOV.UK's sample statement and its publishing guidance.

What an Accessibility Statement Should Cover

A complete accessibility statement should address:

  1. Which accessibility standard the site aims to meet and at what level
  2. Which parts of the site are accessible and which have known issues
  3. What testing has been conducted and when
  4. How users who encounter barriers can contact the organisation
  5. What the organisation will do if it cannot immediately fix a barrier
  6. Where to get advice if the response is unsatisfactory
  7. When the statement was last reviewed

The Template

The template below is for a charity the 2018 Regulations do not cover, aiming for WCAG 2.2 AA. Replace every bracket, delete every instruction in brackets, and delete any sentence that is not true of your site, including sentences with no bracket in them. If you are not confident that something is accurate, leave it out.

Accessibility Statement for [Organisation Name]

Last reviewed: [Month Year]

Our Commitment

[Organisation Name] wants as many people as possible to be able to use this website. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.

Compliance Status

[Keep one paragraph and delete the other three.]

This website is fully compliant with the Web Content Accessibility Guidelines version 2.2 AA standard. We are not aware of any pages or content that fail to meet it.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard. Some pages or content do not meet it, and known issues are listed below.

This website is not compliant with the Web Content Accessibility Guidelines version 2.2 AA standard. Most requirements are not yet met, and known issues are listed below.

We have not yet tested this website against the Web Content Accessibility Guidelines version 2.2 AA standard, so we cannot say how far it complies. We plan to test it by [Month Year].

Known Accessibility Issues

[List the issues you know about, precisely. The three below are examples: keep one only if it is true of your site, and add your own.]

  • PDF documents: Some older PDF documents linked from this site have not been made fully accessible. We are working to replace or remediate these. If you need an accessible version of a specific document, please contact us using the details below and we will provide it within [X working days].
  • Video captions: Some videos published before [date] do not have closed captions. We are adding captions to these progressively. New videos published after [date] include closed captions.
  • Third-party content: Some content embedded from third-party providers, including [name any: donation forms, video platforms, event booking systems], may not meet the same accessibility standards as the rest of this site. We are raising this with the providers. If one stops you doing something, contact us and we will give you another way to do it.

[Delete this section if you are fully compliant or have not yet tested.]

How We Tested This Website

[Keep only the methods you have actually used. If you have not tested yet, delete this whole section.]

This website has been assessed for accessibility using the following methods:

  • Automated testing using [WAVE / Axe DevTools / Lighthouse: list the tools you actually used]
  • Manual keyboard navigation testing
  • Screen reader testing using [NVDA / VoiceOver: list what you used]
  • Colour contrast checking for all text elements

Testing was last completed: [Month Year]

Testing was carried out by: [your digital lead / a named external accessibility auditor: specify who carried out the testing]

[Keep this sentence only if you do this.]

We test accessibility before significant content updates and at a minimum annually.

Technical Information

[Optional: name the platform your website is built on. Do not say that a platform makes the site accessible. That depends on how the site was built and on its content.]

The following technologies are relied on for conformance:

  • HTML
  • CSS
  • JavaScript

What to Do If You Cannot Access Part of This Website

If you experience difficulties accessing any part of this website, please contact us:

Email: [your accessibility or general contact email]

Phone: [phone number, if applicable]

We aim to respond to accessibility enquiries within [5 / 10] working days.

If you need information in a different format, for example large print, easy read, audio or a language other than English, please let us know and we will do our best to provide it.

Reporting Accessibility Problems

We welcome feedback on the accessibility of this website. If you find content that is not accessible, please contact us using the details above.

If You Are Not Happy With Our Response

If you are not satisfied with our response to an accessibility concern, you can get advice from the [Equality Advisory and Support Service (EASS) in England, Scotland and Wales / Equality Commission for Northern Ireland (ECNI) in Northern Ireland: keep the one that applies. Outside the UK, name your national equality body or delete this section.]

How to Use and Maintain This Statement

Where to publish it: Create a standalone page at a consistent address such as /accessibility. Link to it from the footer of every page, alongside the privacy policy, using the text "Accessibility". That is the location and label people look for, so do not bury it inside another page. Write in plain English, explain WCAG on first use, and make sure the page itself is accessible: an inaccessible accessibility statement is a credibility problem.

How to fill it in honestly: The most important principle is accuracy over aspiration. Don't claim full compliance if you haven't tested the site. Don't list known issues vaguely: name them specifically. An honest statement that acknowledges partial compliance and explains what's being done is more credible and more useful than a compliance claim that can't be substantiated. Do not claim full WCAG 2.2 AA compliance unless you have completed both automated testing and manual keyboard and screen reader testing. If you have only run automated tests you cannot yet claim partial compliance either, because partial means the site meets most requirements. Say what you have tested and what is still to come.

When to update it: Update the statement whenever you make significant changes to the site's accessibility: following a remediation project, when known issues are resolved, or when new known issues are identified. Review the statement at minimum annually even if nothing has changed, and update the "last reviewed" date.

The testing section is important: The statement should reflect testing that has actually been carried out, not aspirational testing that you intend to do. If you haven't yet done screen reader testing, say so and indicate when you will. If accessibility testing has only been automated (WAVE and Axe), say that. Automated tools miss a large share of barriers (in a 2017 Government Digital Service test, the best single tool found 37% of the barriers counting only errors and warnings), and an informed reader will know that automated testing alone is not sufficient for a full compliance claim.

Accessibility Statement Checklist

Before publishing your accessibility statement, confirm:

  • Compliance status reflects the actual tested state of the site, not an aspiration
  • Known issues are listed specifically, not vaguely
  • Testing methodology and date are accurate
  • Contact information for accessibility enquiries is current and monitored
  • Response time commitment is realistic and will be met
  • The "last reviewed" date is current
  • The statement is published at a consistent address and linked from the footer
  • The statement page itself is accessible: readable by screen readers, with correct heading structure and sufficient colour contrast

Using the W3C Generator

The W3C provides a free accessibility statement generator at w3.org/WAI/planning/statements/generator. It asks for the details a statement usually carries and produces a draft you can adapt. It is not written to the UK model, so review it rather than publishing it as it stands.

Maintaining the Statement

The accessibility statement is a living document. Update it when: the site undergoes significant changes, an accessibility audit identifies new issues or confirms remediation, the standard you are measured against changes (as EN 301 549, the European standard behind the EAA, will when its version adopting WCAG 2.2 is cited in the EU's Official Journal), or a user reports a barrier that reveals a previously unknown limitation.

Include the review in your regular website checks. A website governance policy is a good place to record who does it and when.

To establish your baseline, start with how to test keyboard navigation and why accessibility is a property of the system, not a task. For the regulatory context, see What the European Accessibility Act Means for NGO Websites.

A Blueprint Audit checks accessibility across your own site, as part of a wider governance diagnostic.

Further Reading

Next step: check that your analytics respects consent with GA4 Consent Mode V2.