Guide

Accessibility statement template (free, copy-paste)

Last updated: 29 June 2026

An accessibility statement is a short public page where you describe how accessible your website is, which standard you're aiming for, and how someone can reach you if they hit a barrier. It's one of the simplest, highest-value things you can publish — and both the EU Accessibility Act and ADA-driven best practice expect you to have one. This guide explains what to include and gives you a template to adapt. (General information, not legal advice.)

Why publish an accessibility statement?

  • It's expected. Accessibility regimes want you to be able to demonstrate accessibility, not just claim it. A statement is the public face of that.
  • It gives users a path. People who hit a barrier need a way to tell you and get help. That's both decent and risk-reducing.
  • It shows good faith. Documenting your target standard, what you've tested, and known gaps demonstrates you're treating accessibility seriously.

What to include

  • Your commitment — a sentence on why accessibility matters to you.
  • The standard you target — almost always WCAG 2.2 Level AA.
  • Current status — fully conformant, partially conformant, or working toward it (be honest).
  • Known limitations — areas you know aren't there yet, and ideally when you expect to fix them.
  • How to get help / report a problem — an email or form, and a realistic response time.
  • Date — when the statement was last reviewed.

Copy-paste template

Replace the [bracketed] parts. Keep only what's true for you.

Accessibility statement for [Your Company]

[Your Company] is committed to making [yourwebsite.com] accessible to as many
people as possible, including people with disabilities.

Standard we follow
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at
Level AA.

Current status
[Choose one:]
- This website is fully conformant with WCAG 2.2 AA.
- This website is partially conformant with WCAG 2.2 AA: some content does not
  yet fully meet the standard (see "Known limitations" below).
- We are actively working toward WCAG 2.2 AA conformance.

Known limitations
We are aware of the following areas that may not yet be fully accessible, and
we are working to address them:
- [e.g. some older PDF documents are not tagged]
- [e.g. a third-party embedded widget on the pricing page]

How we test
We use a combination of automated checks and manual testing (keyboard
navigation, screen readers, zoom, and forms).

Contact us
If you encounter an accessibility barrier on [yourwebsite.com], please tell us:
- Email: [accessibility@yourcompany.com]
- We aim to respond within [X] business days.

This statement was last reviewed on [date].

Keep it honest

Don't claim "fully compliant" unless you've actually tested to that level — an overstated statement can do more harm than good. It's perfectly reasonable (and credible) to say you're partially conformant and actively improving. Update the statement whenever you make significant changes or fixes.

Check before you publish

Before you state a conformance level, see where you actually stand. Scan your site free with WCAGwise to find the machine-detectable issues and where they are in your code, then do the manual checks. When you need a documented audit across your whole site, WCAGwise Pro is coming. WCAGwise is an audit aid, not a legal guarantee.

Related guides