Accessibility statement: who needs one and what to include
Under the European Accessibility Act, many businesses provide information about how accessible their service is. What belongs in it, who needs one — and why it isn’t the same as the detailed statement required of public-sector bodies.
What is an accessibility statement?
An accessibility statement describes how accessible a website, online shop or app is. It makes transparent to your users how your service can be accessed and is provided in an easy-to-find place — much like an imprint or privacy policy. One important detail: the statement itself must be accessible.
The statement isn’t a marketing badge. At its best it’s a useful, honest summary: what you’ve done for accessibility, how people can use the accessible features, and how they can reach you if something doesn’t work for them.
Who needs an accessibility statement?
The obligation applies to providers of services that fall under the European Accessibility Act — in particular e-commerce (online shops and bookable services), banking, electronic communications, passenger transport and e-books. Microenterprises offering services (fewer than 10 employees and no more than €2 million in annual turnover) are generally exempt.
The exact requirements are set by each country’s implementing law (in Germany, for example, the BFSG), so the precise wording and obligations can vary by market. Unlike the public sector, the private sector usually needs one statement, not one per page. (Not legal advice — check your specific situation.)
What should an accessibility statement include?
Requirements differ by country, but in essence a private-sector statement should contain:
- a general description of how your service meets the accessibility requirements,
- a reference to the technical benchmark (the WCAG and the EN 301 549 standard),
- information that helps your users understand and use the accessible features,
- a way to get in touch — a feedback channel for accessibility problems.
Place the statement where people can find it easily — for example linked alongside your imprint and privacy policy — and make sure it’s accessible itself.
Why a private statement isn’t the public-sector one
This is where confusion often starts. Public-sector bodies fall under the EU Web Accessibility Directive (2016/2102) and must publish a detailed statement following a set template — which, among other things, lists non-accessible content. The statement that private businesses provide under the EAA is deliberately leaner.
The practical takeaway: don’t put yourself in the pillory by publicly cataloguing where you fall short. Describe how you meet the requirements instead, and keep a channel open for feedback. If you’re unsure what your national law requires, get it checked.
How to create your accessibility statement
- Check whether your offering falls under the EAA (and your national implementing law).
- Assess the state of your accessibility (for example against the WCAG).
- Describe in the statement how your service meets the requirements — factually and accurately.
- Publish it where it’s easy to find, and make sure it’s accessible.
Welcoma’s statement generator gives you a draft to start from, which you adapt to your actual situation. Honestly: the generator takes the writing off your plate, but it replaces neither a real assessment of your site nor — if you’re unsure — a legal review. For WordPress: accessibility plugin for WordPress.
Accessibility statement — frequently asked questions
Do I need an accessibility statement?
If your offering falls under the EAA (for example an online shop), generally yes. Microenterprises offering services are usually exempt. Requirements vary by country — not legal advice.
What must the statement include?
A general description of how your service meets the accessibility requirements, a reference to the technical standard (WCAG / EN 301 549), and a way to get in touch. It must be easy to find and accessible itself.
Is a private statement the same as the public-sector one?
No. Public-sector bodies follow the EU Web Accessibility Directive with a detailed template that lists non-accessible content. The private-sector statement under the EAA is leaner and should describe how you meet the requirements.
Where should the statement go?
Somewhere clearly visible and easy to find — similar to an imprint or privacy policy — and it must be accessible itself.
Do I need a separate statement for every page?
No. In the private sector, one statement is generally enough — unlike for public-sector bodies.
Does Welcoma help create it?
Yes. The statement generator creates a draft to start from. You should adapt the content to your actual situation and, if unsure, have it reviewed legally.
How accessible is your site?
Enter your URL and get an honest overview of your accessibility — free and with no obligation.