Skip to main content

Accessibility Statement Template for the EAA and BFSG

Information about the article

Portrait of Dmitry Dugarev

Author: Dmitry Dugarev

Consultant for digital accessibility & IT compliance

Last updated on:

Do you run a website or app for consumers in Germany and need an EAA accessibility statement? This page gives you an accessibility statement template to copy. I explain every required item and the section of the law behind it. I also show you why many templates online are written for public bodies, not for businesses.

The European Accessibility Act (EAA) is the EU law. Germany implements it through the BFSG (Barrierefreiheitsstärkungsgesetz, Germany's implementation of the EAA). Since June 28, 2025, the BFSG has applied to e-commerce services [1]. These include online shops, booking flows and other services where consumers enter into a contract online. So when people talk about an EAA accessibility statement for a German website, the rules come from the BFSG.

In short
  • The BFSG requires "information" on how your service meets the accessibility requirements (§ 14(1) No. 2 and Annex 3 BFSG) [1]. In practice, this page is called an accessibility statement.
  • Annex 3 No. 1 BFSG lists four required items. One of them is the competent market surveillance authority [1].
  • Accessibility statements of federal public bodies follow different rules (§ 12b BGG, § 7 BITV 2.0) [2], [3]. Their templates only partly fit a business.
  • A generator formats text. It does not find the real barriers on your website.
tip

Want the template right away? Go to the template to copy.

Looking for the new contact details of the MLBF? Go to the section on market surveillance and conciliation.

What is an accessibility statement under the BFSG?​

The word "accessibility statement" does not appear in the BFSG. The law speaks of "information under Annex 3 No. 1" [1]. The MLBF is the joint market surveillance authority of the German federal states. It stresses that this "information on accessibility" (Information zur Barrierefreiheit) is not the same as the "accessibility statement" (Erklärung zur Barrierefreiheit) of public bodies [4]. In everyday use, the page is still often called an accessibility statement. I use that term in this article.

§ 14(1) BFSG sets two conditions. You may only offer your service if it is accessible (No. 1). And you must prepare the information under Annex 3 and make it "available to the public in an accessible form" (No. 2) [1].

What exactly do you have to state? Annex 3 No. 1 sentence 1 BFSG puts it like this:

The service provider shall state for its service [...], in its general terms and conditions or in another clearly perceivable way, how it meets the accessibility requirements [...]. (Annex 3 No. 1 sentence 1 BFSG, our translation [1])

So you have two options: your terms and conditions or another clearly visible place. The Federal Ministry of Labour and Social Affairs (BMAS) gives a web page as an example [5]. I recommend a separate page with a link in the footer. Users and the authority can find it quickly there. And you can update it without touching your terms and conditions.

Who needs an accessibility statement?​

You need one if your service falls under § 1(3) BFSG [1]. For most websites, that is No. 5: e-commerce services. Under § 2 No. 26 BFSG, these are services provided through websites or apps with a view to concluding a consumer contract [1]. Check whether this applies to you with the BFSG relevance check. I explain exactly who is covered, and so needs a statement, in the article Which websites must be accessible?.

Microenterprises that offer services are exempt (§ 3(3) BFSG) [1]. The BMAS writes that they are "excluded from the scope of the law" [5]. A microenterprise has fewer than 10 employees. In addition, either its annual turnover or its annual balance sheet total is no more than €2 million (§ 2 No. 17 BFSG) [1]. The details are in the article on the microenterprise exemption.

Accessibility statement for businesses or public bodies: BFSG or BITV?​

Search for an accessibility statement template, and you often end up with templates for public bodies. In Germany, federal public bodies follow the German Disability Equality Act (Behindertengleichstellungsgesetz, BGG) and the BITV 2.0, the Accessible Information Technology Ordinance [2], [3]. Businesses follow the BFSG. The required content is different.

ItemFederal public bodies (BGG, BITV 2.0)Businesses (BFSG)
Legal basis§ 12b BGG, § 7 BITV 2.0§ 14(1) No. 2, Annex 3 BFSG
Description of the servicenot requiredrequired (Annex 3 No. 1(a) and (b))
How the requirements are metinformation on compliance (§ 7(3) BITV 2.0)required (Annex 3 No. 1(c))
Inaccessible content and reasonsrequired (§ 12b(2) No. 1 BGG)not expressly required
Feedback contactrequired (§ 12b(2) No. 2 BGG)not expressly required
Reference to conciliationrequired (§ 12b(2) No. 3 BGG)not expressly required
Competent authoritynot requiredrequired: market surveillance authority (Annex 3 No. 1(d))
Updatesevery year and after significant changes (§ 7(6) BITV 2.0)no fixed interval. Take changes to the service, the requirements and the standards into account (§ 14(3) BFSG)

Sources for the table: BGG [2], BITV 2.0 [3] and BFSG [1].

This matters for templates and generators. A public-sector template leaves out the description of your service. And it usually names the conciliation body instead of the market surveillance authority. So your statement would lack two items that Annex 3 requires.

My template below meets the BFSG and adds three items from the public-sector templates. It contains the four items the BFSG requires. On top of that, it covers feedback and contact, inaccessible content and conciliation. The BFSG does not expressly require these three. But they help your users. And they show the authority that you take barriers seriously.

What an EAA accessibility statement must contain: Annex 3 BFSG​

Annex 3 No. 1 BFSG requires a description of the applicable requirements. It covers the design and the delivery of the service, as far as this is relevant for assessing it [1]. Where applicable, it contains at least these four items [1]:

  • (a) "a general description of the service in an accessible format"
  • (b) "descriptions and explanations necessary to understand how the service is provided"
  • (c) a description of how the service meets the accessibility requirements of the ordinance
  • (d) "the name of the competent market surveillance authority"

The MLBF lists the same four items in its FAQ [6]. This information comes on top of the standard consumer information under Art. 246 EGBGB, the German rules on pre-contractual information for consumers [1].

The Austrian Accessibility Act (Barrierefreiheitsgesetz, BaFG) sets out the required information in its own Annex 3. Read what applies there in Information under Annex 3 BaFG in Austria.

The statement itself must be accessible​

§ 14(1) No. 2 BFSG requires the information "in an accessible form" [1]. On how to make it available, the law refers to the ordinance to the BFSG (BFSGV) [1]. § 12 No. 2 BFSGV gives a benchmark. It covers information on how a service works [7]:

  • easy to find and presented in an understandable way
  • in text formats that assistive technology can turn into other formats
  • with sufficient font size, contrast and spacing
  • with an alternative for non-text content
  • perceivable, operable, understandable and robust

For your statement, this means: HTML text, not an image or a scanned PDF. Real headings, good contrast and a link that keyboard and screen reader users can reach.

Keep it on file and up to date​

You must keep the information for as long as you offer the service (§ 14(2) BFSG) [1]. You must also take changes into account. This covers changes to your service, to the requirements and to the harmonized standards (§ 14(3) BFSG) [1].

What happens without a statement?

If the information under Annex 3 is missing or not accessible, this is a "formal non-conformity" (§ 30(2) BFSG) [1]. The authority then asks you to correct it within a reasonable period (§ 30(1) BFSG) [1]. If you do not respond, you risk having your service banned (§ 30(3) BFSG) [1]. Offering a service in breach of § 14(1) is an administrative offense (§ 37(1) No. 8 BFSG) [1]. Read how high the fines can be in the article on BFSG risks and fines.

How to write an accessibility statement, step by step​

Let's go through the sections of your statement one by one. Each section comes with an example.

Scope​

  • What: State which service the statement covers.
  • How: Give the exact URL, or the name and platform of your app. Also name the operator.

This accessibility information under § 14 BFSG (accessibility statement) applies to the website https://www.your-domain.de, operated by [your name/your company].

Description of the service​

This section covers Annex 3 No. 1(a) and (b) [1]. Public-sector templates do not have it.

  • What: Briefly describe what your website or app offers. Then explain step by step how a customer uses it.
  • How: Write simple sentences. You can also refer to your terms and conditions if they contain more detail.

[Your domain] is an online shop for electronics, household goods and leisure products. You can search for products, compare them and buy them online. This is how an order works: you add products to your cart, enter your address, choose a payment method and confirm the order. You can find more information in our terms and conditions.

  • What: Name the rules you use as your benchmark.
  • How: Name the BFSG and the BFSGV [1], [7]. Also name EN 301 549, the standard you follow. For web content, it refers to the WCAG [8].

§ 4 BFSG links a presumption of conformity to harmonized standards whose references are published in the Official Journal of the EU [1]. For the BFSG, these standards have not been published there yet [9]. So do not claim a presumption of conformity under § 4 BFSG in your statement.

EN 301 549 V4.1.1 was released in September 2026. It adopts WCAG 2.2 as its benchmark [10]. Until the European Commission references the new version in the Official Journal, V3.2.1, based on WCAG 2.1 AA, remains the usual reference [10]. So I recommend aiming for WCAG 2.2 A and AA now [11].

We design this website in line with the Barrierefreiheitsstärkungsgesetz (BFSG), Germany's implementation of the European Accessibility Act, and the ordinance to the BFSG (BFSGV). We follow the European standard EN 301 549 V3.2.1, based on WCAG 2.1 A and AA. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.

Accessibility status​

This section covers Annex 3 No. 1(c): how does your service meet the requirements [1]?

  • What: Describe honestly what is already accessible and what is not. Name concrete features, such as keyboard access, alt text or captions.
  • How: Test your website against the 55 success criteria of WCAG 2.2 at Level A and AA [11]. You can do this with a manual audit or as a self-test with the BFSG checklist. The example accessibility audit shows what an audit report looks like.

The BFSG does not prescribe levels such as "partially compliant". Many statements still use three levels, because readers understand them quickly. The following rule of thumb is my own recommendation, not a legal requirement.

Text description for "Flowchart: Rating your accessibility status"

The flowchart shows my rule of thumb for rating your status.

  1. You start with an evaluation (A), as an audit or a self-test.
  2. Question (B): Are all 55 WCAG 2.2 A/AA criteria met?
    • Yes: The website is compliant (C).
    • No: Go to question (D).
  3. Question (D): Can people with disabilities use the core functions without barriers, for example search, purchase and contact?
    • Yes: The website is partially compliant (E).
    • No: The website is not compliant (F).

Also state how you determined the status: self-assessment or evaluation by a third party. Then use one of these wordings:

This website fully meets the requirements of WCAG 2.2 Level A and AA. This is based on a self-assessment dated [date].

Inaccessible content​

  • What: If you are not fully compliant, list the barriers you know about.
  • How:
    • Be specific: which content or functions are affected? Examples are PDF documents, videos without captions or low contrast in the footer.
    • Give the reason and a timeline for the fix.
    • Offer an alternative, for example help by phone or email.

Some content is exempt from the BFSG. This includes prerecorded videos and office files published before June 28, 2025 (§ 1(4) No. 1 and 2 BFSG) [1]. Read about the other exemptions in the article Which content is exempt from the BFSG?.

Are you claiming a disproportionate burden under § 17 BFSG? Then you must document your assessment. You keep it for five years after you last provided the service (§ 17(2) BFSG) [1]. You repeat it at least every five years and whenever the service changes (§ 17(3) BFSG) [1]. And you inform the market surveillance authority without delay (§ 17(5) BFSG) [1]. The BFSG does not say expressly whether the Annex 3 information must mention § 17. I recommend a short note. It makes the statement more honest. Read more in the article on disproportionate burden.

The following content is not yet fully accessible:

  • PDF documents: Our older brochures are not tagged. This means screen readers cannot read them out properly. Alternative: the same content is also on the product pages.
  • Product configurator: You cannot yet complete step 3 with the keyboard alone. Alternative: our support team will help you by phone. We plan to rework it by [time frame].
  • Older videos: Some videos published before June 28, 2025 have no captions (§ 1(4) No. 1 BFSG). We add captions to all new videos.
Honesty is the best policy

Name known gaps openly and show a plan to fix them. A statement that claims "fully accessible" falls apart at the first check. In my audits, I often see statements that promise more than the website delivers.

Feedback and contact​

  • What: Give users a simple way to report barriers to you.
  • How: Provide at least an email address or an accessible contact form. Tell users which details help you.

The BFSG does not expressly require this section. For public bodies, it is required (§ 12b(2) No. 2 BGG) [2]. I still recommend it. For users, reporting a problem to you is faster than going through the authority.

Have you found a barrier on https://www.your-domain.de? Or do you have a question about accessibility? Then write to us:

Please describe the problem and include the affected page (URL). We will reply within [time frame].

Market surveillance authority and conciliation​

  • What: Name the competent market surveillance authority. Annex 3 No. 1(d) BFSG requires this [1].
  • How: In Germany, this is the Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF) in Magdeburg. It is the joint authority of the federal states for the accessibility of products and services. Give its name, address and contact details [12].
New contact details

The MLBF has its own address in Magdeburg and its own website [12]. Check that your statement shows these current details.

Consumers can report a barrier to the MLBF. They can also file a formal application under § 32 BFSG [13]. § 32(1) BFSG does not require them to contact you first [1]. So do not add a waiting period such as "only after four weeks" into your statement.

There is also conciliation under § 34 BFSG. Consumers apply to the conciliation body under § 16 BGG (Schlichtungsstelle) [1], [14]. The BFSG does not require this reference. But it helps your users. And public-sector templates include it anyway.

I explain how the authority checks a website in the article on how an official BFSG inspection works.

The competent market surveillance authority for the accessibility of our service is:

Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF AöR)

You can report a barrier there or file an application under § 32 BFSG. You can also request conciliation from the conciliation body under § 16 BGG (§ 34 BFSG): www.schlichtungsstelle-bgg.de.

Date of this statement​

  • What: State when you created the statement and when you last reviewed it.
  • How: One sentence at the end is enough.

This statement was created on [date of creation] and last reviewed on [date of last review].

Accessibility statement template to copy​

Here are two templates for businesses under the BFSG. Replace the placeholders [...] with your details. Delete any sections that do not fit your case.

tip

The template is written in Markdown. You can paste it into any CMS that supports Markdown, for example Docusaurus. How to publish it in WordPress is explained right below the templates.

Template: Compliant
This accessibility information under § 14 BFSG (accessibility statement) applies to the website [link to your website], operated by [your name/your company].

## Description of the service

[Your domain] is a [...]. On our website, you can [short description of the service].

How to use our service: [description of the main steps, for example search, order, pay]. You can find more information in our [terms and conditions](https://www.your-domain.de/terms).

## Legal basis

We design this website in line with the Barrierefreiheitsstärkungsgesetz (BFSG), Germany's implementation of the European Accessibility Act, and the ordinance to the BFSG (BFSGV). We follow the European standard EN 301 549 V3.2.1, based on WCAG 2.1 A and AA. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.

## Accessibility status

This website **fully** meets the requirements of WCAG 2.2 Level A and AA.

This is how we meet the requirements:

- [Feature 1, for example: All functions work with a keyboard.]
- [Feature 2, for example: Images have alt text.]
- [Feature 3, for example: Videos have captions.]

This is based on [method, for example a self-assessment or an evaluation by Company XY] dated [date of assessment].

## Feedback and contact

Have you found a barrier on [link to your website]? Or do you have a question about accessibility? Then write to us:

- **Email:** [your feedback email]
- **Contact form:** [link to your contact form]

Please describe the problem and include the affected page (URL).

## Competent market surveillance authority

The competent market surveillance authority for the accessibility of our service is:

**Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF AöR)**

- **Address:**
Carl-Miller-Straße 6
39112 Magdeburg
Germany
- **Phone:** [+49 391 289 230 23](tel:+4939128923023)
- **Email:** [kontakt@mlbf-barrierefrei.de](mailto:kontakt@mlbf-barrierefrei.de)
- **Website:** [www.mlbf-barrierefrei.de](https://www.mlbf-barrierefrei.de/)

You can report a barrier there or file an application under § 32 BFSG.

## Conciliation procedure

You can request conciliation from the conciliation body under § 16 of the German Disability Equality Act (BGG) (§ 34 BFSG): [www.schlichtungsstelle-bgg.de](https://www.schlichtungsstelle-bgg.de/).

## Date of this statement

This statement was created on [date of creation] and last reviewed on [date of last review].

Publish your accessibility statement in WordPress​

Many of my clients use WordPress. Here is how to add the template to your website:

  1. Create a new page with the title "Accessibility statement".
  2. Paste the template into the block editor. According to WordPress, the editor usually converts pasted Markdown into blocks well [15].
  3. Check every heading. It must be a Heading block, not a paragraph in bold. Only then can screen readers recognize the structure [16].
  4. Publish the page. Only published pages appear in the menu [17].
  5. Link the page in the footer. In a block theme, the footer is a template part. Edit it once, and the editor updates it across all templates [18]. Add a link to the new page in its Navigation block [17].

Do you use a classic theme or a page builder like Elementor? Then how you edit the footer depends on your theme. If you run a WooCommerce shop, I also recommend a link in the checkout, for example next to the terms and conditions.

Adapt the template to your service. Review the statement after every relaunch, every new feature and every new evaluation. That way, you also comply with § 14(3) BFSG [1].

Accessibility statement generators: what they can and cannot do​

A generator asks for your details and builds a text from them. This saves you time on formatting. But there are two things it cannot do.

First: some free generators are built for public bodies only. One example is the free generator from eRecht24, a German provider of legal texts. According to the provider, it is suitable "exclusively" for authorities and public bodies [19]. For a statement under Annex 3 BFSG, the provider refers to a paid version [19]. So always check that the result contains the four required items from Annex 3.

Second: a generator does not know your website. It writes "partially accessible" if you tick that box. It does not know which barriers exist. But Annex 3 No. 1(c) requires a description of how your service meets the requirements [1]. You can only describe this honestly if you know the real status.

Automated tests also show only part of the picture. Our free BFSG check tests 20 of the 55 WCAG 2.2 A and AA criteria, at least partly automatically. The other 35 criteria can only be tested manually. For example, a tool cannot judge whether an alt text fits the image. An automated test with no findings does not mean your website is accessible.

Here is how to proceed:

  1. Test your website: start with the free check, then get a manual audit for all 55 criteria.
  2. Copy the barriers you found into the "Inaccessible content" section.
  3. Fill in the rest with the template or a generator.
  4. Fix the barriers and update the statement. I can help you with remediation in your existing theme.

Frequently asked questions (FAQ)​

Is an accessibility statement legally required?​

Yes, if your service falls under the BFSG. § 14(1) No. 2 BFSG requires the information under Annex 3 [1]. If it is missing, this is a formal non-conformity (§ 30(2) BFSG) [1]. The market surveillance authority will then ask you to correct it. Microenterprises that offer services are exempt (§ 3(3) BFSG) [1], [5].

Where should the accessibility statement go on my website?​

The BFSG allows your terms and conditions or another "clearly perceivable" place (Annex 3 No. 1 BFSG) [1]. The BMAS gives a web page as an example [5]. I recommend a separate page titled "Accessibility statement" with a link in the footer of every page.

Is there an official accessibility statement template for the BFSG?​

The BFSG does not include a template. It only lists the four items in Annex 3 [1]. The model statement under § 7(4) BITV 2.0 is for public bodies [3]. So use a template that covers the four items from Annex 3 BFSG, for example the template above.

Is an accessibility statement generator enough?​

For the format, yes. For the content, no. A generator does not know the barriers on your website. But Annex 3 No. 1(c) requires a description of how your service meets the requirements [1]. For this, you need an evaluation, as a self-test or as an audit.

How often do I need to update my accessibility statement?​

The BFSG sets no fixed interval. But you must take changes to your service, to the requirements and to the standards into account (§ 14(3) BFSG) [1]. Public bodies update their statements every year (§ 7(6) BITV 2.0) [3]. I recommend the same interval for you, plus a review after every relaunch.


Disclaimer​

This article is for information only and does not constitute legal advice. The templates are samples and do not replace a review of your individual case. I accept no liability for the accuracy or completeness of the information presented here. For your specific situation, please consult a specialized lawyer.

​

  1. Bundesministerium der Justiz und für Verbraucherschutz, “Gesetz zur Umsetzung der Richtlinie (EU) 2019/882 des Europäischen Parlaments und des Rates über die Barrierefreiheitsanforderungen für Produkte und Dienstleistungen (Barrierefreiheitsstärkungsgesetz – BFSG).” 2023. [Online]. Available: https://www.gesetze-im-internet.de/bfsg/ ⤴
  2. Bundesministerium der Justiz, “Gesetz zur Gleichstellung von Menschen mit Behinderungen.” 2018. [Online]. Available: https://www.gesetze-im-internet.de/bgg/ ⤴
  3. “Barrierefreie-Informationstechnik-Verordnung (BITV 2.0).” Verordnung zur Schaffung barrierefreier Informationstechnik nach dem Behindertengleichstellungsgesetz, 2011. Accessed: Nov. 06, 2025. [Online]. Available: https://www.gesetze-im-internet.de/bitv_2_0/ ⤴
  4. Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen, “Informationen für Unternehmen.” 2026. [Online]. Available: https://www.mlbf-barrierefrei.de/Informationen-f%C3%BCr-Unternehmen/ ⤴
  5. Bundesministerium für Arbeit und Soziales, “Leitlinien für die Anwendung des Barrierefreiheitsstärkungsgesetzes.” 2022. [Online]. Available: https://www.bundesfachstelle-barrierefreiheit.de/SharedDocs/Downloads/DE/Externe-Veroeffentlichungen/bmas-leitlinien-bfsg.pdf?__blob=publicationFile ⤴
  6. Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen, “Fragen und Antworten zum Barrierefreiheitsstärkungsgesetz.” 2026. [Online]. Available: https://www.mlbf-barrierefrei.de/Fragen-und-Antworten-zum-Barrierefreiheitsstärkungsgesetz/ ⤴
  7. Bundesministerium der Justiz und für Verbraucherschutz, “Verordnung über die Barrierefreiheitsanforderungen für Produkte und Dienstleistungen nach dem Barrierefreiheitsstärkungsgesetz (Verordnung zum Barrierefreiheitsstärkungsgesetz – BFSGV).” 2022. [Online]. Available: https://www.gesetze-im-internet.de/bfsgv/ ⤴
  8. ETSI, “ETSI EN 301 549 V3.2.1 (2021-03) - Accessibility requirements for ICT products and services.” 2021. [Online]. Available: https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf ⤴
  9. Bundesfachstelle Barrierefreiheit, “Normen und Standards zum BFSG.” 2026. [Online]. Available: https://www.bundesfachstelle-barrierefreiheit.de/DE/Barrierefreiheitsstaerkungsgesetz/Normen-und-Standards/normen-und-standards_node ⤴
  10. AccessibleEU, “The European accessibility standard EN 301 549 has been updated.” 2026. [Online]. Available: https://accessible-eu-centre.ec.europa.eu/content-corner/news/european-accessibility-standard-en-301-549-has-been-updated-2026-09-07_en ⤴
  11. W3C, “Web Content Accessibility Guidelines (WCAG) 2.2.” 2023. [Online]. Available: https://www.w3.org/TR/WCAG22/ ⤴
  12. Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF), “Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen.” 2026. [Online]. Available: https://www.mlbf-barrierefrei.de/ ⤴
  13. Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen, “Antrag nach Paragraf 32 Absatz 1 BFSG.” 2026. [Online]. Available: https://www.mlbf-barrierefrei.de/Informationen-für-Verbraucherinnen-und-Verbraucher/Antrag-nach-Paragraf-32-Absatz-1-BFSG/ ⤴
  14. Schlichtungsstelle nach dem Behindertengleichstellungsgesetz, “Barrierefreiheit von Produkten und Dienstleistungen.” 2026. [Online]. Available: https://www.schlichtungsstelle-bgg.de/Webs/SchliBGG/DE/GBS/moegliche-antragsgegner/barrierefreiheitsstaerkungsgesetz/barrierefreiheitsstaerkungsgesetz-node.html ⤴
  15. Learn WordPress, “How to Create a Post or Page with the WordPress Block Editor.” 2026. [Online]. Available: https://learn.wordpress.org/lesson-plan/how-to-create-a-post-or-page-with-the-wordpress-block-editor/ ⤴
  16. W3C, “Success Criterion 1.3.1 Info and Relationships,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#info-and-relationships ⤴
  17. WordPress.org, “Navigation block.” 2026. [Online]. Available: https://wordpress.org/documentation/article/navigation-block/ ⤴
  18. WordPress.org, “Template Part block.” 2026. [Online]. Available: https://wordpress.org/documentation/article/template-part-block/ ⤴
  19. eRecht24, “Kostenloser Generator für Ihre Barrierefreiheitserklärung.” 2026. [Online]. Available: https://www.e-recht24.de/barrierefreiheitserklaerung.html ⤴

About the author

Portrait of Dmitry Dugarev

Best regards,

Dmitry Dugarev

Founder of Barrierenlos℠. I test websites by hand and fix the barriers on WordPress websites – without a relaunch.