Accessibility statement: example + how to write one

Q: Is an accessibility statement required?

For public-sector bodies in the EU a statement has been mandatory for years, in a fixed model (the Web Accessibility Directive 2016/2102). In the US, federal agencies face a comparable expectation under Section 508. For private companies in the EU, the European Accessibility Act has applied since 28 June 2025: it requires you to provide information on how your service meets the accessibility requirements, and a published accessibility statement is the most common and most defensible way to do that. Under the ADA in the US there's no single mandated template, but a clear statement with a feedback route is widely treated as good practice. Whether — and in what exact form — the obligation applies to your situation depends on your jurisdiction and your size; this is information and tooling, not legal advice.

Q: How do I make an accessibility statement?

In six steps: 1. Measure first. You can't invent your compliance status or your known issues — they come out of a test. Scan your site and note what's wrong. 2. Determine your status. No open issues → "compliant". A handful open → "partially". Many or fundamental issues → "not" (with a plan attached). 3. Describe the issues plus an alternative. For each open point: what, why, and how you still help the visitor. 4. Add a contact and reporting route. A real email address or form that someone reads — not a dead end. 5. Date it and publish. Add the date and link the page from your footer so it's findable on every page. 6. Review periodically. A statement is a snapshot; your site changes. Schedule a review (see below).

Q: Can I generate an accessibility statement with AI or an overlay widget?

Having AI draft the text of a statement is fine — but the compliance status in it must rest on a real measurement, not a guess. An AI that hasn't actually tested your site can't possibly know whether you "comply". And be careful with overlay widgets that ship a ready-made "this site is accessible" badge or statement: that's precisely the kind of untrue claim that gets sites sued. A statement is a promise on paper; regulators and courts look at the real source code underneath. See why a widget won't protect you in I already have an accessibility widget — am I covered?.

9 juni 2026

Short answer. An accessibility statement is a short, public page where you set out how well your website meets the accessibility standard (WCAG 2.1 AA / EN 301 549), which parts aren't right yet, and how a visitor can report a problem. Below is an example you can copy, plus the steps to fill it in for your own site. The key point: a statement is only credible if the status in it is true — so measure first, then declare.

What is an accessibility statement?

It's a dedicated page on your website — usually linked from the footer — where you make three things public: (1) that you intend to make your site accessible, (2) how well it currently meets the standard, and (3) where a visitor can turn if they still run into something. It is not a seal or a certificate you award yourself: it's an honest status plus a contact route. That honesty is exactly what makes it strong — a statement claiming "100% accessible" when that isn't true works against you.

Is an accessibility statement required?

For public-sector bodies in the EU a statement has been mandatory for years, in a fixed model (the Web Accessibility Directive 2016/2102). In the US, federal agencies face a comparable expectation under Section 508. For private companies in the EU, the European Accessibility Act has applied since 28 June 2025: it requires you to provide information on how your service meets the accessibility requirements, and a published accessibility statement is the most common and most defensible way to do that. Under the ADA in the US there's no single mandated template, but a clear statement with a feedback route is widely treated as good practice. Whether — and in what exact form — the obligation applies to your situation depends on your jurisdiction and your size; this is information and tooling, not legal advice.

What should an accessibility statement contain?

These six elements form the commonly accepted model (taken from the EU public-sector model, equally usable by businesses):

Scope — which website, app or store it covers.
Compliance status — whether the site fully, partially, or does not meet WCAG 2.1 AA / EN 301 549. Be honest here; "partially" is a normal and credible answer.
Known issues — which parts aren't accessible yet, why, and what alternative you offer (for example: "a PDF form isn't screen-reader friendly; call or email us and we'll help you directly").
Date and assessment method — when you wrote the statement, how you tested (self-assessment with tooling, or a full audit) and when you last reviewed it.
Feedback option — an email address or form where visitors can report an accessibility problem.
Next step — what a visitor can do if they're not satisfied with your response.

An example accessibility statement

Copy this and replace the bracketed text with your own details:

Accessibility statement for [company name]

[Company name] wants everyone to be able to use [website URL], including visitors who rely on assistive technology such as a screen reader, keyboard navigation or magnification. We aim to meet the WCAG 2.1 level AA standard (EN 301 549).

Compliance status. This website partially meets WCAG 2.1 AA. That means most of it is in order, but we're still improving a number of points.

Known issues. [Describe, point by point, what isn't right yet and what alternative you offer. For example: "Some older product photos still lack alt text; we're adding these gradually." If everything is in order, write: "We're not currently aware of any issues."]

Prepared and tested. This statement was prepared on [date] based on a [self-assessment with automated tooling / external audit]. We review it at least once a year and after major changes to the site. Last reviewed on [date].

Reporting a problem. Run into something anyway? Email us at [email address] or call [phone number]. Briefly describe the page and what went wrong, and we'll find a solution — and where needed, provide what you were after in another way straight away.

How do I make an accessibility statement?

In six steps:

Measure first. You can't invent your compliance status or your known issues — they come out of a test. Scan your site and note what's wrong.
Determine your status. No open issues → "compliant". A handful open → "partially". Many or fundamental issues → "not" (with a plan attached).
Describe the issues plus an alternative. For each open point: what, why, and how you still help the visitor.
Add a contact and reporting route. A real email address or form that someone reads — not a dead end.
Date it and publish. Add the date and link the page from your footer so it's findable on every page.
Review periodically. A statement is a snapshot; your site changes. Schedule a review (see below).

How often should I update the statement?

At least once a year, and always after a major change to your site — a new theme, a new checkout, a large content migration. That's exactly the hard part: every release can introduce a new issue, and a statement that's no longer accurate is worse than none. Continuous monitoring solves this — you know immediately when something changes that belongs in your statement. More on proving accessibility to a regulator in how to prove your accessibility to a regulator.

Having AI draft the text of a statement is fine — but the compliance status in it must rest on a real measurement, not a guess. An AI that hasn't actually tested your site can't possibly know whether you "comply". And be careful with overlay widgets that ship a ready-made "this site is accessible" badge or statement: that's precisely the kind of untrue claim that gets sites sued. A statement is a promise on paper; regulators and courts look at the real source code underneath. See why a widget won't protect you in I already have an accessibility widget — am I covered?.

How do I know what should go in my statement?

The content follows directly from a measurement: your compliance status and your list of known issues are exactly what a scan produces. Scan one page for free — you'll see, per finding, what's wrong and how to fix it, and that gives you the building blocks for an honest, defensible statement. In under 60 seconds, no account needed.