Websites & web design
Accessibility Statement Template (EAA): What It Must Contain
Accessibility statement template for the European Accessibility Act: Annex V requirements, national variants, a copy-paste template, a filled example and common mistakes.

Key takeaways
In short:
- Under the European Accessibility Act (EAA), in-scope service providers must publish information on how their service meets the accessibility requirements (Article 13 and Annex V of Directive (EU) 2019/882). Most businesses publish it as an "accessibility statement" page.
- Annex V core elements: a general description of the service, explanations of how it operates, and how the Annex I requirements are met.
- National laws add details. Germany requires naming the market surveillance authority (the MLBF); France's guidance adds the standard used, exceptions and a contact.
- The public-sector accessibility statement (Web Accessibility Directive, model in Implementing Decision (EU) 2018/1523) is a different document. Many templates mix the two.
- Below you get a copy-paste EAA template, a filled example and a short public-sector template.
The accessibility statement is usually the first page an inspector opens. It is cheap to produce but often wrong: the wrong legal basis, claims the website cannot back up, or missing elements national law explicitly requires. This guide explains what belongs in it, gives you a template that works across EU markets, and lists the mistakes we see most. Whether your site is in scope at all, and how to make it accessible, is covered in our European Accessibility Act website guide. This is not legal advice.
What is an accessibility statement?
An accessibility statement is a public page where a provider explains how accessible its website, app or digital service is, which standard it follows and how users can get help. In EU law there are two separate obligations that both end up being called "accessibility statement":
| EAA accessibility information (businesses) | Accessibility statement (public sector) | |
|---|---|---|
| EU legal basis | Directive (EU) 2019/882, Article 13(2) and Annex V | Directive (EU) 2016/2102, Article 7 |
| Who? | Providers of consumer services in scope, e.g. e-commerce, booking, banking | Public sector bodies |
| Core content | Service description, how it operates, how requirements are met (+ national additions) | Compliance status, non-accessible content and reasons, preparation date and method, feedback mechanism, enforcement procedure |
| Official model | None at EU level | Yes, Implementing Decision (EU) 2018/1523 |
| Format | "In written and oral format, including in a manner which is accessible to persons with disabilities" (Art. 13(2)) | Accessible; prominently linked, e.g. in a footer (model instructions) |
| Updates | Keep it accurate as the service, requirements and standards change (Art. 13(3)) | Review claims regularly, at least once a year (recommended in the model) |
Germany's market surveillance authority states it bluntly on its page for businesses: "Achtung Verwechslungsgefahr!" (beware of confusion). The EAA "information on accessibility" is not the same as the public-sector "accessibility statement". A shop that copies a public-sector template usually cites the wrong law and leaves out what its own national law requires.
What does Annex V of the EAA require?
Article 13(2) obliges service providers to "prepare the necessary information in accordance with Annex V" and to "explain how the services meet the applicable accessibility requirements". They must keep that information for as long as the service is in operation. Annex V says the information goes "in the general terms and conditions, or equivalent document", must describe the applicable requirements and cover the design and operation of the service where relevant. Where applicable it must contain at least:
Checklist: Annex V elements
- (a) A general description of the service in accessible formats. What does the site offer: an online shop, appointment booking, a subscription?
- (b) Descriptions and explanations needed to understand how the service operates. Search, account, basket, payment, confirmation, cancellation.
- (c) A description of how the relevant Annex I accessibility requirements are met. In practice: the standard applied (EN 301 549, which incorporates WCAG 2.1 AA) and the concrete measures.
- Monitoring: Annex V point 3 adds that the provider "shall provide information demonstrating that the service delivery process and its monitoring ensure compliance". Describing your testing method and review cycle covers this.
- On top of consumer information: The accessibility information comes "in addition to" the consumer information under Directive 2011/83/EU. It does not replace your legal notice, terms or withdrawal information.
National additions
The directive sets the floor. Transposition laws sometimes add elements, so check each market you sell into:
| Country | Legal basis | What the information must or should include |
|---|---|---|
| Germany | BFSG § 14 and Annex 3 | Annex V elements (a) to (c) plus (d) the competent market surveillance authority. Missing or incomplete information is a "formal non-conformity" (§ 30 BFSG). |
| Austria | BaFG § 14 and Annex 3 | Annex V elements (a) to (c); information must be available in written and oral form. Authority: Sozialministeriumservice (§ 21). |
| Ireland | S.I. No. 636/2023, Reg. 14 and Schedule 3 | Annex V elements, prepared before providing the service and available in writing and orally. |
| France | Code de la consommation, annex to art. D412-57 (France Num summary) | No mandatory model; a page "Information sur l'accessibilité" with a general description, the standard used, conformity status and exceptions, derogations with alternatives, and a contact. France Num recommends at least two contact channels. |
A single template that covers the German and French lists covers the directive minimum in every member state. Translate it into the language of each market.
The German authority details
If you serve consumers in Germany, name the Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF AöR). According to its legal notice (checked 6 November 2026): Carl-Miller-Straße 6, 39112 Magdeburg, Germany; phone +49 391 289 230 23; email kontakt@mlbf-barrierefrei.de. Re-check the details before publishing.
What else should a good statement include?
Beyond the legal minimum, the W3C guidance on accessibility statements names a commitment, the standard applied and contact information as the minimum of a useful statement, and recommends known limitations, measures taken, technical prerequisites and tested environments. Combined with the public-sector model, we recommend:
| Voluntary element | Why it helps |
|---|---|
| Compliance status (full, partial, none) | An honest summary instead of a marketing claim |
| Known limitations and alternatives | Users know where problems are and how to complete the task anyway, e.g. by phone |
| Planned fixes with a timeframe | Shows the issues are known and being addressed |
| Evaluation method and date | Self-assessment, external audit or both; date of last review |
| Contact for reporting barriers | Email and phone, with a response time |
| Complaint or mediation route | E.g. in Germany the BGG arbitration board under § 34 BFSG |
| Tested browsers and assistive technology | E.g. NVDA with Firefox, VoiceOver with Safari |
| Third-party components | Payment providers, consent banner, chat widget, if their accessibility is limited |
A published limitation does not replace the duty to fix it. Under Article 13(4), a non-compliant service must be corrected, and the provider must "immediately inform the competent national authorities" of the member states where it provides the service. The statement is a transparency tool, not an exemption.
Accessibility statement template (EAA)
Replace everything in square brackets. Delete sections that do not apply rather than leaving placeholders. Publish it as a normal HTML page, not as an image or a PDF only.
Accessibility information (accessibility statement)
Last updated: [DD Month YYYY]
1. Our service
[Company name] operates [an online shop for ... / online booking for ... /
an online subscription for ...] at [www.example.eu]. Consumers can use
this website to [choose, order and pay for products / book and manage
appointments / ...]. This information applies to [the entire website
www.example.eu including checkout / the app "..." version ...].
2. How the service works
- Finding products: [search, filters, categories]
- Account: [ordering with or without an account, sign-in method]
- Basket and checkout: [steps of the checkout]
- Payment: [payment methods and providers]
- After ordering: [email confirmation, tracking, withdrawal via ...]
- Support: [phone, email, chat, opening hours]
3. How we meet the accessibility requirements
Our service is subject to Directive (EU) 2019/882 (European Accessibility
Act) as transposed by [national law, e.g. the German BFSG]. We follow the
harmonised standard EN 301 549 [V3.2.1], which incorporates the Web
Content Accessibility Guidelines (WCAG) 2.1 at level AA.
Measures include:
- full keyboard operability with a visible focus indicator
- text alternatives for informative images
- colour contrast meeting WCAG 2.1 AA
- labelled form fields and clear, announced error messages
- headings and landmarks for screen reader navigation
- zoom up to 200% without loss of content or function
- [accessible payment and authentication]
- [accessibility information on products, where provided by the
manufacturer]
4. Compliance status and known limitations
This website is [fully / partially] compliant with the standard above.
[If partially:] The following content is not yet fully accessible:
- [Section/function]: [plain-language description of the barrier].
Alternative: [e.g. order by phone on ...].
Planned fix by: [month/year].
5. How this information was prepared
It is based on [a self-assessment / an evaluation by (third party)]
carried out on [date] against [WCAG 2.1 AA / EN 301 549]. The evaluation
covered [home page, category and product pages, search, account, the full
checkout, contact and legal pages]. We re-test after significant changes
and review this page at least once a year. Last reviewed on [date].
6. Feedback and contact
Have you found a barrier, or do you need content in another format?
Email: [accessibility@example.eu]
Phone: [number, opening hours]
We usually reply within [X] working days.
7. Competent market surveillance authority
[Germany: Marktüberwachungsstelle der Länder für die Barrierefreiheit
von Produkten und Dienstleistungen (MLBF AöR), Carl-Miller-Straße 6,
39112 Magdeburg, +49 391 289 230 23, kontakt@mlbf-barrierefrei.de,
www.mlbf-barrierefrei.de]
[Other countries: name and contact of the national authority]
8. Complaints and mediation
[Germany: If you believe we breach the BFSG and you therefore cannot use
our service or can use it only to a limited extent, you can apply to the
arbitration board under the German Disability Equality Act (§ 34 BFSG):
www.schlichtungsstelle-bgg.de]
[Other countries: national complaint or enforcement route]
Sections 1, 2 and 3 cover Annex V (a) to (c); section 5 covers the monitoring point; section 7 covers Germany's element (d). The rest is voluntary but, in our view, standard. Update the standard reference once EN 301 549 V4.1.1 (based on WCAG 2.2) is cited in the Official Journal. According to AccessibleEU, it only becomes the legal reference then; we could not confirm a citation as of 6 November 2026.
Filled example: a fictional shop
The following example is invented. Example Home Ltd (35 employees) sells home textiles through its own shop to consumers in Germany and Austria and offers online booking for in-store consultations. An external audit found two open issues.
Accessibility information
Last updated: 6 November 2026
Our service: Example Home Ltd operates an online shop for curtains, cushions and rugs at www.example-home.eu, plus online booking for free consultations in our store. This information applies to the entire website including checkout and booking.
How the service works: Find products via search or categories. You can order with or without an account. Checkout has four steps: basket, address, payment, review and order. You can pay by invoice, direct debit or credit card and receive an email confirmation. Consultation slots are chosen from a list and confirmed by email.
How we meet the requirements: Our service is subject to the European Accessibility Act as transposed by the German BFSG and the Austrian BaFG. We follow EN 301 549 V3.2.1 and WCAG 2.1 level AA. All functions work by keyboard, form fields are labelled, error messages are announced by screen readers, contrast meets WCAG 2.1 AA and the site remains usable at 400% zoom. Manufacturers' accessibility information on products is shown on each product page.
Compliance status: The website is partially compliant. Not yet fully accessible:
- Colour planner: the interactive colour tool cannot be operated by keyboard. Alternative: our advisers help you choose colours by phone. Planned fix by March 2027.
- Care instructions (PDF): some PDFs created before 28 June 2025 are not tagged. On request we send the content in an accessible format.
Preparation: Based on an external evaluation against WCAG 2.1 AA on 15 October 2026. Last reviewed on 6 November 2026.
Report a barrier: accessibility@example-home.eu or +49 1234 567890 (Mon–Fri 9:00–17:00). We reply within five working days.
Market surveillance authorities: Germany: MLBF AöR, Carl-Miller-Straße 6, 39112 Magdeburg, kontakt@mlbf-barrierefrei.de. Austria: Sozialministeriumservice.
Mediation (Germany): Under § 34 BFSG you can apply to the arbitration board under the German Disability Equality Act: www.schlichtungsstelle-bgg.de
Note the PDFs: office files published before 28 June 2025 may fall outside the directive's scope. The example still mentions them and offers an alternative, which is better for customers and avoids arguments.
Short template: public-sector accessibility statement
Public sector bodies follow the model in Implementing Decision (EU) 2018/1523. Its instructions say the statement should be easy to find, for example via a link "in a static header or footer", and Article 3 requires the claims to be based on an actual evaluation (self-assessment or third party), with the method stated. The mandatory structure:
Accessibility statement
[Name of public sector body] is committed to making its website [URL]
accessible, in accordance with [national law transposing Directive (EU)
2016/2102].
Compliance status
This website is [fully / partially / not] compliant with [standard or
national law].
Non-accessible content
[Content, reason (non-compliance / disproportionate burden / out of
scope), accessible alternative]
Preparation of this accessibility statement
Prepared on [date]. Method: [self-assessment / third-party assessment].
Last reviewed on [date].
Feedback and contact information
[Link to feedback mechanism, email, phone, responsible unit]
Enforcement procedure
[Description of and link to the national enforcement procedure; contact
of the enforcement body]
The model allows "fully compliant" only if "all requirements of the standard or technical specification are fully met without exceptions". National rules may add more; Germany, for example, requires federal bodies to answer feedback within one month (§ 12b BGG).
Where should the statement be published?
Annex V allows the general terms and conditions "or equivalent document". We recommend a dedicated page because it is easier to find, check and update than a paragraph buried in your terms.
- Own URL, such as
/accessibility, titled "Accessibility" or "Accessibility information". - Footer link on every page, next to your legal notice and privacy policy.
- Linked from checkout and booking, next to terms and withdrawal information. If you are reworking the checkout's legal links anyway, add the new EU withdrawal button at the same time.
- Accessible itself: real headings, sufficient contrast, no text in images, no untagged PDF as the only version. Germany's inspection method (BFSG Annex 1) explicitly includes the accessibility information page in every sample.
- Oral format available: Article 13(2) asks for written and oral format. A phone line that can read out or explain the information is a pragmatic way to cover this.
- In apps: in the menu or settings, and on the download page.
How often should you update it?
The EAA sets no interval, but Article 13(3) requires providers to take into account changes in the service, the accessibility requirements and the referenced standards. A statement with an outdated standard or long-fixed issues no longer describes how your service meets the requirements.
| Trigger | What to do |
|---|---|
| At least once a year | Re-test the sample, update "last reviewed" (the public-sector model recommends this frequency) |
| Redesign, new shop system, new checkout | New evaluation and full rewrite |
| New payment provider, booking tool or consent banner | Test the component and update the statement |
| Known issue fixed | Remove it from the list and update the date |
| New standard cited in the Official Journal | Update the reference and test against it |
| User feedback | Investigate, fix or add as a known limitation with an alternative |
Keep old versions and audit reports. If you rely on the disproportionate-burden exception (Article 14), the assessment must be documented and renewed at least every five years; the statement alone is not enough.
Common mistakes in accessibility statements
1. "Our website is fully accessible" without an audit. The EU model allows "fully compliant" only without exceptions. Without an evaluation, "partially compliant" with an honest list is the safer and more credible statement.
2. No authority named for Germany. Templates from the public sector or from other countries often omit the market surveillance authority. For consumers in Germany, it is a required element.
3. Wrong legal basis. A shop citing the Web Accessibility Directive or a national public-sector law signals an unadapted template. Cite the EAA and the national transposition law.
4. Overlay badges as proof. A widget vendor's seal does not show conformity. The US Federal Trade Commission alleged that accessiBe misrepresented its widget's ability to make websites WCAG-compliant; the settlement required a $1,000,000 payment, according to the Federal Register. State what is actually implemented in your code.
5. Outdated date. A 2025 date on a site that has changed several times since looks like a forgotten compliance page.
6. Generic generator text. Annex V (a) and (b) require a description of your specific service. Statements of intent without details on checkout and payment fall short.
7. PDF-only or buried in the terms. An untagged PDF is itself a barrier.
8. No accessible contact route. A form with an inaccessible CAPTCHA is not a way to report barriers.
9. Third parties ignored. Payment, identification and authentication must also be accessible under the EAA. If an embedded tool has issues, list them.
10. One language only. Selling into several countries? Publish the statement in each market's language, with the relevant national authority.
Conclusion: short, specific and honest
A good accessibility statement is not legal boilerplate. It is an honest description of your service: what it offers, how it works, which standard it follows, where problems remain and whom to contact. The EAA sets three core elements plus monitoring information; Germany adds the authority, France adds the standard, exceptions and contact. The public-sector model is useful structure, but not a drop-in solution for businesses. And without an evaluation, there is no reliable compliance claim.
We audit websites against WCAG and EN 301 549, fix the findings and write the accessibility statement to match the real state of the site. See Accessible Websites for the scope, or Website Optimization if accessibility should go together with speed and conversion work. Send us your URL for a no-obligation call.
This article is general information, not legal advice. Check with a lawyer where in doubt whether and how national EAA legislation applies to your service.
Sources
All sources accessed 6 November 2026.
- Directive (EU) 2019/882 (European Accessibility Act), Articles 13, 14 and Annex V: eur-lex.europa.eu
- Directive (EU) 2016/2102 (Web Accessibility Directive): eur-lex.europa.eu
- Commission Implementing Decision (EU) 2018/1523 (model accessibility statement): eur-lex.europa.eu
- Germany, BFSG Annex 3: gesetze-im-internet.de/bfsg/anlage_3.html
- Germany, BFSG Annex 1: gesetze-im-internet.de/bfsg/anlage_1.html
- Germany, BFSG § 30 and § 34: gesetze-im-internet.de/bfsg, § 34
- Germany, BGG § 12b: gesetze-im-internet.de/bgg/__12b.html
- Germany, MLBF, Information for businesses: mlbf-barrierefrei.de
- Germany, MLBF, Legal notice (contact details): mlbf-barrierefrei.de/Impressum
- Germany, Schlichtungsstelle BGG: schlichtungsstelle-bgg.de
- Austria, Barrierefreiheitsgesetz (BaFG): ris.bka.gv.at
- Ireland, S.I. No. 636/2023: irishstatutebook.ie
- France, France Num, Accessibilité des sites de e-commerce: francenum.gouv.fr
- W3C WAI, Developing an Accessibility Statement: w3.org
- AccessibleEU, "The European accessibility standard EN 301 549 has been updated", 7 September 2026: accessible-eu-centre.ec.europa.eu
- Federal Register, accessiBe, Analysis of Proposed Consent Order, 6 January 2025: federalregister.gov
Frequently asked questions
Does the European Accessibility Act require an accessibility statement?
It requires service providers in scope to publish information on how their service meets the accessibility requirements (Article 13 and Annex V of Directive (EU) 2019/882). The directive does not call it an accessibility statement, but in practice a dedicated web page is the most common way to publish it. Microenterprises providing services and B2B-only offerings are outside the obligation.
What must an EAA accessibility statement contain?
Annex V lists a general description of the service in accessible formats, explanations needed to understand how the service operates, and a description of how the accessibility requirements of Annex I are met. Some countries add elements: Germany requires naming the competent market surveillance authority, and France's official guidance lists the standard used, exceptions and a contact.
Can I use the public-sector model statement for my online shop?
Only as inspiration. The model statement in Implementing Decision (EU) 2018/1523 was written for public sector bodies under the Web Accessibility Directive and refers to that legal basis and its enforcement procedure. A shop under the EAA must cover the Annex V elements and any national additions instead.
Can I say my website is fully accessible?
Only if an actual evaluation supports it. Even the EU model statement for public bodies allows 'fully compliant' only when all requirements of the standard are met without exception. An unsupported claim undermines the statement and is easy for an authority to check.
How often should an accessibility statement be updated?
The EAA has no fixed interval but requires providers to take changes in the service, requirements and standards into account. The public-sector model recommends reviewing claims at least once a year. We recommend the same for businesses, plus a review after every redesign or checkout change.


