Accessibility Statement: What It Is and How to Write One

Your privacy policy tells visitors how you handle their data. Your cookie banner explains what you track. An accessibility statement does something similar: it tells people what you've done to make your website usable for everyone, and what to do if something doesn't work.

If your business falls under the European Accessibility Act (EAA), you're required to publish one. But even if you're exempt, having an accessibility statement is a smart move. It shows you care about your visitors and gives people with disabilities a way to reach you when they hit a barrier.

What an accessibility statement actually does

An accessibility statement is a page on your website. It describes your accessibility efforts, names the standard you're working toward and gives visitors a way to report problems.

Think of it as a commitment in writing. You're saying: "We've done this work. We know about these gaps. Here's how to tell us if something isn't working for you."

It's not a legal shield. Publishing one doesn't protect you from complaints if your site is full of barriers. But it does show good faith, and regulators take that into account.

Who needs one

The EAA requires businesses in scope to publish an accessibility statement. That includes e-commerce sites, banking services, telecom providers and transport services, among others. If you're not sure whether the EAA applies to you, read our guide on the EAA and small businesses.

Even if you're a microenterprise (fewer than 10 employees, under €2 million turnover) and exempt from the EAA, publishing an accessibility statement still makes sense. It costs nothing. It takes 30 minutes. And it gives people a clear way to contact you if they can't use part of your site.

What to include

A good accessibility statement covers six things. Here they are.

1. Conformance status

State which accessibility standard you're following and how well you meet it. The standard for most websites is WCAG 2.1 Level AA. Be honest about where you stand. You can say:

• Fully conformant — your site meets the standard with no known issues
• Partially conformant — your site meets most of the standard but has some gaps
• Non-conformant — your site doesn't yet meet the standard (but you're working on it)

Most small business websites will be "partially conformant" and that's fine. What matters is honesty. Claiming full conformance when your site has known issues will backfire if someone files a complaint.

2. Known limitations

List the parts of your site that aren't fully accessible yet. Be specific. "Some images lack alt text" is more useful than "we're working on improvements." If you know which pages have issues, name them.

This section shows you've actually tested your site rather than just copying a template and calling it done.

3. Feedback mechanism

Give visitors a clear way to report accessibility problems. An email address works. A contact form works too, as long as the form itself is accessible. Include:

• An email address or link to a contact form
• Expected response time (e.g. "We'll respond within 5 business days")
• What happens after someone reports a problem

This is the most important part. Without a feedback channel, the statement is just decoration.

4. Enforcement procedure

If you're covered by the EAA, include information about the national enforcement body. In the Netherlands, this is the Dutch Human Rights Institute (College voor de Rechten van de Mens). Visitors should know where to go if you don't respond to their feedback.

5. Technical information

Mention which technologies your site relies on (HTML, CSS, JavaScript, PDF) and which browsers and assistive technologies you've tested with. You don't need to list every screen reader on the market. Just be transparent about what you've checked.

6. Date

Include the date the statement was written or last updated. A statement from 2021 on a site redesigned in 2025 isn't credible. Review and update yours at least once a year.

Template you can adapt

Here's a starting point. Replace the bracketed text with your own details.

---

Accessibility Statement for [Your Company Name]

[Your Company Name] is committed to making [website URL] accessible to all visitors, including people with disabilities.

Conformance status

This website aims to conform to WCAG 2.1 Level AA. We are currently [fully conformant / partially conformant / non-conformant] with this standard.

Known limitations

We are aware of the following accessibility issues:

• [Describe issue 1, e.g. "Some product images do not have descriptive alt text"]
• [Describe issue 2, e.g. "The booking calendar is difficult to use with keyboard navigation"]
• [Describe issue 3, if applicable]

We are actively working to fix these issues by [target date or "on an ongoing basis"].

Feedback

If you encounter an accessibility barrier on this website, please contact us:

• Email: [your email]
• Phone: [your phone number]
• Postal address: [your address]

We aim to respond to accessibility feedback within [5] business days.

Enforcement

If you are not satisfied with our response, you can contact [your national enforcement body, e.g. "the Dutch Human Rights Institute (College voor de Rechten van de Mens) at mensenrechten.nl"].

Technical specifications

This website relies on HTML, CSS and JavaScript. It has been tested with [browser names] and [assistive technology names, e.g. "NVDA screen reader"].

Date

This statement was last updated on [date].

---

Where to put it

Add a link to your accessibility statement in your website footer, right next to your privacy policy and terms of service. Label the link "Accessibility" or "Accessibility Statement." Don't bury it in a submenu.

The footer is where visitors expect to find this kind of page. If someone using a screen reader needs to find your accessibility contact info, the footer is the first place they'll look.

Common mistakes to avoid

Claiming full compliance when you're not. This is the biggest one. If a regulator checks your site and finds issues you claimed didn't exist, it looks far worse than admitting you have gaps. Be honest about your conformance status. "Partially conformant" with a plan to improve is perfectly acceptable.

No contact information for feedback. A statement without a way to report problems is pointless. The whole purpose is to give people a channel. Include at least an email address.

Using a generic template without customizing it. A statement that says "[insert company name]" or includes placeholder text hurts your credibility. Take ten minutes to fill in the details properly.

Never updating it. Your website changes over time. New pages, new features, new plugins. Review your statement at least once a year and update the date.

Making the statement page itself inaccessible. This happens more often than you'd think. If your accessibility statement can't be read by a screen reader, you have a problem. Keep the page simple: plain text, proper headings, no decorative clutter.

What to do next

Writing an accessibility statement is a good start, but it works best alongside actual accessibility improvements. If you haven't tested your site yet, run a free scan to see where you stand. For quick fixes you can make today, check out our guide to quick accessibility wins.

And if you're wondering what happens when enforcement authorities come knocking, read our breakdown of EAA penalties and what they mean in practice.

The statement won't fix your site's issues. But it shows you're paying attention, and it gives real people a way to tell you what's broken. That's worth 30 minutes of your time.

FAQ

Is an accessibility statement legally required?

It depends on your business. If you fall under the European Accessibility Act, yes. Microenterprises (fewer than 10 employees, under €2 million turnover) providing services are currently exempt from the EAA. But even exempt businesses benefit from having one. Check our EAA small business guide to see if you're in scope.

Can I just copy a template from the internet?

You can use a template as a starting point, but you need to customize it. Fill in your actual company details, your real conformance status and your known issues. A generic copy-paste job with placeholder text will hurt your credibility and won't satisfy regulators if they check.

How often should I update my accessibility statement?

At least once a year. Also update it after major website changes like a redesign, a new e-commerce platform or adding new functionality. The date on the statement should reflect when you last reviewed it.

Does publishing a statement protect me from fines?

Not on its own. A statement doesn't replace actual compliance work. But it does show good faith. Enforcement authorities typically consider whether a business has acknowledged its obligations and is making genuine efforts to improve. A well-maintained statement with a working feedback channel helps your case.

What's the difference between an accessibility statement and a VPAT?

A VPAT (Voluntary Product Accessibility Template) is a detailed technical document used mainly in procurement, especially in the US. An accessibility statement is a simpler public-facing page for website visitors. Most EU small businesses need an accessibility statement, not a VPAT.