EAA accessibility statement: template and real example
Under the European Accessibility Act and its national implementations, publishing an accessibility statement is one of the most concrete, low-cost things a small online shop can do — and one of the first things a regulator or auditor will look for. It won't make your site compliant by itself, but its absence is an easy, visible red flag. This guide gives you the structure and a worked example.
What an accessibility statement is (and isn't)
It's a public page, usually linked from your footer, where you describe the accessibility status of your website or app: what standard you're aiming for, what you've tested, what's known to still be a problem, and how someone can report an issue. It is not a certificate, and publishing one does not itself prove compliance — it's a transparency document, and its credibility depends on it being accurate rather than aspirational.
The Carrefour lesson: in the June 2026 French court case, Carrefour's own assessment showed 71% compliance with the RGAA standard — and the court still ordered a full fix within six months. A statement that honestly says "71% and improving, here's our plan" is far more defensible than a vague claim of "fully accessible" that a quick scan would contradict.
What to include, section by section
Here's a practical structure. Replace the bracketed text with your own facts — don't copy generic claims you haven't verified.
[Company name] is committed to making [website/app name] accessible, in line with the European Accessibility Act and [applicable national law, e.g. Spain's Royal Decree, or Germany's BFSG].
2. Conformance status
This website is [fully conformant / partially conformant / not conformant] with WCAG 2.1 level AA. [Partially conformant means some parts do not fully conform yet — see known issues below.]
3. What we've tested
Last tested on [date] using [automated scan tool / manual keyboard testing / screen reader tested: name it] covering [homepage, product pages, checkout, account area].
4. Known issues
- [Issue 1, plain language, e.g. "Some product filter controls are not fully operable by keyboard"]
- [Issue 2]
- Planned fix date: [date or "within Q_ 2026"]
5. Feedback and contact
If you encounter an accessibility barrier, contact [email address]. We aim to respond within [X business days].
6. Enforcement procedure
If you are not satisfied with our response, you can contact [relevant national market-surveillance authority].
7. Date
This statement was prepared on [date] and last reviewed on [date].
A filled-in example
Here's what that looks like for a fictional small homeware shop, "Nordkist," based in the Netherlands:
Accessibility statement — Nordkist.eu
Commitment: Nordkist is committed to making nordkist.eu accessible, in line with the European Accessibility Act and the Dutch Besluit digitale toegankelijkheid.
Conformance status: Partially conformant with WCAG 2.1 level AA. Most pages meet the standard; some interactive filters on category pages do not yet.
What we've tested: Last tested on 3 June 2026 using an automated accessibility scan of our homepage, top 10 product pages and full checkout flow, plus manual keyboard testing of the checkout process.
Known issues: The size/color filter on category pages cannot currently be operated with a keyboard alone. Planned fix: Q3 2026. Some product images predating March 2025 are missing descriptive alt text; we are updating these on a rolling basis.
Feedback: Email access@nordkist.eu. We aim to respond within 5 business days.
Enforcement: If unsatisfied with our response, contact the Dutch Authority for Consumers and Markets (ACM).
Date: Prepared 10 June 2026, last reviewed 10 June 2026.
Common mistakes to avoid
- Claiming "fully accessible" without evidence. If a court or regulator runs one scan and finds obvious contrast failures, an overclaimed statement makes your position worse, not better — it looks like you knew and said otherwise.
- Never updating it. A statement from 2023 with no review date signals neglect. Revisit it after every redesign and at minimum annually.
- Hiding it. Link it from your footer, the same place users expect to find privacy and legal pages.
- Writing it before testing anything. A statement based on assumptions rather than an actual scan is the exact gap that later gets exposed — test first, then write.
Get the facts before you write your statement
Our Online shop audit includes a ready-to-publish accessibility statement draft based on your actual scan results — not guesswork.
See audit pricingWhere this fits in your broader compliance work
The statement is documentation, not a fix. Pair it with the concrete steps in our online shop accessibility checklist for 2026, and read why a statement alone — like an overlay alone — isn't the same thing as reducing your actual legal exposure in our overlay risk breakdown.