Accessibility guide

How to Write an Accessibility Statement

An accessibility statement is a public page that explains how accessible your website or service is, what is not yet accessible, and how someone can report a problem. For public-sector bodies it is a legal requirement; for everyone else it is good practice that also reduces legal risk. This guide explains when you need one and exactly what to put in it.

Reviewed by the EAA Navigator team

TL;DR

  • An accessibility statement sets out your compliance status, known accessibility problems, and how users can get help or report a barrier.
  • It is mandatory for public-sector bodies under the EU Web Accessibility Directive (2016/2102), using the EU model statement and updated at least once a year.
  • Under the EAA, service providers must make accessibility information available, which a statement helps deliver.
  • A clear statement with a working feedback route also reduces ADA litigation risk, because it shows good faith and gives users a way to raise issues.
Get the WCAG ChecklistBrowse all guides

In this guide

What this covers

  • What an accessibility statement is and why it exists.
  • When it is legally required: the public-sector obligation under the Web Accessibility Directive, and the EAA duty to make accessibility information available.
  • The specific elements a statement should contain.
  • How the public-sector model statement is structured and how to adapt it for a private business.

What matters

What to include

  • Compliance status: state whether the site is fully compliant, partially compliant or non-compliant with the relevant standard (WCAG 2.1 AA via EN 301 549).
  • Known issues: list the non-accessible content, with the reason, and note any exemption or disproportionate-burden claim you rely on.
  • A feedback mechanism: a clear way for users to report accessibility problems and request information in an accessible format.
  • An enforcement or escalation contact: who to approach if a user is not satisfied with the response.
  • How and when the statement was prepared: the assessment method (self-assessment or third-party audit) and the date, with at least annual review for public-sector bodies.

Across web accessibility, Level AA of WCAG 2.2 is the working target, and for the EU it is incorporated into the harmonised standard EN 301 549.

What to do

What to do next

  1. Test your site against WCAG 2.1 AA so you can state an honest compliance status rather than guessing.
  2. Start from the EU model accessibility statement structure if you are a public-sector body, or adapt it if you are a private service provider.
  3. Write the compliance status, the list of known non-accessible content, and the reasons or exemptions in plain language.
  4. Add a working feedback route and a named escalation or enforcement contact, and make sure someone monitors it.
  5. Date the statement, record the assessment method, and set a reminder to review it at least annually or whenever the site changes materially.

For the standard itself, see the WCAG explainer; to put it into practice, work through the WCAG 2.2 AA checklist.

FAQ

Common questions

Is an accessibility statement legally required?
For public-sector bodies in the EU, yes — the Web Accessibility Directive (2016/2102) requires a statement using the EU model, kept up to date and reviewed at least annually. For private businesses it is not always a standalone legal requirement, but the EAA expects service providers to make accessibility information available, and a statement is the usual way to do that.
What should an accessibility statement contain?
At a minimum: your compliance status against the relevant standard, a list of known non-accessible content with reasons or exemptions, a feedback mechanism for users to report problems or request accessible formats, an enforcement or escalation contact, and the date and method of assessment.
How often should I update it?
Public-sector bodies must review their statement at least once a year and whenever the site changes significantly. For everyone else, the same cadence is sensible: an out-of-date statement that claims compliance you no longer meet can do more harm than good.
Does an accessibility statement make my site compliant?
No. A statement describes your accessibility; it does not create it. Publishing a statement that claims full compliance without testing can increase risk. Test first, then state honestly what is and is not accessible.

Make your site accessible

Start with the WCAG 2.2 AA checklist, then work through the guides to fix what you find.

Get the WCAG ChecklistTry the contrast checker

This is guidance, not legal advice

This guide is here to help you understand web accessibility and how WCAG, the EAA and the ADA apply in practice. It is not legal advice. For decisions specific to your business, confirm with the official sources we link or a qualified adviser.

Sources

  1. [1]Web Content Accessibility Guidelines (WCAG) 2.2 (W3C Recommendation)retrieved 9 Jun 2026
  2. [2]WCAG overview (W3C Web Accessibility Initiative)retrieved 9 Jun 2026
  3. [3]Directive (EU) 2019/882 — European Accessibility Act (EUR-Lex)retrieved 9 Jun 2026
  4. [4]EN 301 549 v3.2.1 — harmonised ICT accessibility standard (ETSI)retrieved 9 Jun 2026
  5. [5]US DOJ ADA Title II web accessibility rule fact sheetretrieved 9 Jun 2026
  6. [6]WebAIM Million 2025 — accessibility of the top 1,000,000 home pagesretrieved 9 Jun 2026
  7. [7]Overlay Fact Sheet — why overlays do not deliver complianceretrieved 9 Jun 2026

The Accessibility Brief

Subscribe to The Accessibility Brief

We watch the standards so you don't. Plain-English WCAG, EAA and ADA updates, free.

No spam. Unsubscribe anytime.

How to Write an Accessibility Statement (with checklist) | EAA Navigator · EAA Navigator