
Website accessibility statement: what the EAA asks for
At a glance
EU-17MediumDirective (EU) 2019/882, Art. 13(2) and Annex V; BFSG § 14(1) No. 2 and Anlage 3
Peeky looks for the accessibility information the European Accessibility Act asks online shops to publish, checks that a visitor can reach and read it, and reads it against Annex V.
Last checked against the source:
The rule
An online shop that sells to people in the EU has two accessibility duties under the European Accessibility Act. One is to make the site work for disabled customers, which EU-10 covers. The other is to say in public how it does that. This page is about the second one.
“Service providers shall prepare the necessary information in accordance with Annex V and shall explain how the services meet the applicable accessibility requirements. The information shall be made available to the public in written and oral format, including in a manner which is accessible to persons with disabilities. Service providers shall keep that information for as long as the service is in operation.”
“The service provider shall include the information assessing how the service meets the accessibility requirements referred to in Article 4 in the general terms and conditions, or equivalent document.” Where applicable, it contains “(a) a general description of the service in accessible formats; (b) descriptions and explanations necessary for the understanding of the operation of the service; (c) a description of how the relevant accessibility requirements set out in Annex I are met by the service.”
The Directive never uses the word “statement”. It says “general terms and conditions, or equivalent document”, and German law also allows “auf andere deutlich wahrnehmbare Weise”, another clearly visible way. The German labour ministry’s guidance gives a web page as the example, and the Dutch ACM tells shops to put a statement on their website and app. So a page called Accessibility, linked from the footer, does the job. A section in your terms does too.
The duty covers “e-commerce services” provided to consumers after 28 June 2025, defined as “services provided at a distance, through websites and mobile device-based services by electronic means and at the individual request of a consumer with a view to concluding a consumer contract”. A service provider is anyone who “provides a service on the Union market or makes offers to provide such a service to consumers in the Union”, so a UK or US shop selling into the EU is in.
The ACM reads that widely: a site where consumers can buy, rent, order, book or subscribe, even if only part of the site sells, and even if the price is paid in personal data. A site that only takes enquiries, or sells only to businesses, isn’t an e-commerce service on the Directive’s wording.
“Microenterprises providing services shall be exempt from complying with the accessibility requirements referred to in paragraph 3 of this Article and any obligations relating to the compliance with those requirements.” A microenterprise “employs fewer than 10 persons and … has an annual turnover not exceeding EUR 2 million or an annual balance sheet total not exceeding EUR 2 million”.
National laws say plainly that the exemption takes in the information too. Ireland writes that Regulation 14, the information duty, “shall not apply to a service provided by a microenterprise”. The Dutch Civil Code says the same of article 6:230fb, and Austria exempts them “von allen Verpflichtungen im Zusammenhang mit der Erfüllung dieser Anforderungen”, from every obligation tied to the requirements.
The disproportionate burden rule doesn’t take the information away. Article 14 lets a provider skip a requirement whose cost would be out of proportion, but it limits only “the accessibility requirements referred to in Article 4”. The information duty sits in Article 13. A business that relies on Article 14 has to document the assessment, renew it at least every five years and, unless it’s a microenterprise, “send information to that effect” to the authority (Art. 14(3), (5) and (8)).
Each country wrote the duty into its own law, and some added to it.
| Where | What the national text adds | Who supervises online shops |
|---|---|---|
| Germany (BFSG § 14, Anlage 3) | A fourth element: “die Angabe der zuständigen Marktüberwachungsbehörde”, the name of the authority. Missing or incomplete information is a “formale Nichtkonformität” with its own procedure (§ 30) | The MLBF, the joint authority of the German states |
| Austria (BaFG § 14, Anlage 3) | Written and oral form. Not preparing the information is an offence of its own (§ 36(2) No. 2) | Sozialministeriumservice |
| France (D. 412-57, R. 451-4) | Written and oral form. Not establishing, publishing or keeping the information is a separate fifth-class offence | Not named in the decree |
| Netherlands (BW 6:230fb) | Written and oral form. The ACM says the statement must be easy to find and itself accessible | ACM |
| Ireland (S.I. 636/2023, Reg. 14) | The information must be ready “before providing a service”. Ignoring a direction to fix it is an offence (Reg. 32) | Competition and Consumer Protection Commission |
| Italy (D.lgs. 82/2022, art. 12) | Written and oral form. The fines in art. 24 cover the information duty | AgID |
| Spain (Ley 11/2023, art. 13) | Point (c) is worded as how the delivery of the service and its monitoring keep it in line with the requirements | An authority named by each autonomous community |
Germany’s extra element is easy to miss in a template written for another country. The MLBF names itself as the authority to give: the “Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen”.
What PeekWell checks and how
EU-17 asks whether a visitor can find and read the accessibility information the Act asks for, and whether it says what Annex V lists. Peeky runs it for the same companies as EU-10: every company except one whose profile says it has fewer than 10 people. It runs whether or not consumers can buy or book on your site. That part is PeekWell’s choice, not the Act’s. The Act asks this of sites that sell, take bookings or take paid sign-ups online, and on a site that does none of those the finding says so. If the information isn’t there, the check fails. It’s never left out of the score.
Peeky looks where a customer would. That means the footer, header and menus of every page it opens, your terms, your legal and help pages, and every language version of the site. It looks for links and headings such as Accessibility, Barrierefreiheit, Accessibilité, Toegankelijkheid, Accessibilità and Accesibilidad, and for a section in the terms.
The check passes when all of this holds:
- A visitor can reach the information without signing in, from your terms or from a link in the footer, header or menu that every page shares.
- It’s real text: a web page or a tagged PDF that a screen reader can read, not a picture of text or a scanned document.
- It describes the service (Annex V point (a)).
- It explains how the service works (point (b)).
- It says how the service meets the requirements, by naming the standard or rules you follow or describing what you’ve done (point (c)). A sentence like “we aim to be accessible” doesn’t say how.
- If your scan covers the German market, it names the MLBF.
The finding names what was missing and quotes what the scan read, so you can see where it looked.
Some things don’t count against you. The page can be called anything. The information can live only in your terms. The Act doesn’t ask for a date, a feedback contact or a list of known problems, so Peeky doesn’t check for them. If your page says you rely on the disproportionate burden rule, Peeky doesn’t judge that claim.
The scan has limits, and the report says so. The Act asks for the information in “oral format” too, and that usually means someone on your phone line can read it out; Peeky can’t see that. It doesn’t check whether what your page claims is true, because that’s what EU-10 tests on the site itself, and EU-10 no longer asks whether a statement exists. It can’t see your turnover, notices you’ve sent an authority, your app, or pages behind a sign-in you didn’t give it. A Passed means the expected information was found and readable on the pages scanned. It doesn’t say the site complies.
Why it matters for a company
Anyone can check this part of the Act from outside your business, and Germany’s authority says it does exactly that. The MLBF’s strategy for services, dated 8 January 2026, says checking this information “ist ein wesentlicher Bestandteil der formalen Überwachung”: a core part of its formal supervision. The same document says that for web-based services it relies on automated pre-checks to cover far more of the market than manual testing could, and that its first step is a request to put things right by a deadline.
German law gives missing information a procedure of its own. Under § 30 BFSG the authority asks for a correction within a reasonable time, then asks again with the threat of prohibiting the service, then takes the measures needed. Consumers and recognised associations can ask the MLBF to open proceedings (§ 32).
Elsewhere the information duty carries its own penalty. Austria fines not preparing it at up to EUR 40,000, or EUR 25,000 for a small or medium business (BaFG § 36(2)). France makes it a fifth-class offence (art. R. 451-4). Italy’s range for the provider’s duties, information included, runs from EUR 5,000 to EUR 40,000 (art. 24). Those are the ceilings and ranges in the statutes. Nobody has been fined under them yet, as far as we could find.
What has happened is quieter. The Dutch ACM says it picks sites to examine itself. In Germany, law firms report two waves of warning letters since summer 2025 that cite the information duty alongside the accessibility requirements. By late August 2026 no court had decided whether a business can enforce the BFSG against a rival that way.
A published statement also gets read. In the French case against Auchan’s online shop, the claimants asked the Lille court to order every defect listed in the shop’s own accessibility statement fixed, and the court quoted its ratings: 13 of its 19 sections had a strong to major impact. It still dismissed the claims in interim proceedings. Under a separate French law, the media regulator Arcom served formal notice on a ministry on 24 June 2026 over impots.gouv.fr, its accessibility statements included. One hadn’t been updated in three years and claimed full conformity at a rate of 42.11%.
Smaller companies and larger companies
The size line is the microenterprise test: fewer than 10 people and a turnover or balance sheet of no more than EUR 2 million. Peeky goes by the head count on your profile, so it skips every company under 10 people. The law’s exemption is narrower. A team of eight with a turnover and a balance sheet both above EUR 2 million isn’t a microenterprise, and the duty applies.
A small shop often has no accessibility page at all, because the theme didn’t come with one. When it does have one, it’s often a template written for public bodies under the Web Accessibility Directive, with a conformance level, a list of problems and a feedback form. That template rarely says what the shop is or how buying from it works, which is what points (a) and (b) ask for. A German shop that copied an English template usually doesn’t name the MLBF.
A larger company sells in several countries, languages and apps, and each needs the information where its customers will look. The authority to name in Germany isn’t the one an Irish or Dutch page would mention. Keeping it current is the harder part: the Directive asks providers to take account of changes to the service and to the standards they cite (Art. 13(3)). In France a company with more than EUR 250 million in average French turnover also has the older duties of Article 47 of the 2005 disability law: a compliance mention on the home page, a declaration, and multi-year and annual plans, which Arcom supervises.
Enforcement cases
Published decisions about other companies, listed for context. Each links to the authority's own page. They say nothing about any particular website.

Larger companies
No decision is listed here yet.
Smaller companies
By 3 November 2026 no authority or court had published a decision on this duty, about a company of any size. We checked Germany's MLBF, which has published how it supervises but no decision; the Dutch ACM, whose publications name no company; and Sweden's PTS, which told its user council in June 2026 that it had never used a conditional fine under the accessibility law. We found no published decision from the Austrian, Irish, Italian or Spanish authorities either. France's DGCCRF reported its first round of e-commerce checks in September 2026, which we could only read about in the trade press. The warning letters reported in Germany are known only from law firms, and they don't name the shops.
How to fix it
The steps follow the Directive’s points (a) to (c), then the German extra and the form the information has to take. Check the wording against the law of each country you sell to.
- Pick where it lives. Add a page called Accessibility, or a section in your terms, and link it from the footer every page shares and from the terms. Don’t hide it behind a sign-in.
- Describe the service, point (a). One short paragraph: who runs the site, under the same legal name as your imprint, and what customers can do there. “An online shop where you can browse our range, order, pay and track your delivery” is the kind of thing.
- Explain how it works, point (b). Walk through the steps a customer takes: finding products, the basket, checking out with or without an account, the ways to pay, delivery and returns, and how to reach customer service. Add how these steps work with a keyboard, a screen reader or zoom.
- Say how it meets the requirements, point (c). Name the standard you work to, such as EN 301 549 V3.2.1, whose web clauses match WCAG 2.1 level AA, and the national law. Say which parts you checked (the site, the app, checkout and payment, customer support), how and when. Describe what you’ve done: text alternatives, keyboard use, contrast, captions, labelled forms, accessible payment providers. If some part still falls short, saying so and when you’ll fix it is honest and useful, though the Act doesn’t require it.
- In Germany, name the authority. Write it out: “Zuständige Marktüberwachungsbehörde: Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF)”.
- Publish it as text. An ordinary web page with real headings works best. A PDF has to be tagged with a text layer. A scanned page or an image doesn’t count.
- Offer it out loud too. The Directive says “written and oral”. Tell customer service they may be asked to read it out, or add a recording. The ACM gives a recorded reading as its example.
- Keep it current. Update it when you change your checkout, your theme, your payment providers or the standard you work to, and keep it published for as long as you sell.
- Re-scan. Run a scan again once the page is up. The finding should clear when the page is reachable, readable and complete.
Accessibility
About this service What the site is and who runs it
How it works Finding products, ordering, paying, delivery, support
How we meet the rules The standard and law, what was checked and when, what we've done
Authority (Germany) Marktüberwachungsstelle der Länder ... (MLBF)
Other formats How to get this information read out
Whether your wording meets a particular country’s law is a question for your legal adviser. Peeky reports what it sees.
Questions
Do I need an accessibility statement for my website?
If you sell to consumers in the EU and you're bigger than a microenterprise, yes, in substance. The European Accessibility Act asks you to publish how your service meets its accessibility requirements (Art. 13(2) and Annex V). The law doesn't call it a statement, but a page with that name is the usual way to do it.
A microenterprise has fewer than 10 people and a turnover or balance sheet of no more than 2 million euros. If you provide services and you're that small, you're exempt. A site that sells nothing to consumers isn't covered either.
What should be included in an accessibility statement?
Under the European Accessibility Act, three things: a general description of your service, the explanations someone needs to understand how it works, and a description of how it meets the accessibility requirements. That's Annex V, point 1, (a) to (c). Naming the standard you follow, such as EN 301 549 or WCAG 2.1 level AA, is the clearest way to do the third.
In Germany add the market surveillance authority, the MLBF. How to fix it has an outline you can copy.
What is a Barrierefreiheitserklärung?
It's the German name people use for the page an online shop publishes under the Barrierefreiheitsstärkungsgesetz (BFSG). The law itself asks for "Informationen nach Anlage 3", and the German authority, the MLBF, points out that the official Erklärung zur Barrierefreiheit is the public-sector document. The title doesn't matter. The content does.
German law asks for the same three elements as the Directive plus one more: the name of the competent market surveillance authority, which is the MLBF.
Is it the same as a public sector accessibility statement?
No. Public bodies follow the Web Accessibility Directive (EU) 2016/2102, which asks for a statement that lists content that isn't accessible, gives the reasons and offers a way to report problems. The European Accessibility Act asks a business for something different: what the service is, how it works and how it meets the requirements.
A statement copied from a public-sector template often leaves out the first two. Adding a feedback contact is good practice, but the Act doesn't require it.
How does Peeky check an accessibility statement?
Peeky looks for the information where a visitor would: in the footer and menus of every page it opens, in your terms and on your legal and help pages, in each language the site uses. It checks that a visitor can open it without signing in and read it as text, and reads it for the three Annex V elements, plus the MLBF for Germany. It doesn't judge whether what the page says is true. EU-10 tests the site itself.
Filed with
The rule
Directive (EU) 2019/882 (European Accessibility Act), Arts. 2(2)(f), 3(4), 3(23), 3(30), 4(5), 13(2), 14 and 30; Annex V
Read the rule (Directive (EU) 2019/882 (European Accessibility Act), Arts. 2(2)(f), 3(4), 3(23), 3(30), 4(5), 13(2), 14 and 30; Annex V)Sources
The law
- Directive (EU) 2019/882 of 17 April 2019 on the accessibility requirements for products and services, Official Journal L 151, 7.6.2019 (Arts. 2, 3, 4, 13, 14, 30, 31 and 32; Annexes I and V)
- Directive (EU) 2019/882, Article 13: obligations of service providers (legislation.gov.uk copy of the text as adopted)
- Directive (EU) 2019/882, Annex V: information on services meeting accessibility requirements (legislation.gov.uk copy)
- Directive (EU) 2019/882, Article 14: fundamental alteration and disproportionate burden (legislation.gov.uk copy)
- Germany, BFSG § 14: Pflichten des Dienstleistungserbringers
- Germany, BFSG Anlage 3: Anforderungen an die Informationen über Dienstleistungen
- Germany, BFSG § 30: Marktüberwachungsmaßnahmen bei formaler Nichtkonformität von Dienstleistungen
- Germany, BFSG § 37: Bußgeldvorschriften
- Germany, BFSG § 3: Barrierefreiheitsanforderungen, with the microenterprise exemption in paragraph 3
- Germany, BFSGV § 12: Allgemeine Anforderungen an Dienstleistungen
- Austria, Barrierefreiheitsgesetz (BaFG), BGBl. I Nr. 76/2023, consolidated text (§§ 6, 14, 35 and 36; Anlage 3)
- France, Décret n° 2023-931 of 9 October 2023 on the accessibility of products and services (art. D. 412-57 and its annex; art. R. 451-4)
- France, Code de la consommation, Article L412-13
- Netherlands, Burgerlijk Wetboek Book 6, arts. 230fa to 230fd (accessibility of e-commerce services)
- Netherlands, Implementatiewet toegankelijkheidsvoorschriften producten en diensten
- Ireland, S.I. No. 636/2023, European Union (Accessibility Requirements of Products and Services) Regulations 2023
- Italy, Decreto legislativo 27 maggio 2022, n. 82, art. 12: obblighi del fornitore di servizi
- Italy, Decreto legislativo 27 maggio 2022, n. 82, art. 24: sanzioni
- Spain, Ley 11/2023 of 8 May 2023, consolidated text (Title I, arts. 3, 13, 27 and 30)
- Greece, Law 4994/2022, Article 13: obligations of service providers (unofficial consolidated text)
- Directive (EU) 2016/2102 (Web Accessibility Directive), Article 7: the public-sector accessibility statement (legislation.gov.uk copy)
Guidance
- MLBF (Germany), market surveillance strategy for services under the BFSG, as of 8 January 2026
- MLBF (Germany), Informationen für Unternehmen
- MLBF (Germany), Fragen und Antworten zum Barrierefreiheitsstärkungsgesetz
- German Federal Ministry of Labour and Social Affairs (BMAS), Leitlinien für die Anwendung des Barrierefreiheitsstärkungsgesetzes
- ACM (Netherlands), Toegankelijkheid van e-handelsdiensten en elektronische communicatiediensten
- Arcom (France), Accessibility of digital sites and services: the duties of companies under Article 47 of Law 2005-102
Further reading
- Arcom, Décision n° 2026-358 of 24 June 2026 (formal notice to the Ministry of Public Action and Accounts over impots.gouv.fr), JORF of 7 July 2026
- Tribunal judiciaire de Lille, ordonnance de référé of 5 May 2026, apiDV and Droit Pluriel v. Auchan E-Commerce France (published by the claimants)
- PTS (Sweden), minutes of the user council of 12 June 2026
- ITMR Rechtsanwälte, BFSG 2026: MLBF-Prüfung und Abmahnung (revised 27 August 2026)
Last checked against the source:
For information only. Not legal advice.
