Guide · reviewed 2026-11-03
What is an accessibility statement, and what should it contain?
An accessibility statement is a page on your site that says how accessible the site is, which standard you aim for (usually WCAG 2.2 AA), what you know does not work yet and when it will be fixed, and how people can report a barrier or get the content another way. EU public sector sites must follow a model statement set by the European Commission, and it is a good template for anyone. Raasta’s free accessibility statement generator writes one from a short form.
Who needs one
Public sector websites and apps in the EU must publish a statement under the Web Accessibility Directive, using the Commission’s model. The European Accessibility Act asks service providers to explain how their service meets the accessibility requirements, in their terms and conditions or in another easy-to-find way; an accessibility statement is the usual place for this. Outside these laws, a statement is still good practice: it shows you take accessibility seriously and gives people a way to tell you about problems.
What the EU model statement contains
- Compliance status. Whether the site is fully, partially or not compliant with the standard (EN 301 549, which builds on WCAG).
- Non-accessible content. What does not meet the standard and why: a failure you have not fixed yet, a disproportionate burden, or content outside the law’s scope. Say what alternatives are available.
- How the statement was prepared. The date it was written or last reviewed, and the method: a self-assessment or a review by a third party.
- Feedback and contact. How to report a barrier or ask for content in another format, with an email address or form.
- Enforcement procedure. For public sector bodies, a link to the national body to complain to if the response is not satisfactory.
Writing a good one
Be honest and specific. “Some older PDFs are not accessible; we will replace them by March, and you can ask for any of them by email” is more useful than a claim of full compliance. Base it on real testing (an automated scan such as Raasta’s free quick scan, plus keyboard and screen reader checks), date it, and review it at least once a year or after a redesign. Do not claim that a tool or widget has made the site compliant.
Link to the statement from every page, usually in the footer, and answer reports promptly.
See the common failures and their fixes, the WCAG 2.2 guide or the accessibility statement generator.
Questions
Does publishing a statement make my site compliant?
No. It describes where the site stands; the site still has to meet the requirements. An honest statement with a plan is better than an inaccurate claim.
Can I say my site is fully compliant after an automated scan?
No. Automated checks find a large share of problems, not all. Full compliance needs a manual review against every applicable criterion.
Where should the statement go?
On its own page, linked from the footer of every page, with a clear title such as “Accessibility”.
Does Raasta’s generator send my answers anywhere?
No. The generator runs in your browser and nothing you type leaves it. Copy the result into your site.