Your website needs an accessibility statement. Here is what it must say.
Since the European Accessibility Act applies, publishing an accessibility statement is a legal requirement for in-scope services - not a voluntary badge. A compliant statement describes how your service meets the accessibility requirements, lists known issues and a plan to fix them, and is reviewed and updated at least once a year.
Real scan evidence · Documented PDF · Annex V statement you can publish
The parts of a compliant accessibility statement
A statement must be produced and made publicly available in an accessible form. Regulators look for a statement that is honest, specific and current. The core parts are:
- The conformance level reached - a clear statement of which accessibility requirements you meet (typically EN 301 549 / WCAG 2.x AA), and the assessment basis (a self-assessment, an automated scan, or a full evaluation).
- Known issues and a remediation timeline - the specific accessibility problems still present and when you plan to fix them. A statement that claims full compliance while issues exist is a liability.
- Last review date - when the statement was last assessed and updated. Regulators treat an out-of-date assessment date as a formal defect, however accessible the site actually is.
- A way to report problems - a directly reachable contact so users can tell you about barriers and ask for alternatives.
- Disproportionate burden - if you rely on the disproportionate-burden exception for any part, you must state it and justify it in the statement; authorities can review it.
Public-sector bodies follow the EU model statement (Implementing Decision 2018/1523) and are held to stricter form requirements: an accessible, ideally machine-readable format, reachable from every page, and updated at least once a year. For private EAA services the substance above is the reliable baseline.
Do not write a statement you cannot back up
The assessment basis you cite in your statement should be real. Market-surveillance authorities can ask you to substantiate what you claim. That is where an automated scan is the right first step: it gives you objective, dated evidence of the violations on your site, a score you can track against over time, and the specific list you need for the "known issues" section of your statement.
An automated scan detects machine-testable WCAG criteria (structure, alt text, colour contrast, form labelling, keyboard operability, ARIA). It does not replace manual testing of everything a human must verify - so a strong statement pairs the scan with human review.
Scan your site and build the statement on facts
Run a free automated scan to see your current score and violations. The €19 report turns that into a documented PDF with a prioritised fix plan and a ready-to-publish Annex V accessibility statement - the conformance level, the issue list, the review date and the feedback contact, written from your actual scan results.
The free scan is an automated pre-check. The report adds a documented PDF, fix plan and Annex V statement. See pricing.