What an accessibility statement for an online shop must contain
The European Accessibility Act asks a provider of e-commerce services to consumers, unless it is a microenterprise, to make public how its service meets the accessibility requirements; Germany’s BFSG asks for corresponding information and adds the competent market surveillance authority. The EU model accessibility statement was made for public sector bodies, under a different directive.
- Written by
- William Quaade Rasmussen
- Published
- Last updated
- Answers
- 11 questions
- Sources
- 10 sources
On this page: 11 answers
Does an online shop need an accessibility statement?
The European Accessibility Act (EAA) asks a provider of e-commerce services to consumers to make public information on how its service meets the accessibility requirements; microenterprises that provide services are exempt. The EU model accessibility statement is a template set up under a different directive, for public sector bodies.
- Covered (Article 2(2))
- E-commerce services provided to consumers after
- Exempt (Article 4(5))
- Microenterprises that provide services, from the accessibility requirements and the obligations relating to them
- Asked for (Article 13(2))
- “prepare the necessary information in accordance with Annex V” and “explain how the services meet the applicable accessibility requirements”
Sources: Directive (EU) 2019/882, Articles 2(2), 3, 4(5) and 13(2) · Commission Implementing Decision (EU) 2018/1523
Details: who the EAA covers, the exemption, what Article 13(2) asks, and the W3C’s example
The European Accessibility Act (EAA) asks a provider of e-commerce services to consumers to make public information on how its service meets the accessibility requirements; microenterprises that provide services are exempt. The EU model accessibility statement is a template set up under a different directive, for public sector bodies.
Article 2(2) of the EAA covers e-commerce services provided to consumers after 28 June 2025. Article 3 defines e-commerce services as services provided at a distance, through websites and mobile device-based services, by electronic means, at the individual request of a consumer, with a view to concluding a consumer contract. Article 4(5) exempts microenterprises that provide services from the accessibility requirements and the obligations relating to them; the guide to the European Accessibility Act explains who counts as one.
Under Article 13(2), service providers “prepare the necessary information in accordance with Annex V” and “explain how the services meet the applicable accessibility requirements”. The W3C’s guide Developing an Accessibility Statement gives an example of when a statement is required: “In some situations, you may be required to provide an accessibility statement, such as public bodies in countries that implement the EU Web Accessibility Directive.”
What does the European Accessibility Act ask an online shop to publish?
Annex V of the EAA asks, where applicable, for three elements: a general description of the service, the explanations needed to understand how it operates, and a description of how it meets the accessibility requirements. The information goes in the general terms and conditions or an equivalent document.
- a general description of the service in accessible formats;
- descriptions and explanations necessary for understanding the operation of the service;
- a description of how the relevant accessibility requirements set out in Annex I are met by the service.
Source: Directive (EU) 2019/882, Article 13(2) and Annex V
Details: the text of Annex V, and the form and duration of the information
Annex V of the EAA asks, where applicable, for three elements: a general description of the service, the explanations needed to understand how it operates, and a description of how it meets the accessibility requirements. The information goes in the general terms and conditions or an equivalent document.
Annex V states that the service provider includes the information “in the general terms and conditions, or equivalent document”. The information describes the applicable requirements and covers, as far as relevant for the assessment, the design and the operation of the service. Where applicable, it contains:
- (a) a general description of the service in accessible formats;
- (b) descriptions and explanations necessary for understanding the operation of the service;
- (c) a description of how the relevant accessibility requirements set out in Annex I are met by the service.
These elements come in addition to the consumer information that Directive 2011/83/EU requires. Article 13(2) adds the form and the duration: the information is made available to the public “in written and oral format, including in a manner which is accessible to persons with disabilities”, and kept “for as long as the service is in operation”.
What does the BFSG add for an online shop in Germany?
The competent market surveillance authority. Annex 3 of Germany’s BFSG asks for three elements that correspond to those of Annex V of the European Accessibility Act and adds that authority as a fourth; for the BFSG, that authority is the MLBF in Magdeburg.
The authority for the BFSG, according to the federal accessibility agency
- Name
- Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF)
- Seat
- Magdeburg
- Responsible for
- Market surveillance under the BFSG, nationwide
Sources: § 14(1) BFSG and Annex 3 BFSG · Bundesfachstelle Barrierefreiheit
Details: § 14(1) BFSG, the four elements of Annex 3, the federal agency’s FAQs and the MLBF
In Germany, the BFSG asks for three elements that correspond to those of Annex V of the European Accessibility Act and adds a fourth: the competent market surveillance authority. For the BFSG, that authority is the MLBF in Magdeburg.
Under § 14(1) BFSG, a service provider may offer or provide its service only if the service meets the accessibility requirements of the regulation under § 3(2) BFSG (the BFSGV), and if the provider has prepared the information of Annex 3 (Anlage 3) and made it available to the public in accessible form. Annex 3 places the information in the general terms and conditions (Allgemeine Geschäftsbedingungen) or in another clearly perceptible way. It describes the applicable requirements, covers the design and the performance of the service as far as relevant, and contains:
- a) a general description of the service, in an accessible format;
- b) the descriptions and explanations needed to understand how the service is provided;
- c) a description of how the service meets the relevant accessibility requirements of the regulation under § 3(2) BFSG;
- d) the competent market surveillance authority.
The Bundesfachstelle Barrierefreiheit, Germany’s federal accessibility agency, says in its FAQ on electronic commerce that online shops fall under the BFSG in connection with services in electronic commerce, and that the providers of such services prepare this information and make it available to the public in accessible form. Its FAQ on services distinguishes the Annex 3 information from the Erklärung zur Barrierefreiheit, the accessibility statement of public bodies under the Behindertengleichstellungsgesetz (BGG). It gives a reference to harmonised standards or technical specifications as an example for element c). The FAQs are the agency’s reading of the law. More on the law is in the BFSG for online shops.
The authority for the BFSG is the Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF). According to an announcement by the federal accessibility agency, the MLBF is based in Magdeburg, is responsible nationwide for market surveillance under the BFSG, and began its work when a state treaty took effect on 26 September 2025.
What is in the EU model accessibility statement?
The EU model accessibility statement starts with a commitment and its scope, then has a section headed “Compliance status”, lists the content that is not accessible, says how the statement was prepared, and gives feedback and contact details and the enforcement procedure. Optional content may follow.
- Commitment and scope
- Compliance status
- Non-accessible content
- Preparation of this accessibility statement
- Feedback and contact information
- Enforcement procedure
Sources: Commission Implementing Decision (EU) 2018/1523 · Directive (EU) 2016/2102, Article 7
Details: Decision (EU) 2018/1523, the six parts, the three status options, and the W3C generator’s four options
The EU model accessibility statement starts with a commitment and its scope, then has a section headed “Compliance status”, lists the content that is not accessible, says how the statement was prepared, and gives feedback and contact details and the enforcement procedure. Optional content may follow.
Commission Implementing Decision (EU) 2018/1523 of 11 October 2018 established the EU model accessibility statement under Article 7(2) of Directive (EU) 2016/2102 on the accessibility of the websites and mobile applications of public sector bodies, the Web Accessibility Directive. Article 7(1) of that directive has Member States ensure that public sector bodies provide and regularly update a “detailed, comprehensive and clear accessibility statement”, for websites in an accessible format, using the model. The model’s parts, in order:
- Commitment and scope. The body commits to making its websites or apps accessible in accordance with the national law that transposes Directive (EU) 2016/2102, and names what the statement applies to.
- Compliance status. One of the three options in the table below.
- Non-accessible content. What is not accessible, grouped by reason: it does not meet the requirements, the body invokes a disproportionate burden, or it is outside the scope of the applicable legislation.
- Preparation of this accessibility statement. The date, and the method: a self-assessment by the body, or an assessment by a third party, for which the model gives a certification as an example.
- Feedback and contact information. A link to the feedback mechanism for reporting failures and asking for excluded content, and the contacts responsible.
- Enforcement procedure. A link to the procedure for unsatisfactory responses, and the enforcement body’s contact information.
Optional content can follow “as deemed appropriate”.
| Option | The model’s wording | When the model says to choose it |
|---|---|---|
| (a) | "[website/mobile application] is fully compliant with [standards/technical specifications]" | Only if all requirements of the standard or technical specification are fully met, without exceptions |
| (b) | "[website/mobile application] is partially compliant with [standards/technical specifications], due to [the non-compliance(s)] [and/or] [the exemptions] listed below" | Most requirements are met, with some exceptions |
| (c) | "This/These website(s)/mobile application(s) is/are not compliant with [xxx]. The non-compliance(s) and/or the exemptions are listed below." | Most requirements are not met |
The model says “compliant”. The W3C’s statement generator offers four conformance options instead: “Fully conformant”, “Partially conformant”, “Non conformant” and “Not assessed”.
How do the EAA, the BFSG and the EU model compare?
The EAA and the BFSG ask a service provider for information about its service and how it meets the requirements. The EU model gives a public body places for a status, a list of barriers, a feedback mechanism and the enforcement procedure.
| Point | EAA (Article 13(2), Annex V) | BFSG (§ 14, Annex 3) | EU model statement (Decision (EU) 2018/1523) |
|---|---|---|---|
| Written for | Service providers, including providers of e-commerce services to consumers; microenterprises that provide services are exempt | Service providers; the federal accessibility agency names online shops | Public sector bodies, under the Web Accessibility Directive (EU) 2016/2102 |
| Where it goes | The general terms and conditions, or an equivalent document | The general terms and conditions, or another clearly perceptible way | On the website, in an accessible format |
| What it contains | Where applicable: a general description of the service; the explanations needed to understand how it operates; how it meets the requirements of Annex I | Three corresponding elements, and the competent market surveillance authority | Commitment and scope; compliance status; non-accessible content; preparation; feedback and contact; enforcement procedure |
| Form | Written and oral, including in a way accessible to persons with disabilities | Available to the public in accessible form | An accessible format |
| How long, how often | Kept for as long as the service is in operation | Kept for as long as the service is offered or provided, according to the federal accessibility agency | Updated regularly; the recitals encourage a review at least once a year |
Sources: Directive (EU) 2019/882, Article 13(2) and Annex V · § 14 and Annex 3 BFSG · Decision (EU) 2018/1523
Does a shop have to use the EU model statement?
The EU model was made for public sector bodies under the Web Accessibility Directive; for a shop, the EAA names the Annex V information and the BFSG the Annex 3 information. Whether to follow the model’s structure is a decision for the shop and its legal counsel.
Sources: Decision (EU) 2018/1523 · Directive (EU) 2019/882, Annex V · Annex 3 BFSG
Details: what the model has places for, and what it leaves out
The EU model was made for public sector bodies under the Web Accessibility Directive. For a shop, the EAA names the Annex V information and the BFSG names the Annex 3 information.
The model’s structure has places for a status, known barriers, contact details and an enforcement body. The general description of the service and the explanations needed to understand how it operates, which Annex V and Annex 3 both name, are not among its six parts listed above. Whether to follow the model’s structure, and in which document the information goes, is a decision for the shop and its legal counsel.
Does a statement have to list what is not accessible yet?
Under the BFSG, no, according to Germany’s federal accessibility agency: non-conformity does not have to be stated and justified, because a service provider is in principle obliged to make its service fully accessible. The W3C advises listing known limitations; whether to list them is for the shop and its legal counsel.
-
Decision (EU) 2018/1523
EU model
It has a section for non-accessible content.
-
Bundesfachstelle Barrierefreiheit, FAQ on services
BFSG
Germany’s federal accessibility agency says that non-conformity does not have to be stated and justified, because a service provider is in principle obliged to make its service fully accessible.
-
W3C, Developing an Accessibility Statement
W3C
It advises naming “any known limitations, to avoid frustration of your users”.
Sources: Bundesfachstelle Barrierefreiheit, FAQ on services · W3C, Developing an Accessibility Statement
Details: what the agency contrasts it with, and the W3C’s advice
The EU model has a section for non-accessible content. For the BFSG, Germany’s federal accessibility agency says in its FAQ on services that non-conformity does not have to be stated and justified, because a service provider is in principle obliged to make its service fully accessible. The W3C advises listing known limitations.
The agency contrasts this with public bodies, which state which parts of a website or app are not yet fully accessible and why. “Does not have to” is not the same as “must not”. The W3C’s guide advises naming “any known limitations, to avoid frustration of your users”, and its generator has a field for “What to do in the meantime”. Whether a shop’s information lists known barriers is a decision for the shop and its legal counsel.
What makes a statement useful to customers?
A useful statement is written for the people who use the shop, in plain language, and tells them whom to contact. That is the W3C’s advice, which is good practice rather than law.
-
W3C, Developing an Accessibility Statement
At least
A commitment to accessibility for people with disabilities, the accessibility standard applied, such as WCAG 2.2, and contact information in case users encounter problems.
-
W3C, Developing an Accessibility Statement
Also advised
Known limitations, the measures taken, technical prerequisites such as supported web browsers, the environments in which the content was tested, and references to applicable laws and policies.
Source: W3C, Developing an Accessibility Statement and Generate an Accessibility Statement
Details: what the W3C says a statement should contain, and its advice on language
A useful statement is written for the people who use the shop, in plain language, and tells them whom to contact. That is the W3C’s advice, which is good practice rather than law.
The W3C’s guide Developing an Accessibility Statement says a statement should contain at least a commitment to accessibility for people with disabilities, the accessibility standard applied, such as WCAG 2.2, and contact information in case users encounter problems. It also advises known limitations, the measures taken, technical prerequisites such as supported web browsers, the environments in which the content was tested, and references to applicable laws and policies.
On language, the guide gives an example: rather than “WCAG Success Criterion 1.2.2 was not met”, it is better to say “videos do not have captions”. The W3C generator also has a field for the typical duration of a response to feedback.
Where should the information go, and how often should it be updated?
In the general terms and conditions, or an equivalent document under Annex V of the EAA, or another clearly perceptible way under Annex 3 of the BFSG. For a shop, Article 13(2) of the EAA asks that the information be kept for as long as the service is in operation.
-
Annex to Decision (EU) 2018/1523, for public sector bodies
A prominent link
The instructions call for a link placed prominently on the home page or available on every page, for example in a static header or footer.
-
W3C, Developing an Accessibility Statement
Several places
The W3C advises linking the statement from several places, such as the footer, help menu, sitemap and about page, and using consistent link names.
-
Decision (EU) 2018/1523, for public sector bodies
A yearly review
The recitals encourage a review of the statement at least once a year, and the model’s optional part recommends checking the accuracy of its claims at least once a year.
Sources: Directive (EU) 2019/882, Article 13(2) and Annex V · Annex 3 BFSG · Decision (EU) 2018/1523 · W3C
Details: where the information goes, how customers find it, how long it is kept, and the yearly review for public sector bodies
Annex V of the EAA places the information in the general terms and conditions or an equivalent document. Annex 3 of the BFSG places it in the general terms and conditions or another clearly perceptible way; the federal accessibility agency names a website as an example.
For findability, the instructions in the Annex to Decision (EU) 2018/1523, written for public sector bodies, call for a link placed prominently on the home page or available on every page, for example in a static header or footer. The W3C advises linking the statement from several places, such as the footer, help menu, sitemap and about page, and using consistent link names.
For a shop, Article 13(2) of the EAA asks that the information be kept for as long as the service is in operation. For public sector bodies, the recitals of Decision (EU) 2018/1523 encourage a review of the statement at least once a year, and the model’s optional part recommends checking the accuracy of the statement’s claims at least once a year.
Does publishing a statement mean the shop meets the requirements?
No. In both the EAA and the BFSG, publishing the information and meeting the accessibility requirements are separate: Article 13 of the EAA sets them in separate paragraphs, and § 14(1) BFSG names each as a condition for offering the service.
Accessibility statements are not technical assessments or declarations of conformity, though they ideally refer to such background to provide verification and increase credibility.
Sources: Directive (EU) 2019/882, Article 13 · § 14(1) BFSG · W3C, Developing an Accessibility Statement
Details: Article 13 of the EAA, § 14(1) BFSG and the W3C
No. In both laws, publishing the information and meeting the accessibility requirements are separate. Article 13 of the EAA sets them in separate paragraphs: paragraph 1 has services designed and provided “in accordance with the accessibility requirements”, paragraph 2 asks for the information. § 14(1) BFSG names each as a condition for offering the service.
The W3C puts it this way: “Accessibility statements are not technical assessments or declarations of conformity, though they ideally refer to such background to provide verification and increase credibility.”
What does the draft statement in a Remediation Evidence Package contain?
The draft accessibility statement in a Remediation Evidence Package follows the structure of the EU model statement, adapted to the European Accessibility Act for an online shop. It is marked “Draft for legal review”, and its notice says that the merchant’s legal counsel must review it before it is published.
- Commitment and scope
- Status
- Non-accessible content
- Preparation
- Feedback and contact information, and the enforcement procedure
- Information about the service
- A Before publishing checklist
Details: the draft’s sections, what only the merchant can provide, and the checklist
The Remediation Evidence Package includes a draft accessibility statement for the shop, marked “Draft for legal review”. Validiscan prepares it from the results of the package. It follows the structure of the EU model accessibility statement and adapts it to the European Accessibility Act for an online shop. Its notice says that the merchant’s legal counsel must review it before it is published, that Validiscan does not give legal advice, and that whether, where and in which languages the statement must be published depends on the law that applies to the merchant.
The draft’s sections:
- Commitment and scope, with the national law that transposes the EAA: the BFSG for a merchant in Germany, a field to complete for a merchant in another country.
- Status, in the model’s wording, with a sentence saying that it describes conformance with the Level AA success criteria of the WCAG versions it names, as evaluated on the pages and dates the statement names.
- Non-accessible content, in plain language per WCAG success criterion, marked “not met”, “partially met” or “fixed, verification pending”. For success criterion 1.2.2: “Some prerecorded videos have no captions, so people who cannot hear the sound miss the spoken content.”
- Preparation: the date, the package version, and the method, which the draft calls a self-assessment by the merchant, based on the evaluation in the package, and “not a certification”.
- Feedback and contact information, and the enforcement procedure with the market surveillance authority.
- Information about the service, the Annex V block: the service, using the service, the accessibility requirements and the accessibility features.
- A Before publishing checklist.
Text in square brackets marks what only the merchant can provide, such as the contact for accessibility feedback, the market surveillance authority for a merchant outside Germany, and a general description of the shop. The checklist asks for those fields to be completed, for a review by legal counsel, for publication in an accessible format, for example linked from the footer of every page, with a reference in the general terms and conditions, and for an update after every new evaluation. The application holds the draft’s text in English, German, Danish, French and Spanish.
The package itself says: “This package is evidence of an evaluation and of remediation work. It is not a certificate and does not state legal compliance.” The steps from the baseline scan to the package are described in how a project runs.
Sources
10 sources: EU law, German law and the federal accessibility agency, and the W3C’s guidance. Each was checked for this guide on 6 October 2026.
EU law 3
- Directive (EU) 2019/882 (European Accessibility Act) · EUR-Lex · checked
- Directive (EU) 2016/2102 on the accessibility of the websites and mobile applications of public sector bodies · EUR-Lex · checked
- Commission Implementing Decision (EU) 2018/1523 establishing a model accessibility statement · EUR-Lex · · checked
Germany 5
- § 14 BFSG · gesetze-im-internet.de · checked
- Anlage 3 BFSG · gesetze-im-internet.de · checked
- FAQ zum BFSG: Dienstleistungen · Bundesfachstelle Barrierefreiheit · checked
- FAQ zum BFSG: elektronischer Geschäftsverkehr · Bundesfachstelle Barrierefreiheit · checked
- Website der Marktüberwachungsstelle ist online · Bundesfachstelle Barrierefreiheit · checked
W3C guidance 2
- Developing an Accessibility Statement · W3C Web Accessibility Initiative (WAI) · · checked
- Generate an Accessibility Statement · W3C Web Accessibility Initiative (WAI) · · checked
Read next
All 6 guides-
The European Accessibility Act (EAA) for online shops
UpdatedThe European Accessibility Act, Directive (EU) 2019/882, covers e-commerce services provided to consumers after 28 June 2025 and exempts microenterprises that provide services from its accessibility requirements.
-
The BFSG for online shops: who it covers and what it requires
UpdatedThe BFSG is the German law that transposes the European Accessibility Act; it has been in force since 28 June 2025 and covers e-commerce services offered to consumers through websites and apps.
-
WCAG 2.2 AA and EN 301 549: which one applies to an online shop
UpdatedWCAG and EN 301 549 are not alternatives: EN 301 549, the European standard for the accessibility of ICT products and services, uses the success criteria of WCAG for web pages.
Start with a free check of your shop.
Send your shop’s address. Validiscan scans it and replies with every failure the scan can prove, with the page and the code.
Request a free checkOr write to info@validiscan.com.
What the free check covers, and what it leaves out- You send
- your shop’s address
- Pages scanned
- up to 15
- You get
- every failure the scan can prove, with the page and the code
- On your shop
- public pages only; no login, nothing bought, no forms sent
- What it is not
- a full audit