Skip to main content

Divi Accessibility: Fixing Common Issues in Divi 4 and 5

Information about the article

Portrait of Dmitry Dugarev

Author: Dmitry Dugarev

Consultant for digital accessibility & IT compliance

Last updated on:

If you build or maintain Divi websites, you will want to know where Divi accessibility stands. The short answer: Divi is not accessible out of the box. I audit Divi websites by hand, with a keyboard and a screen reader. Below, I show you the typical barriers in Divi 4 and Divi 5. You will also see how to fix them in the builder and with CSS.

In short
  • Out of the box, the Divi theme has no visible focus and no skip link. The form labels are hidden [1].
  • Divi 5 adds two useful tools: custom HTML attributes and a choice of HTML tag for each module [2], [3].
  • Accordions and tabs still need custom code or a plugin. For simple toggles, Divi 5 now has a native option [4], [5].
  • You do not need a rebuild. Most fixes happen in the module settings and in your CSS.

Is Divi accessible? Where things stand in September 2026​

There are now two versions of Divi. Divi 5 left beta on February 26, 2026 [6]. Elegant Themes will keep supporting Divi 4 for at least another 12 months [6]. So your website may still run on Divi 4.

In its help center (as of December 2024), Elegant Themes announces better accessibility for Divi 5. It lists keyboard navigation, ARIA, visible focus and alt text [7]. For Divi 4, it points you to plugins from the Divi Marketplace [7].

Two new Divi 5 features make a real difference:

  • Custom Attributes (since September 2025): you can add any HTML attribute to modules and most of their sub-elements, for example aria-label or role [8].
  • Semantic Elements (since January 2026): you can choose the HTML tag of a module, for example nav, section or button [9].

Accessibility consultant Renee Dunn is still critical. She writes that Divi 5 brings only a few built-in accessibility improvements [1]. So the new tools only help if someone uses them deliberately.

Common Divi accessibility issues I find in audits​

I see these barriers on Divi websites again and again. The table shows which WCAG success criterion each one fails.

BarrierWCAG criterion
Heading level does not match the page structure1.3.1 Info and Relationships [10]
Submenus and mobile menu not reachable by keyboard2.1.1 Keyboard [11]
Toggle, accordion and tabs not usable by keyboard2.1.1 Keyboard [11]
Slider arrows without a name4.1.2 Name, Role, Value [12]
Form labels hidden3.3.2 Labels or Instructions [13]
Error messages not announced3.3.1 and 4.1.3 [14], [15]
Icon font without a text alternative1.1.1 Non-text Content [16]
No visible focus, no skip link2.4.7 and 2.4.1 [17], [18]
Animations that loop forever2.2.2 Pause, Stop, Hide [19]

Headings in modules​

Many Divi modules come with their own heading. Divi gives that heading a fixed level. For example, the title in the Blurb module is an H4 by default [20].

In my audits, I often see heading levels picked for their font size. An H1 is then followed directly by an H4. The outline in the code no longer matches the visible structure [10].

According to Renee Dunn, Divi only opens submenus when the mouse hovers over them. Keyboard users cannot reach them [1]. The mobile menu cannot be opened by keyboard either [1]. And the search field in the header has no label [1].

Toggle, accordion and tabs​

In 2024, Renee Dunn found that the Toggle, Accordion and Tabs modules could not be operated by keyboard [21].

An accordion needs a button in each title. The button sits inside a heading and reports its state with aria-expanded [22]. Tabs need the roles tablist, tab and tabpanel. Users move between tabs with the arrow keys [23].

Semantic Elements in Divi 5 cannot solve this cleanly. In Renee Dunn's test, the button wrapped the heading and the whole content [4]. For tabs, she could not set a button for each tab [4].

Slider​

According to Renee Dunn, the arrows in the Slider module have no accessible name [1]. A screen reader user then does not know what the arrow does. If the slider plays automatically, it also needs a way to pause it [19]. Our pattern for accessible carousels shows what a good carousel looks like.

Contact form: labels and errors​

By default, the Contact Form module shows the field names inside the fields [24]. This placeholder disappears as soon as someone starts typing. Elegant Themes itself says that a placeholder must not be the only label [25].

Renee Dunn found two more problems. Required fields were not marked. Error messages did not reach the screen reader [21].

Icon font​

Divi shows many icons through an icon font. A screen reader then reads out the character behind the icon. Renee Dunn gives an example: the search icon sounds like the letter "U" [1]. If the icon is a link, it has no accessible name.

Renee Dunn has documented that the Divi theme's CSS removes the visible focus [1]. Keyboard users can no longer see where they are on the page. This fails WCAG 2.4.7 [17].

The theme does not output a "Skip to content" link [1]. Check both in your own Divi version with the Tab key.

For animations, you can set "Animation Repeat" to loop forever [26]. According to Renee Dunn, Divi's default CSS ignores the "reduce motion" setting in the operating system [1].

How to make Divi accessible: fixing the barriers​

The fixes below work without a rebuild. You add CSS under Divi → Theme Options → General → Custom CSS [27]. Changes to theme files such as header.php need a child theme. Only then do they survive a theme update [27].

Choose heading levels by structure​

Open every module that has a heading. Choose the level to fit the page outline, not the font size. I recommend exactly one H1 per page.

In the Design tab, open "Title Text". Under "Title Heading Level", choose the level [20]. You set the font and size separately in the same group.

Make the main menu work with a keyboard​

There is no builder setting for submenus or the mobile menu. You need your own JavaScript or a plugin. Renee Dunn's plugin "Fix Divi A11y" makes both menus usable by keyboard. According to her, this means editing the header.php file [1]. Then test with Tab, Enter and Escape.

In Divi 5, open the Advanced tab of an element. Under "Attributes", add an attribute. You choose the target element, the name and the value [2]. This is how you give an icon link an aria-label. You hide the icon itself with aria-hidden="true".

<!-- Before: the screen reader reads "U, link" -->
<a href="/search"><span class="icon">U</span></a>

<!-- After: the screen reader reads "Search, link" -->
<a href="/search" aria-label="Search">
<span class="icon" aria-hidden="true">U</span>
</a>

Divi 4 only offered a few fixed attributes, such as class and ID. You cannot add arbitrary attributes like aria-label in its builder [8]. For ARIA attributes, Elegant Themes recommends plugins such as Divi Assistant or Accessibility Attributes [7].

Toggles and accordions with a real button​

Divi 5 offers a clean way to build simple toggles. Set the Element Type of a Group module to details. Set the first Text module inside it to summary [5]. The text in the summary then becomes the title of the toggle.

<!-- Result: a native toggle without any custom script -->
<details>
<summary>Delivery times</summary>
<p>…</p>
</details>

The details element works with a keyboard natively. Screen readers announce whether it is open or closed [5]. If you give several details elements the same name attribute, only one of them is open at a time. Elegant Themes advises testing this in older browsers [5].

If you need the Accordion module, its HTML must follow the W3C pattern [22]:

<!-- Before: the title is not a control -->
<div class="toggle">
<h3 class="toggle-title">Delivery times</h3>
<div class="toggle-content">…</div>
</div>

<!-- After: a button inside the heading, state via aria-expanded -->
<div class="toggle">
<h3>
<button type="button" aria-expanded="false" aria-controls="delivery-times">
Delivery times
</button>
</h3>
<div id="delivery-times" hidden>…</div>
</div>

A script must toggle aria-expanded and hidden on click. For this, Renee Dunn still recommends her plugin "Fix Divi A11y" [4].

Make form labels visible​

In 2023, Elegant Themes published a CSS rule. It places the labels above the fields [24]:

.et_pb_contact_form_label {
display: block;
}

CSS cannot fix required fields or error messages. For those, you need your own code or a different form plugin. Our pattern for accessible forms shows what a good form needs.

These rules give every control a visible focus [17]. I use a two-color focus ring for this: dark on the inside, light on the outside. That keeps it visible on both light and dark areas. The ring needs a contrast of at least 3:1 against the background [30]. Check your colors with our contrast checker.

If the focus is still invisible, a Divi rule is overriding yours. In that case, increase the specificity.

/* Visible focus: dark ring with a light edge */
:is(a, button, input, select, textarea, summary, [tabindex]):focus-visible {
outline: 3px solid #1a1a1a;
outline-offset: 2px;
box-shadow: 0 0 0 6px #fff;
}

/* Skip link: only visible on keyboard focus */
.skip-link {
position: absolute;
left: -9999px;
}
.skip-link:focus {
left: 1rem;
top: 1rem;
z-index: 100000;
padding: 0.5rem 1rem;
background: #fff;
}

/* Less motion when the operating system asks for it */
@media (prefers-reduced-motion: reduce) {
*,
*::before,
*::after {
animation-duration: 0.01ms !important;
animation-iteration-count: 1 !important;
transition-duration: 0.01ms !important;
}
}

The last rule switches off animations when someone has chosen reduced motion in their operating system [31]. That is a plus under WCAG 2.3.3 (AAA) [32]. To meet 2.2.2, an auto-playing slider still needs a pause button [19].

The skip link must be the first element on the page, for example <a class="skip-link" href="#main-content">Skip to content</a>. Its target is the first section of the main content. This is how you meet WCAG 2.4.1 [18].

Add the link to the header.php file in your child theme [27]. I place it directly after the opening body tag. In the Advanced tab, give the first section of the main content the CSS ID main-content [33].

Sticky header

A sticky header can hide the focused element. If it hides the element completely, that fails WCAG 2.4.11 [34]. Tab through every page all the way to the end.

Divi accessibility plugins: what they can and cannot do​

Search for "Divi accessibility" and you will find several plugins. Elegant Themes itself names two products from its Marketplace: Divi Assistant and the Accessibility Bundle [7].

The Accessibility Bundle comes from the vendor Divi-Modules. It costs 72 US dollars for unlimited websites with one year of updates. It works with Divi 4 and Divi 5 [35]. Among other things, it adds focus rings, skip links, menu settings and reduced motion [35].

Renee Dunn offers the plugin "Fix Divi A11y". It adds a skip link and a visible focus. It makes menus, toggles, accordions and tabs usable by keyboard [1]. For the menus, you have to change header.php [1].

The free "Divi Accessibility" plugin has been closed on WordPress.org since May 2020 [36]. That is why Elegant Themes advises caution [7].

Keep two points in mind. First, no plugin replaces a manual audit.

Second, the bundle includes a sidebar for visitors. In it, they can change settings such as contrast and text size [35]. A tool like this does not make the website compliant [37]. I explain why in the article on overlays and BFSG compliance.

For a comparison of other plugins, read the article on WordPress accessibility plugins.

What about the Divi AI Agent?

According to Elegant Themes, the Divi AI Agent finds skipped heading levels. It also adds alt text and aria-label across a whole page [3]. The agent changes code. But it does not navigate the page with a keyboard or a screen reader. You still have to check yourself whether an alt text describes the image correctly. The article Alt text for images shows what good alt text looks like.

Divi, the EAA and the BFSG: what to check now​

The European Accessibility Act (EAA) is the EU law. Germany implements it through the BFSG (Barrierefreiheitsstärkungsgesetz). The BFSG has applied since June 28, 2025 [38]. To find out whether it covers your Divi website, use the BFSG relevance check. For an overview of the law, see BFSG basics.

Here is how to proceed:

  1. Start the free BFSG check. It tests 20 of the 55 WCAG 2.2 A and AA criteria automatically, at least in part.
  2. Test the menu, toggles, tabs, slider and form yourself with the Tab key. Whether they work by keyboard can only be tested manually. A tool sees the code, but it does not operate the elements.
  3. Get the remaining criteria checked by hand. The Basis-Audit for €490 plus VAT checks your home page and 4 subpages by hand against all 55 criteria.
  4. Fix the barriers in your existing Divi layout. If you prefer, I can do this for you with remediation without a rebuild.

For more on themes, plugins and content editing, read the guide to WordPress accessibility.

Frequently asked questions (FAQ)​

Is Divi accessible?​

Not without extra work. Out of the box, the Divi theme has no visible focus and no skip link. The form labels are hidden [1]. You can fix these barriers with module settings, CSS and a little custom code.

Is Divi 5 more accessible than Divi 4?​

Divi 5 gives you better tools. You can add custom attributes and choose the HTML tag of a module [2], [3]. But accordions and tabs remain a problem without custom code [4].

Is a Divi accessibility plugin enough for BFSG compliance?​

No. A plugin fixes individual patterns such as focus or the skip link. Many criteria can only be tested manually. For example, only a person can judge whether a heading describes its content correctly [39]. A manual audit is still necessary.

Do I have to rebuild my Divi website for the BFSG?​

In my projects, that has rarely been necessary so far. The barriers usually sit in settings, attributes and CSS. You can change these in your existing layout. A rebuild is mainly worth it if you want a redesign anyway.


Disclaimer​

The content of this article has been 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 knows your specific situation.

The information on Divi, plugins and prices comes from the sources cited, as of September 2026. It may have changed since then.

I make no 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. Renee Dunn, Elevage Digital, “Improving WordPress Divi Accessibility.” 2026. [Online]. Available: https://elevagedigital.com/improving-wordpress-divi-accessibility/ ⤴
  2. Elegant Themes, “Custom Attributes in Divi 5.” 2025. [Online]. Available: https://help.elegantthemes.com/en/articles/12274853-custom-attributes-in-divi-5 ⤴
  3. Elegant Themes, “Semantic Elements & Custom HTML Wrappers For Divi 5.” 2026. [Online]. Available: https://help.elegantthemes.com/en/articles/13284097-semantic-elements-custom-html-wrappers-for-divi-5 ⤴
  4. Renee Dunn, Elevage Digital, “Divi5 Semantic Elements Does Little to Improve Accessibility.” 2026. [Online]. Available: https://elevagedigital.com/divi5-semantic-elements-doesnt-improve-accessibility/ ⤴
  5. Christopher Morris, Elegant Themes, “How To Create Browser-Native Toggles Using Divi 5’s Semantic Tags.” 2026. [Online]. Available: https://www.elegantthemes.com/blog/divi-resources/how-to-create-browser-native-toggles-using-divi-5s-semantic-tags ⤴
  6. Nick Roach, Elegant Themes, “Divi 5 Official (Beta Ends Today).” 2026. [Online]. Available: https://www.elegantthemes.com/blog/theme-releases/divi-5-official ⤴
  7. Elegant Themes, “How to Make Your Divi Website More Accessible.” 2024. [Online]. Available: https://help.elegantthemes.com/en/articles/10296543-how-to-make-your-divi-website-more-accessible ⤴
  8. Nick Roach, Elegant Themes, “Introducing Custom Attributes For Divi 5.” 2025. [Online]. Available: https://www.elegantthemes.com/blog/theme-releases/custom-attributes ⤴
  9. Nick Roach, Elegant Themes, “Semantic Elements & Custom HTML Wrappers For Divi 5.” 2026. [Online]. Available: https://www.elegantthemes.com/blog/theme-releases/semantic-elements ⤴
  10. W3C, “Success Criterion 1.3.1 Info and Relationships,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#info-and-relationships ⤴
  11. W3C, “Success Criterion 2.1.1 Keyboard,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#keyboard ⤴
  12. W3C, “Success Criterion 4.1.2 Name, Role, Value,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#name-role-value ⤴
  13. W3C, “Success Criterion 3.3.2 Labels or Instructions,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#labels-or-instructions ⤴
  14. W3C, “Success Criterion 3.3.1 Error Identification,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#error-identification ⤴
  15. W3C, “Success Criterion 4.1.3 Status Messages,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#status-messages ⤴
  16. W3C, “Success Criterion 1.1.1 Non-text Content,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#non-text-content ⤴
  17. W3C, “Success Criterion 2.4.7 Focus Visible,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#focus-visible ⤴
  18. W3C, “Success Criterion 2.4.1 Bypass Blocks,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#bypass-blocks ⤴
  19. W3C, “Success Criterion 2.2.2 Pause, Stop, Hide,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#pause-stop-hide ⤴
  20. Elegant Themes, “How to Customize H1-H6 Headings in Divi.” 2024. [Online]. Available: https://help.elegantthemes.com/en/articles/8570577-how-to-customize-h1-h6-headings-in-divi ⤴
  21. Equalize Digital, “Strategies for Creating Accessible Websites Using Divi Theme and Page Builder: Renee Dunn.” 2024. [Online]. Available: https://equalizedigital.com/divi-accessibility-renee-dunn/ ⤴
  22. W3C Web Accessibility Initiative (WAI), “ARIA Authoring Practices Guide: Accordion Pattern.” 2023. [Online]. Available: https://www.w3.org/WAI/ARIA/apg/patterns/accordion/ ⤴
  23. W3C Web Accessibility Initiative (WAI), “ARIA Authoring Practices Guide: Tabs Pattern.” 2023. [Online]. Available: https://www.w3.org/WAI/ARIA/apg/patterns/tabs/ ⤴
  24. Chaucee Stillman, Elegant Themes, “How to Add Labels Above the Fields in Divi’s Contact Form Module.” 2023. [Online]. Available: https://www.elegantthemes.com/blog/divi-resources/how-to-add-labels-above-the-fields-in-divis-contact-form-module ⤴
  25. Aayush, Elegant Themes, “How To Create Better Focus States For Accessible Forms In Divi 5.” 2026. [Online]. Available: https://www.elegantthemes.com/blog/divi-resources/how-to-create-better-focus-states-for-accessible-forms-in-divi-5 ⤴
  26. Elegant Themes, “Understanding the Animation Option Group in Divi 5.” 2026. [Online]. Available: https://help.elegantthemes.com/en/articles/10102631-understanding-the-animation-option-group-in-divi-5 ⤴
  27. Elegant Themes, “How to Create a Child Theme for Divi.” 2024. [Online]. Available: https://help.elegantthemes.com/en/articles/2188070-how-to-create-a-child-theme-for-divi ⤴
  28. Elegant Themes, “Understanding the Heading Text Option Group in Divi 5.” 2026. [Online]. Available: https://help.elegantthemes.com/en/articles/10365216-understanding-the-heading-text-option-group-in-divi-5 ⤴
  29. W3C, “H44: Using label elements to associate text labels with form controls,” 2023, [Online]. Available: https://www.w3.org/WAI/WCAG22/Techniques/html/H44 ⤴
  30. W3C, “Success Criterion 1.4.11 Non-text Contrast,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#non-text-contrast ⤴
  31. W3C, “C39: Using the CSS prefers-reduced-motion query to prevent motion,” 2023, [Online]. Available: https://www.w3.org/WAI/WCAG22/Techniques/css/C39 ⤴
  32. W3C, “Success Criterion 2.3.3 Animation from Interactions,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#animation-from-interactions ⤴
  33. Elegant Themes, “Divi Design Settings & Advanced Module Settings.” 2024. [Online]. Available: https://help.elegantthemes.com/en/articles/8616690-divi-design-settings-advanced-module-settings ⤴
  34. W3C, “Success Criterion 2.4.11 Focus Not Obscured (Minimum),” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#focus-not-obscured-minimum ⤴
  35. Deanna McLean, Elegant Themes, “Divi Product Highlight: Accessibility Bundle.” 2026. [Online]. Available: https://www.elegantthemes.com/blog/divi-resources/divi-product-highlight-accessibility-bundle ⤴
  36. WordPress.org, “Divi Accessibility (accessible-divi): Plugin geschlossen.” 2020. [Online]. Available: https://wordpress.org/plugins/accessible-divi/ ⤴
  37. “Overlay Fact Sheet.” 2021. [Online]. Available: https://overlayfactsheet.com/en/ ⤴
  38. 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/ ⤴
  39. W3C, “Success Criterion 2.4.6 Headings and Labels,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#headings-and-labels ⤴

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.