Accessibility Statement Template (EU Model, EAA, UK)
Accessibility statement: regime table (WAD, EAA, UK, ADA), compliance status, non-accessible content, preparation, feedback, enforcement, improvement plan
Mode d'emploi: Use it when you publish a website or app that must, or should, state how accessible it is. Fill the regime table and base the statement on a recent audit, then list each failure with criterion, impact and fix date. The main pitfall is claiming full compliance while listing issues, or a disproportionate burden claim without an assessment.
Aperçu
Accessibility Statement: [Website or app name]
Format for a public accessibility statement for a website or mobile app: compliance status, non-accessible content and the reasons for it, how the statement was prepared, feedback and contact, enforcement procedure and the improvement plan. Structure aligned with the EU model accessibility statement in Commission Implementing Decision (EU) 2018/1523 under the Web Accessibility Directive (EU) 2016/2102, with the service information duty of the European Accessibility Act, Directive (EU) 2019/882 (Member State measures apply from 28 June 2025), and dated UK and US examples. Replace every
[bracketed]value and every row marked Example. This is a documentation format, not legal advice. A statement describes accessibility; it does not make a service accessible or compliant. Check the current official texts that apply to you and get qualified advice where needed.
Document control
| Field | Value |
|---|---|
| Document ID | [A11Y-STMT-001] |
| Website or app | [Name, URL or app store link, version] |
| Organisation | [Legal name] |
| Version | [0.1] |
| Status | [Draft / Approved / Published] |
| Owner | [@owner, Accessibility lead or Product owner] |
| Approvers / reviewers | [Legal], [Digital service owner], [Accessibility specialist] |
| Regime | [EU public sector / EU EAA service / UK public sector / US ADA Title II / Voluntary] |
| Standard tested against | [EN 301 549 V3.2.1 / WCAG 2.2 level AA / WCAG 2.1 level AA] |
| Evidence | [Audit report ID and date] |
| Last updated | YYYY-MM-DD |
| Next review | YYYY-MM-DD |
| Classification | Public once published |
Approvals
| Role | Name | Decision | Date |
|---|---|---|---|
| Digital service owner | [@name] | [Approved] | YYYY-MM-DD |
| Accessibility specialist | [@name] | [Evidence confirmed] | YYYY-MM-DD |
| Legal or compliance | [@name] | [Approved] | YYYY-MM-DD |
Revision history
| Version | Date | Author | Change summary |
|---|---|---|---|
| 0.1 | YYYY-MM-DD | [@name] | First draft from audit [ID] |
| 1.0 | YYYY-MM-DD | [@name] | Example: Published; status partially compliant, 6 known issues |
| 1.1 | YYYY-MM-DD | [@name] | Example: Annual review; 4 issues fixed, 1 new issue in the booking calendar |
A. Which regime applies
| Regime | Who | What the statement must contain | Standard | Applies? |
|---|---|---|---|---|
| EU Web Accessibility Directive (EU) 2016/2102, Art. 7, model statement in Implementing Decision (EU) 2018/1523 | Public sector bodies in EU Member States | Model structure: compliance status, non-accessible content and reasons, preparation, feedback and contact, enforcement procedure | Harmonised standard EN 301 549 V3.2.1 (V4.1.1 published by ETSI in 2026; check whether it has been cited in the Official Journal) | [Yes / No] |
| European Accessibility Act, Directive (EU) 2019/882, Art. 13 and Annex V | Providers of covered services, for example e-commerce, consumer banking, e-books, passenger transport | Information on how the service meets the accessibility requirements, in the general terms and conditions or an equivalent document, in accessible formats | EN 301 549 as cited | [Yes / No; microenterprises providing services are exempt, Art. 4(5)] |
| UK Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 | UK public sector bodies | GOV.UK sample structure, with required wording for compliance status | WCAG 2.2 level AA (GOV.UK sample, updated 30 September 2024) | [Yes / No] |
| US ADA Title II rule, 28 CFR part 35 subpart H (2024) | US state and local governments | No set statement format; a statement and feedback route support compliance | WCAG 2.1 level AA; compliance dates 26 April 2027 (population 50,000 or more) and 26 April 2028 (smaller entities and special districts), as extended by the interim final rule of 20 April 2026 | [Yes / No] |
| Voluntary | Anyone else | Use the same structure | WCAG 2.2 level AA recommended by W3C | [Yes / No] |
1. Our commitment and scope
[Organisation name] is committed to making [website or app name] accessible[, in accordance with (national law transposing Directive (EU) 2016/2102 / the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018)].
This accessibility statement applies to [URL(s) or app name and version, platform].
[We want as many people as possible to be able to use this service. For example, you should be able to change colours and text size, zoom to 400% without the text spilling off the screen, navigate using only a keyboard or speech recognition software, and listen to most of the service using a screen reader.]
2. Compliance status
This [website / app] is:
- Option A: fully compliant with [standard and level].
- Option B: partially compliant with [standard and level], due to the non-compliances and/or the exemptions listed below.
- Option C: not compliant with [standard and level]. The non-compliances and/or the exemptions are listed below.
3. Non-accessible content
3.1 Non-compliance with the accessibility requirements
| ID | Content or feature | Problem for users | Criterion | Fix by | Alternative now |
|---|---|---|---|---|---|
| A11Y-NC-001 | [Page or component] | [What fails and for whom] | [WCAG 2.2 SC number and name] | YYYY-MM-DD | [Alternative route] |
| A11Y-NC-002 (Example) | Booking calendar date picker | Days cannot be chosen with a keyboard alone | 2.1.1 Keyboard | 2027-02-28 | Type the date in the text field, or call [phone] |
| A11Y-NC-003 (Example) | Promotional images on the home page | Some images have no text alternative | 1.1.1 Non-text Content | 2026-12-15 | The text next to each image gives the same information |
| A11Y-NC-004 (Example) | Session timeout on the payment page | Users are not warned before a 10-minute timeout | 2.2.1 Timing Adjustable | 2027-01-31 | Contact us to complete payment by phone |
3.2 Disproportionate burden
| ID | Content | Reason and assessment reference | Alternative | Reassess by |
|---|---|---|---|---|
| A11Y-DB-001 | [Content] | [Summary of the assessment, reference A11Y-DBA-NNN] | [Accessible alternative] | YYYY-MM-DD |
3.3 Content outside the scope of the applicable law
| ID | Content | Reason it is outside scope | Alternative on request |
|---|---|---|---|
| A11Y-OS-001 | [Office documents published before (date)] | [Exemption under the law, for example documents published before a set date and not needed for active administrative processes] | [Accessible version on request] |
| A11Y-OS-002 | [Live video] | [Exemption for live time-based media] | [Transcript within (N) days] |
| A11Y-OS-003 | [Third-party content not funded, developed or controlled by us] | [Exemption] | [Alternative] |
4. Preparation of this statement
This statement was prepared on [YYYY-MM-DD]. It was last reviewed on [YYYY-MM-DD].
The [website / app] was last tested on [YYYY-MM-DD] by [our own team / (evaluator name)]. The test used [method, for example a sample of (N) pages and the main user journeys, tested with automated tools, keyboard-only use, two screen readers and zoom at 400%]. [Link to the summary of the evaluation report, if published.]
5. Feedback and contact information
If you find a problem not listed here, or need information from this service in a different format such as accessible PDF, large print, easy read, audio or braille:
- email [accessibility@example.com]
- call [phone number] [hours]
- use [the feedback form link]
We will reply within [(N)] working days. [For requests for content in another format we aim to supply it within (N) working days.]
6. Enforcement procedure
If you are not happy with how we respond to your feedback or request, you can contact [name of the enforcement or complaints body] at [link].
UK option: The Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility regulations. If you are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS) [link]. [Northern Ireland: contact the Equality Commission for Northern Ireland (ECNI) [link].]
7. Service accessibility information (European Accessibility Act)
| Item | Our information |
|---|---|
| General description of the service | [Plain-language description] |
| How the service works for users of assistive technology | [Main journeys, supported platforms and assistive technologies tested] |
| How we meet the accessibility requirements | [Summary per requirement area, with standard and evaluation reference] |
| Where this is also published | [Terms of service section link] |
| Market surveillance authority | [Name and link in your Member State] |
8. Improvement plan
| ID | Action | Fixes | Owner | Due | Status |
|---|---|---|---|---|---|
| A11Y-ACT-001 | [Action] | [A11Y-NC-NNN] | [@owner] | YYYY-MM-DD | [Planned / In progress / Done] |
| A11Y-ACT-002 (Example) | Replace date picker with an accessible component and retest | A11Y-NC-002 | [@frontend-lead] | 2027-02-28 | In progress |
| A11Y-ACT-003 (Example) | Add timeout warning with option to extend | A11Y-NC-004 | [@payments-lead] | 2027-01-31 | Planned |
References
| Source | Status / date checked | Used for |
|---|---|---|
| Directive (EU) 2016/2102 (Web Accessibility Directive) and Commission Implementing Decision (EU) 2018/1523 (model accessibility statement), via European Commission web accessibility page | Read 2026-10-30 (EUR-Lex did not return the text to the automated reader); page names EN 301 549 v3.2.1 | Regime row, statement structure |
| Directive (EU) 2019/882 (European Accessibility Act), Arts. 4(5), 13, 31, Annex V | Checked against design/accessibility-checklist and quality/accessibility-audit in this collection (verified 2026-10-29) | EAA service information |
| GOV.UK, Sample accessibility statement for a fictional public sector website | Read 2026-10-30; page last updated 30 September 2024 | UK structure, statuses, enforcement wording |
| US Department of Justice, ADA Title II web and mobile rule, ada.gov | Read 2026-10-30; interim final rule of 20 April 2026 extended compliance dates | US row |
| W3C, Web Content Accessibility Guidelines 2.2 | W3C Recommendation, current version dated 12 December 2024 | Success criteria numbers |
Standard and licence note
Structure aligned with the model accessibility statement in Commission Implementing Decision (EU) 2018/1523 under Directive (EU) 2016/2102, with service information under Directive (EU) 2019/882 and dated UK and US examples, all summarised in original words. WCAG success criterion numbers and short names are cited from the W3C Recommendation; the statement wording is original. Check the current official texts and your national transposing law before publishing. This is a documentation format, not legal advice. Examples are fictional. Template licence: MIT.
Modèles associés
Cookie Policy Template (EU ePrivacy, UK PECR, CCPA)
Cookie policy: applicability check, watch list, consent banner checklist, categories, cookie list, choices and GPC, third parties, consent records
JuridiqueData Processing Agreement (DPA) Template (GDPR Art. 28)
Controller-processor DPA: Art. 28(3)(a)-(h) terms, sub-processors, breach notice, audits, transfer tools (SCCs, DPF, UK IDTA), CCPA s. 7051 terms, annexes
JuridiqueEnd User Licence Agreement (EULA) Template
EULA for installed software: acceptance, licence types, restrictions, open-source notices, activation, updates, data sent, warranty, liability, termination