Free Accessibility Statement Generator
The European Accessibility Act requires service providers to publish information on how their product or service meets accessibility requirements. Fill in the details below and get a ready-to-use statement — including the correct enforcement authority and complaint procedure for whichever of our 27 countries you pick, pulled from the same sourced dataset as the rest of this site. Free, no email required.
Your statement
This is a starting point, not legal advice — it's only accurate if it reflects how your service actually works. Wording a statement correctly doesn't make a service accessible; verify the underlying claims before you publish it, and check the official source linked on the relevant country page for anything that matters.
A statement is a claim — check it holds
Wording a statement correctly doesn't make a service accessible. Run the same URL through the scanner to see what an automated WCAG audit actually finds before you publish this. Analyze your website →
What the EAA actually requires you to publish
Most generators produce a page and stop there. It is worth knowing what the law asks for, because the obligation has a shape that a page alone does not entirely fill.
Article 13(2) of Directive (EU) 2019/882 requires a service provider to prepare the information set out in Annex V, to explain how the service meets the applicable accessibility requirements, to make that informationavailable to the public in written and oral format, including in a manner accessible to persons with disabilities, and tokeep it for as long as the service is in operation.
Annex V places that information in the general terms and conditions, or an equivalent document. It must describe the applicable requirements and cover the design and the operation of the service, and where applicable it includes a general description of the service in accessible formats, the descriptions and explanations needed to understand how the service works, and a description of how the relevant accessibility requirements in Annex I are met.
This is not the public sector statement
The template accessibility statement most people have seen comes from a different law: Directive (EU) 2016/2102, the Web Accessibility Directive, which covers public sector websites and mobile apps and has its own harmonised model. If you searched for an accessibility statement and found a form asking which public body you work for, that is why.
The EAA covers private-sector services, including e-commerce, consumer banking, e-books, telecommunications and passenger transport information. Its information obligation is the one above. The two overlap in spirit and differ in detail, and a statement written to the public sector template can leave out things the EAA asks for.
Two requirements people miss
- Oral format. The information has to be available orally as well as in writing. If you run a support line, the people answering it should be able to explain your accessibility position and where to complain. A page nobody internally has read does not meet this.
- For as long as the service operates. The statement is not a launch artefact. It has to stay available, and to stay true it has to be revisited when the service changes. A statement dated three redesigns ago works against you rather than for you.
What this generator fills in for you
The part of a statement that generic tools get wrong is the national detail, because it differs across all 27 member states and it changes. For the country you pick, the generator inserts the national law that transposes the EAA, the enforcement authority that supervises it, and the complaint route a dissatisfied customer can use, from the same sourced dataset as the rest of this site. Where an authority or a figure is not confirmed against an official source, the statement says so instead of inventing one, and points at thecountry page where the current status is tracked.
What a statement does not do
It does not make a service accessible, and publishing one does not reduce your obligations. What it does is put a claim about your service in public, which is the sort of thing a supervising authority reads first and a complainant quotes back. That cuts both ways: an honest partial statement listing known issues and a plan is defensible, while a claim of full conformance that fails on the home page is worse than having published nothing. Run a scan before you publish one.
Accessibility statements and the EAA: common questions
- Does the European Accessibility Act require an accessibility statement?
- It requires information, and it is specific about the form. Article 13(2) obliges service providers to prepare the information set out in Annex V, explain how the service meets the applicable accessibility requirements, make it available to the public in written and oral format including in a way accessible to persons with disabilities, and keep it for as long as the service is in operation. Annex V places that information in the general terms and conditions or an equivalent document. A published statement page is the usual way to satisfy this, and on its own it does not cover the oral-format obligation.
- Is this the same accessibility statement as the one public sector bodies publish?
- No, and mixing the two up is common. The familiar template statement comes from Directive (EU) 2016/2102, the Web Accessibility Directive, which applies to public sector websites and apps and has its own harmonised model statement. The EAA is a separate law covering private-sector services such as e-commerce, consumer banking, e-books and transport information, and its information obligation is shaped differently.
- Where should the statement go on my website?
- Annex V points at the general terms and conditions or an equivalent document, so the safe pattern is to publish it as its own page, link it from the footer on every page, and reference it from your terms. Putting it only inside a PDF of the terms is a poor fit for the requirement that the information itself be accessible.
- What does written and oral format mean in practice?
- Article 13(2) requires the information to be available to the public in both. In practice that means the content of your statement has to be something your customer support can explain over the phone, not only a page someone can read. If you operate a support line, the people answering it need to know what your accessibility position is.
- Can I say my site is fully conformant if I have not tested it?
- You should not. The statement is a public claim about your service, made to consumers and to the authority that supervises you. Declaring partial conformance and listing the known issues is permitted and more defensible than a claim of full conformance that does not survive a first audit.
Sources: Directive (EU) 2019/882 (European Accessibility Act), Article 13 and Annex V; Directive (EU) 2016/2102 (Web Accessibility Directive), the public sector statement this is often confused with. The national law, enforcement authority and complaint route come from our country dataset, each entry carrying its own official source.
This page explains the general requirement and is not legal advice. A statement is only accurate if it reflects how your service actually works.