What is an accessibility statement + where should it live?
Legally required statement with: WCAG conformity, known issues, contact options + enforcement route. Footer link + dedicated page.
An accessibility statement is a formal public statement declaring to what extent your site or app complies with WCAG 2.1 AA. Mandatory for government since 2018 (Dutch Temporary Decree) + for commercial services under EAA since 28 June 2025. Required content: (1) Name + address organisation. (2) Conformity status: "fully conformant / partially conformant / not conformant" with WCAG 2.1 AA — honest status. (3) Known issues: per issue: location, description, impact, planned solution + deadline. (4) How tested: WAVE/axe/manual/screen-reader test, date of last test, external audit if any. (5) Contact option: email + phone for accessibility complaints. State response time. (6) Enforcement route: on no response → ILT (government) or NL Institute for Human Rights or relevant sector regulator. (7) Date drafted + review date (max 1 year old). Where to publish? Footer link "Accessibility" + dedicated page at /toegankelijkheid/ or /accessibility/. For mobile apps: in app + in app store description. Templates: Stichting Drempelvrij + Dutch government publish templates. Missing or poor statement = punishable under EAA — fine + ILT/ACM enforcement. Practical: being honest about what doesn't work is stronger than claiming everything works. Users appreciate transparency. WCAG conformity audit once a year by external party (~€2,500-€7,500).
Sources
🔎 Common search variants
Recognise your own search? Our answer above covers these too.
- “accessibility statement template”
- “a11y statement”
- “wcag conformance statement”