Skip to main content

WordPress Accessibility: EAA Compliance Without a Rebuild

Information about the article

Portrait of Dmitry Dugarev

Author: Dmitry Dugarev

Consultant for digital accessibility & IT compliance

Last updated on:

Your website runs on WordPress, and you want to know if it is accessible. This guide shows you how to make WordPress accessible without rebuilding the site. I audit WordPress websites by hand, with a keyboard and a screen reader. Here I explain which layer of your site the barriers come from and in what order to fix them.

In short
  • WordPress itself is a good foundation. In my audits, most barriers come from the theme, the page builder, plugins and content.
  • The "accessibility-ready" tag on a theme does not mean it meets WCAG AA [1].
  • An overlay plugin does not make a website accessible on its own [2].
  • You do not need a relaunch. Start with the templates that appear on every page.

What WordPress accessibility means under the EAA and BFSG​

WordPress is the most widely used content management system. According to W3Techs, it powers 40.2% of all websites (as of September 2026) [3]. That is why Germany's accessibility law affects many WordPress websites too.

The European Accessibility Act (EAA) is the EU law. Germany implements it through the BFSG (Barrierefreiheitsstärkungsgesetz, the German Accessibility Strengthening Act). The BFSG has applied since June 28, 2025 [4]. It also covers e-commerce services ("Dienstleistungen im elektronischen Geschäftsverkehr", § 1 Para. 3 No. 5 BFSG) [4]. These are websites and apps through which a consumer initiates or concludes a contract (§ 2 No. 26 BFSG) [4]. An online shop, a booking form and a course checkout all count. Microenterprises that provide services are exempt (§ 3 Para. 3 BFSG) [4].

To check whether the BFSG applies to your website, use the BFSG relevance check. The article on microenterprises under the BFSG explains the exemption in detail. The article Who must make their website accessible? explains who else is affected.

Where barriers come from in a WordPress site​

A WordPress website is built from several layers. Each layer produces part of the HTML that visitors and screen readers receive. A barrier can start in any of them. So checking just one layer is not enough.

Open text description for "Flowchart: The layers of a WordPress website"

The flowchart shows five layers. Each layer leads to the box "HTML of the page".

  1. "1. Core and block editor"
  2. "2. Theme: header, menu, footer, templates"
  3. "3. Page builder: Elementor, Divi"
  4. "4. Plugins: forms, shop, cookie banner"
  5. "5. Content: text, images, PDFs"

The HTML of the page leads to the last box (green): "What visitors experience with a screen reader, keyboard and zoom".

Layer 1: Core and block editor​

In my audits, the WordPress core is rarely the cause of a barrier. New and changed code in WordPress must follow the Accessibility Coding Standards [5]. These standards set WCAG 2.2 Level AA as the benchmark [6]. The project aims to make the admin area and the bundled themes meet WCAG 2.2 AA "where possible" [5].

A dedicated accessibility team works to make WordPress accessible to as many people as possible [7]. The team looks for volunteers who review open patches and pull requests for accessibility [8].

The block editor also gives you tools for your content. In the Image block, you can add alt text or mark the image as decorative [9]. The Document Overview in the editor shows your heading outline [10]. But these fields only help when someone fills them in correctly.

Layer 2: The theme​

The theme builds the parts that appear on every page: header, main menu, search, footer and the post templates. So a bug in the theme repeats on every page. In my audits, I often find these barriers in the theme:

  • There is no "Skip to content" link (WCAG 2.4.1) [11].
  • The CSS removes the visible focus (WCAG 2.4.7) [12].
  • Submenus open only with a mouse (WCAG 2.1.1) [13].
  • The theme's colors have too little contrast (WCAG 1.4.3) [14].
  • A sticky header completely hides the focused element (WCAG 2.4.11) [15].

Normal text needs a contrast ratio of at least 4.5:1 against its background [14]. You can test your colors with our contrast checker.

Accessible WordPress themes: what "accessibility-ready" means​

In the WordPress.org theme directory, some themes carry the "accessibility-ready" tag. To get it, the developer has to request a voluntary review. Only themes that pass a manual review receive the tag [16]. The review covers 18 requirements, for example a skip link, keyboard navigation, contrast and labeled form fields [16].

That is a good start. But the WordPress Theme Handbook says that "accessibility-ready" does not mean the theme meets WCAG AA [1]. The theme only meets the minimum standards of the review team [1]. WordPress.org also says that it cannot guarantee every theme [5].

There is one more catch. The review covers the theme as the developer submitted it. Nobody reviews your own colors, fonts and customizations for you.

Layer 3: The page builder​

Page builders such as Elementor or Divi produce their own HTML. They decide what an accordion, a tab or a slider looks like in the code. Whether such an element works with a keyboard depends first on the builder. A screen reader needs a name, a role and a state for every control (WCAG 4.1.2) [17].

In my audits, I often see headings that are only bold text. Or an icon is a link but has no accessible name. I show how to fix this in each builder in the articles on Elementor and Divi. For sliders, see our pattern for accessible carousels.

Layer 4: Plugins​

Plugins bring their own interfaces. Contact forms, cookie banners, newsletter sign-ups and the shop checkout are typical examples. A form needs a label for every field (WCAG 3.3.2) [18]. The form must detect an error and describe it in text (WCAG 3.3.1) [19].

A cookie banner is a special case. It appears on every page, often before any other content. If it covers the page and you cannot close it with a keyboard, it blocks the whole website. I explain which plugins help and which make things worse in the article on WordPress accessibility plugins. For forms, there is a separate guide to Contact Form 7. For shops, read the article on accessible online shops with WooCommerce.

Layer 5: Content and editorial work​

You fill the last layer yourself. Every image that carries information needs alt text (WCAG 1.1.1) [20]. Headings, lists and tables must be marked up as such in the code (WCAG 1.3.1) [21]. Links need text that names their destination (WCAG 2.4.4) [22].

This layer changes every day. A new blog post can add new barriers, even when the theme and plugins are fine. I explain how to write good alt text in the article on alt text for images.

Test your WordPress site yourself: a 10-minute check​

Before you hire anyone, you can get a first impression yourself. All you need is your browser. This test does not replace an audit. But it shows you which layer the problem is in.

  1. Keyboard: Put the mouse aside. Press the Tab key and move through the home page, the menu and the contact form. You must always see where the focus is [12]. Every function must work with the keyboard [13].
  2. Skip link: On the home page, press Tab once. Does a "Skip to content" link appear? If not, the barrier is usually in the theme.
  3. Zoom: Zoom the page to 200% in your browser. All text and functions must stay available [23].
  4. Narrow window: Make the window as narrow as a smartphone. At a width of 320 CSS pixels, there must be no horizontal scrolling [24].
  5. Form: Submit the contact form empty. Does an error message tell you in text which field is wrong [19]?

If you get stuck at step 1 or 2, the cause is usually in a shared template. That is good news, because one fix there works on every page.

Why a plugin alone will not make your website accessible​

Some plugins promise to make a website accessible without any work on the code. Germany's federal and state monitoring bodies for digital accessibility have assessed such overlay tools for public-sector websites. Their conclusion: an overlay tool does not necessarily make an inaccessible website accessible [2]. Their reasons are technical, so they also apply to companies under the BFSG. The bodies recommend building accessibility in from the design stage [2].

An overlay puts scripts on top of the existing HTML. The cause in the theme, the builder or the plugin stays in place. You can find the full analysis in the article Overlays and the BFSG.

This does not mean that all plugins are bad. A plugin that improves the code itself can help. A plugin that only shows a menu for font size and contrast fixes nothing in the code. I show which plugins really help in the article on WordPress accessibility plugins.

How to make WordPress accessible without a relaunch: 7 steps​

Many site owners think they have to rebuild their website. That is rarely necessary. In my audits, most barriers sit in a few templates and components. Here is how you make your website accessible without rebuilding it. If you work in this order, each fix improves many pages at once.

Run an automated test: the free check​

Start with our free BFSG check. It checks 20 of the 55 WCAG 2.2 A and AA criteria automatically, at least in part. The other 35 criteria can only be tested manually. For example, a tool cannot judge whether an alt text describes the image meaningfully, or whether the focus order is logical.

The W3C says that evaluation tools cannot determine accessibility. They can only assist [25]. So if the tool finds nothing, that does not mean your website is accessible.

Get a manual audit​

A manual audit shows you the barriers on the tested pages, each with its location and a proposed fix. In the Basis-Audit for €490 plus VAT, I test your home page and 4 subpages. I test all 55 WCAG 2.2 A and AA criteria by hand. For the whole website, there is the BFSG audit for €1,490 plus VAT. Our sample audit report shows you what such a report looks like.

One point matters for WordPress in particular: a good audit assigns every barrier to its layer. Then you know whether you need to change the theme, the builder, a plugin or the content.

Fix the shared templates first​

Start with the header, the main menu, the footer and the cookie banner. These parts appear on every page. One fix in the header template removes the barrier across the whole website. After that, move on to the templates for posts, products and archives.

In a block theme, the header and footer are template parts. They appear in many templates, and you edit them under "Appearance > Editor" [26]. With a page builder, you edit the global header and footer templates.

For a classic theme, put your fixes in a child theme. Then they survive updates to the parent theme [27]. An example: this rule in the child theme's style.css makes the keyboard focus visible again (WCAG 2.4.7) [12].

/* style.css in the child theme */
:focus-visible {
outline: 3px solid #1a1a1a;
outline-offset: 2px;
}

If you would rather not do this yourself, we can take care of the remediation in your existing theme.

Fix your forms​

Checkout, booking and sign-up forms are where a customer concludes a contract. This is exactly what the BFSG targets (§ 2 No. 26 BFSG) [4]. Test these forms first, then the contact form and the search. Every field needs a visible label [18]. Error messages must describe the error in text (WCAG 3.3.1) [19]. Ideally, the message sits right next to the field.

You can find the basics in our pattern for accessible forms.

Set rules for your editors​

Write a short list of rules for your team. It should include at least these points:

  • Every image that carries information gets alt text. Mark decorative images as decorative in the Image block [9].
  • Headings follow a logical outline. After an H2 comes an H3, not an H4 [10], [21].
  • Link text names the destination. "Click here" is not enough.
  • PDFs are accessible or have an HTML alternative.

A tip for the Image block: alt text in the Media Library is the default for every new use of the image. Alt text in the block applies only to that one page [9].

Publish an accessibility statement​

§ 14 Para. 1 No. 2 BFSG requires the information listed in Annex 3 No. 1 [4]. You provide it in your terms and conditions (AGB) or in another clearly visible way [4]. Many people call this document an accessibility statement (Barrierefreiheitserklärung). The accessibility statement describes your service and explains how it meets the requirements [4]. It also names the responsible market surveillance authority (Marktüberwachungsbehörde) [4]. Use our accessibility statement template as a starting point.

Keep testing accessibility​

An accessible website does not stay accessible on its own. Every plugin update can change the HTML. Every new piece of content can add new barriers. So schedule short checks at fixed intervals, for example after major updates.

After our remediation, we offer ongoing support for €99 plus VAT per month for this.

Which standard applies to an accessible WordPress website?​

The BFSG itself does not name specific techniques. The detailed requirements are in the ordinance to the BFSG (BFSGV) [4], [28]. Under § 4 BFSG, your website is presumed to conform if it meets a harmonized standard [4]. The reference to that standard must be published in the Official Journal of the EU [4]. So far, no such standard for the BFSG has been published in the Official Journal [29]. This means there is no presumption of conformity under § 4 BFSG for websites yet.

In practice, EN 301 549 is the benchmark standard for websites. The common reference so far is V3.2.1, based on WCAG 2.1 AA [30], [31]. V4.1.1 came out in September 2026. It adopts WCAG 2.2 as the benchmark [31]. It only creates a presumption of conformity once the European Commission lists it in the Official Journal [31].

That is why I already test against WCAG 2.2 [32]. Version 2.2 adds 9 new success criteria compared with WCAG 2.1 [33]. All other criteria from WCAG 2.1 still apply. Only 4.1.1 "Parsing" was removed [33]. For more on the legal situation, see the overview of the EAA and BFSG.

Accessible website design: fix or rebuild?​

A relaunch only pays off in a few cases, for example when the theme no longer gets updates or the site needs a redesign anyway. In that case, plan accessibility in from the start. In my experience, that costs less than fixing it later.

In all other cases, you fix the barriers in your existing website. Design, content and URLs stay the same. The audit shows you how much work is involved. I explain roughly what the work costs in the article on the costs of an accessible website.

The longer you wait, the higher the risk. The authority can impose fines of up to €100,000 (§ 37 Para. 1 No. 8 and Para. 2 BFSG) [4]. I explain how the authority proceeds in the article on risks and fines under the BFSG.

Gutenberg websites: semantics without touching the theme​

Some barriers sit in the HTML that a block outputs. One example is an accordion title that sits in a div instead of a heading. For block editor websites, I developed the Semanticality™ plugin for this. It changes the tags and ARIA attributes of the block output when the page renders, without changing the theme's code.

<!-- Before: the title sits only in a div -->
<div class="accordion-title">
<button aria-expanded="false">FAQ</button>
</div>

<!-- After: the button sits in a real heading -->
<h3 class="accordion-title">
<button aria-expanded="false">FAQ</button>
</h3>

The button in the title stays a button. This approach does not apply to Elementor and Divi. There, we fix barriers directly in the builder and in the child theme.

Frequently asked questions (FAQ)​

Is WordPress accessible?​

The WordPress core is a good foundation. New and changed code must follow the Accessibility Coding Standards [5]. These set WCAG 2.2 AA as the benchmark [6]. But whether your website is accessible depends on the theme, the page builder, plugins and content. You have to check that for your own website.

Does the EAA or BFSG apply to my WordPress website?​

The BFSG applies, for example, when consumers initiate or conclude a contract through your website [4]. This is set out in § 1 Para. 3 No. 5 and § 2 No. 26 BFSG. Purely B2B offerings are not covered. Microenterprises that provide services are exempt (§ 3 Para. 3 BFSG) [4]. The CMS makes no difference. The BFSG relevance check gives you a first assessment. If in doubt, have a lawyer review your specific case.

Which WordPress themes are accessible?​

A theme alone does not make your website BFSG-compliant. It is only one of five layers. Themes with the "accessibility-ready" tag have passed a manual review [16]. But that does not mean they meet WCAG AA [1]. Test the theme with your own colors, plugins and content.

Can a plugin make my WordPress website accessible?​

No, not on its own. Plugins help with individual tasks, such as checking content in the editor. They do not fix the causes in the theme, the code and the content. I show which plugins are worth it in the article on WordPress accessibility plugins.

How do I make my WordPress website accessible without rebuilding it?​

Get your website tested first. Start with the free BFSG check and a manual audit. Then fix the shared templates, then the forms, then the content. Finally, publish your accessibility statement.


Disclaimer​

The content of this article was researched to the best of my knowledge and is for general information only. It does not constitute legal advice and cannot replace individual advice from a lawyer who considers your specific situation.

I cannot guarantee that the information is correct, complete or up to date. Any action you take based on the information provided here is at your own risk.

​

  1. WordPress.org, “Theme Handbook: Accessibility.” 2026. [Online]. Available: https://developer.wordpress.org/themes/functionality/accessibility/ ⤴
  2. Überwachungsstelle des Bundes für Barrierefreiheit von Informationstechnik (BFIT), “Gemeinsame Einschätzung der Überwachungsstellen des Bundes und der Länder für die Barrierefreiheit von Informationstechnik zum Einsatz von Overlay-Tools.” Mar. 2025. [Online]. Available: https://www.bfit-bund.de/DE/Publikation/einschaetzung-overlaytools.html ⤴
  3. W3Techs, “Usage statistics and market share of WordPress.” 2026. [Online]. Available: https://w3techs.com/technologies/details/cm-wordpress ⤴
  4. 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/ ⤴
  5. WordPress.org, “Accessibility.” 2024. [Online]. Available: https://wordpress.org/about/accessibility/ ⤴
  6. WordPress.org, “Accessibility Coding Standards.” 2024. [Online]. Available: https://developer.wordpress.org/coding-standards/wordpress-coding-standards/accessibility/ ⤴
  7. WordPress Accessibility Team, “Accessibility Team Handbook.” 2026. [Online]. Available: https://make.wordpress.org/accessibility/handbook/ ⤴
  8. WordPress Accessibility Team, “Make WordPress Accessible.” 2026. [Online]. Available: https://make.wordpress.org/accessibility/ ⤴
  9. WordPress.org, “Image block.” 2026. [Online]. Available: https://wordpress.org/documentation/article/image-block/ ⤴
  10. WordPress.org, “Heading block.” 2026. [Online]. Available: https://wordpress.org/documentation/article/heading-block/ ⤴
  11. W3C, “Success Criterion 2.4.1 Bypass Blocks,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#bypass-blocks ⤴
  12. W3C, “Success Criterion 2.4.7 Focus Visible,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#focus-visible ⤴
  13. W3C, “Success Criterion 2.1.1 Keyboard,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#keyboard ⤴
  14. W3C, “Success Criterion 1.4.3 Contrast (Minimum),” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#contrast-minimum ⤴
  15. W3C, “Success Criterion 2.4.11 Focus Not Obscured (Minimum),” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#focus-not-obscured-minimum ⤴
  16. WordPress Accessibility Team, “Guidelines for the WordPress accessibility-ready tag.” 2026. [Online]. Available: https://wpaccessibility.org/docs/topics/theme-guidelines/ ⤴
  17. W3C, “Success Criterion 4.1.2 Name, Role, Value,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#name-role-value ⤴
  18. W3C, “Success Criterion 3.3.2 Labels or Instructions,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#labels-or-instructions ⤴
  19. W3C, “Success Criterion 3.3.1 Error Identification,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#error-identification ⤴
  20. W3C, “Success Criterion 1.1.1 Non-text Content,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#non-text-content ⤴
  21. W3C, “Success Criterion 1.3.1 Info and Relationships,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#info-and-relationships ⤴
  22. W3C, “Success Criterion 2.4.4 Link Purpose (In Context),” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#link-purpose-in-context ⤴
  23. W3C, “Success Criterion 1.4.4 Resize Text,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#resize-text ⤴
  24. W3C, “Success Criterion 1.4.10 Reflow,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#reflow ⤴
  25. W3C Web Accessibility Initiative (WAI), “Selecting Web Accessibility Evaluation Tools.” May 13, 2024. [Online]. Available: https://www.w3.org/WAI/test-evaluate/tools/selecting/ ⤴
  26. WordPress.org, “Theme Handbook: Template Parts.” 2023. [Online]. Available: https://developer.wordpress.org/themes/templates/template-parts/ ⤴
  27. WordPress.org, “Theme Handbook: Child Themes.” 2024. [Online]. Available: https://developer.wordpress.org/themes/advanced-topics/child-themes/ ⤴
  28. 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/ ⤴
  29. Bundesfachstelle Barrierefreiheit, “Normen und Standards zum BFSG.” 2026. [Online]. Available: https://www.bundesfachstelle-barrierefreiheit.de/DE/Barrierefreiheitsstaerkungsgesetz/Normen-und-Standards/normen-und-standards_node ⤴
  30. 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 ⤴
  31. 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 ⤴
  32. W3C, “Web Content Accessibility Guidelines (WCAG) 2.2.” 2023. [Online]. Available: https://www.w3.org/TR/WCAG22/ ⤴
  33. W3C Web Accessibility Initiative (WAI), “What’s New in WCAG 2.2.” 2023. [Online]. Available: https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/ ⤴

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.