Website & Development
Website accessibility statement: what it must contain, with examples and a template
Copy for AI
An accessibility statement is a public page describing how accessible your website is.
It also says which parts don’t comply yet, what you’re doing about it and where visitors turn when they get stuck.
The verdict: public bodies must publish one. For companies under the European Accessibility Act, it’s the clearest way to meet the law’s information duty.
Below you’ll find who needs a statement and what goes in it. Then the website accessibility statement examples, and a template you can fill in straight away.
What is an accessibility statement?
It’s an honest status report on the accessibility of a website or app.
It isn’t a quality label. And it isn’t a promise that everything works perfectly.
It tells the visitor four things:
- which standard you follow
- to what extent you meet it
- which limitations remain
- how someone gets help
What the W3C says belongs in it
The W3C is the organisation behind the WCAG guidelines. Its guidance on accessibility statements lists three parts as a minimum:
- a commitment to accessibility
- the standard you apply
- contact details for anyone who runs into problems
Known limitations, your measures and the technical requirements are what make a statement genuinely useful. Technical requirements means things such as supported browsers.
New to the concept itself? Our wiki entry on accessibility covers the basics.
Who has to publish an accessibility statement?
That depends on who you are and what you offer.
There are two regimes, and they’re often confused:
| Government and public bodies | Companies under the European Accessibility Act | |
|---|---|---|
| Legal basis | Web Accessibility Directive (EU) 2016/2102 and national transposition | Directive (EU) 2019/882, in Belgium Book VIII of the Code of Economic Law |
| What must you publish? | An accessibility statement following a fixed model | Accessibility information about your service, in your terms and conditions or an equivalent document |
| Form | Prescribed, with a status and an audit report | Freer, but with required content |
| Who checks? | The competent government body per country or region | In Belgium the Economic Inspection of the FPS Economy |
Public bodies: a mandatory model
Government organisations must publish a statement for every website and app.
In the Netherlands, this follows a mandatory model, drawn up via digitoegankelijk.nl (in Dutch) and its form wizard.
The statement gets a status there from A (fully compliant) to E (no statement). It refers to an audit report and a plan for the open items.
Belgian public bodies also work with a fixed model that refers to the EN 301 549 standard.
Companies: accessibility information under the EAA
Companies covered by the European Accessibility Act have no mandatory model. Think of webshops and consumer banks.
The directive (Directive (EU) 2019/882, Annex V) does require you to explain publicly how your service meets the accessibility requirements.
The Belgian FPS Economy makes this concrete in its guidelines for accessible e-commerce services (in Dutch).
In your terms and conditions or an equivalent document, such as an accessibility statement, you must always:
- give a general description of the service
- explain how the service works
- state how you apply the accessibility requirements
The FPS adds that you should explain both the possibilities and the limitations.
And this information must itself be accessible for as long as the service exists.
Whether you fall under the law, and which transition periods apply, is covered in our article on the European Accessibility Act.
Why a B2B site might publish one anyway
Some clients and tenders ask about accessibility.
A clear statement answers that question before it’s asked. Our piece on the European Accessibility Act and lead generation explains the commercial side.
What belongs in an accessibility statement?
Ten parts, of which the first six are the practical minimum for a company under the EAA.
Combine the legal information duty with what the W3C recommends and you arrive at this:
The practical minimum
- Scope. Which website, subdomains or apps does the statement cover?
- Description of the service. What can a visitor do, and how does it work: search, order, pay, return?
- Standard applied. Usually WCAG 2.1 level AA, the standard incorporated in the European standard EN 301 549. If you already build to WCAG 2.2, say so.
- Compliance status. Fully, partially or not compliant, with a short explanation.
- Known limitations. Which parts don’t comply yet, why, which alternative you offer meanwhile and when it’ll be fixed.
- Contact and follow-up. Where someone reports a problem (email, phone, form), who follows up and how fast you respond.
What makes it credible
- How you tested. An internal review, an external audit, automated tools and manual tests, with the date of the last test.
- Technical requirements. Which technologies the site relies on (HTML, CSS, JavaScript) and which browsers and assistive software you tested with.
- Date. When the statement was drawn up and last updated.
- Complaints route. Where someone can go if you don’t respond. In Belgium, for webshops and banking services, that’s the Economic Inspection of the FPS Economy.
Accessibility statement examples
Three passages, each showing what a good section looks like in practice.
We wrote them for an imaginary webshop. They aren’t copied from an existing site.
Example: a known limitation in a “partially compliant” statement
Product videos published before June 2025 do not have captions yet. Each video has a written description of the product on the same page. We will add captions to all product videos by March 2027.
Why it works: it names the exact problem, offers an alternative today and commits to a date.
Example: a contact block that actually helps
Can’t complete an order or find the information you need? Email accessibility@ourshop.example or call +32 3 000 00 00 (weekdays 9:00 to 17:00). We confirm your message within two working days and help you place your order another way if needed.
Why it works: two channels, opening hours, a response time and a concrete promise. A general info address does none of that.
Example: a description of how you tested
Last review: 14 September 2026, by our own web team. We used automated checks on all page templates and tested the full order process manually with keyboard only, NVDA on Firefox and VoiceOver on Safari for iOS.
Why it works: a visitor can see how recent and how thorough the claim is.
Where to see real statements
The W3C publishes a free statement generator that shows the same structure:
Tip: compare the generator’s output with your terms and conditions. Both must tell the same story.
Template: accessibility statement for a company website
This template is meant for a private website or webshop.
Replace everything in square brackets and delete what doesn’t apply to you. Have the final text checked by your lawyer if in doubt, especially if you fall under the EAA.
Accessibility statement
[Company name] wants everyone to be able to use [website address],
including people with a visual, auditory, motor or cognitive
disability.
Which website does this statement cover?
This statement covers [website address] and [any subdomains or apps].
What can you do on this website?
On this website you can [view, order and pay for products / book an
appointment / manage an account]. [Short description of the process:
search, basket, checkout, returns.]
Which standard do we follow?
We test this website against the Web Content Accessibility Guidelines
(WCAG) 2.1, level AA, as incorporated in the European standard
EN 301 549.
How accessible is the website?
This website is [fully / partially / not] compliant with WCAG 2.1
level AA. [Short explanation.]
What does not work yet?
- [Part]: [problem]. Alternative: [for example ordering by phone or
email]. Planned fix: [month and year].
- [Part]: [problem]. Alternative: [...]. Planned fix: [...].
How did we test?
Last review on [date], by [our own team / an external party], using
automated tools and manual tests with keyboard and screen reader on
[browsers and assistive software].
Stuck?
Report it via [email address], [phone number] or [form]. We confirm
your report within [number] working days and look for a solution
together.
Not satisfied with our response?
[Belgium, webshops and banking services:] You can file a complaint
with the Economic Inspection of the FPS Economy.
This statement was drawn up on [date] and last updated on [date].
Where to publish it
Put the statement on its own page, for example /accessibility/.
Link to it from your website footer so it’s reachable from every page. Refer to it from your terms and conditions as well.
It sits next to the other mandatory website pages, such as your privacy policy and legal notice.
Watch out: make the page itself accessible. Real headings, a readable font size and no PDF as the only version.
Which mistakes do you see often?
Most statements don’t fail on form. They fail on credibility.
These are the patterns we come across most often.
A copied text without a test behind it
A statement claiming “fully compliant” while the contact form has no labels undermines trust.
It does so faster than an honest “partially”.
No working contact point
A general info address that nobody follows up isn’t a reporting channel.
Say who follows up, and within what time.
Limitations without a plan
Naming open items is fine. But without an alternative and a date, it’s an excuse.
Never updated
After a redesign, a new payment module or a new theme, last year’s statement is no longer accurate.
Add the statement to your website maintenance routine, so a review happens with every release.
An overlay as proof
Mentioning an accessibility plugin as if it guarantees compliance is misleading.
Plugins rarely solve structural problems in your code.
How do you gather the information for your statement?
You only write a statement once you know where you stand.
That takes two kinds of test, an automated scan and a manual check.
Step 1: Run a quick automated scan
Start with your most important pages. Our WCAG checker shows the automatically detectable errors.
For example, scan your homepage, a product page and a form.
Step 2: Add a manual test
Automated tools only catch part of the problems. So test by hand:
- navigate using only the keyboard
- let a screen reader read out your order process
- zoom in to 200 percent
What each WCAG criterion means, and who in your team owns it, is in our WCAG 2.1 AA checklist.
Step 3: Turn findings into your “What does not work yet?” list
The limitations you find become that list in your statement.
Plan the fixes following the step-by-step plan in our guide to website accessibility for your existing site.
Rule of thumb: every limitation gets an alternative and a month. No month, no entry.
Frequently asked questions
Is an accessibility statement mandatory for companies?
Not as a separate document. Companies under the European Accessibility Act must, however, describe publicly how their service works and how they apply the accessibility requirements, in their terms and conditions or an equivalent document. An accessibility statement is the most common and clearest form for that.
Can I use a generator?
Yes, as a starting point. The W3C offers a free accessibility statement generator, and Dutch public bodies use their own form wizard. A generator creates the structure, but the content (status, limitations, contact) has to come from your own test.
How often should I update the statement?
At least once a year, and immediately after every major change to your website, such as a redesign, a new theme or a new payment module. Show the date of the last update visibly at the bottom.
What if my site is not compliant yet?
Then write that down honestly. A statement with the status “partially compliant”, a list of known limitations, alternatives and planned dates is more credible than a promise that is too good to be true, and shows you are taking accessibility seriously.
The short summary
An accessibility statement tells visitors honestly how accessible your site is, what doesn’t work yet and where to turn.
Public bodies follow a mandatory model. Companies under the EAA describe how their service works and how they apply the requirements.
Use the examples and the template above, fill them in from a real test, and update after every major change.
Want to know where your website stands today? See how we handle the audit, the fixes and the statement on our WCAG compliance page, or contact us.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.