Skip to main content

Elementor Accessibility: 9 Common Barriers and Fixes

Information about the article

Portrait of Dmitry Dugarev

Author: Dmitry Dugarev

Consultant for digital accessibility & IT compliance

Last updated on:

You build or maintain websites with Elementor, and you want them to be accessible. This guide to Elementor accessibility shows you how to get there without rebuilding your pages. I audit Elementor websites by hand, with a keyboard and a screen reader. Below are the barriers I find most often and the setting that fixes each one.

In short
  • Elementor gives you plenty of useful settings. But your page only becomes accessible through the choices you make in each widget.
  • In classic widgets, an aria-label added under "Advanced > Attributes" ends up on the wrapper, not on the link [1]. Use the link options instead [2].
  • A Button widget without a link is an <a> without href. Keyboard users cannot reach it [3], [4].
  • The "Web Accessibility" plugin (formerly Ally) does not replace an audit. Elementor says so itself [5].

Is Elementor accessible?​

Elementor's Help Center says the editor already has the technology it needs for accessibility built in [6]. According to Elementor, all you have to do is supply accessible content [6]. That is only partly true.

Elementor does offer important settings. You choose the level of every heading [7]. You show or hide the labels in a form [8]. A container can get an HTML tag such as main or nav [9]. Scroll and mouse effects switch off when the visitor has turned on "reduce motion" in their operating system [10].

But these settings only help when someone sets them correctly. In my audits, most barriers do not come from Elementor's code. They come from decisions made in the editor.

Elementor, the EAA and the BFSG​

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 [11]. The BFSG covers, among other things, e-commerce services (§ 1(3) No. 5 BFSG) [11]. In practice, these are mainly websites where consumers enter into a contract. Microenterprises that provide services are exempt (§ 3(3) BFSG) [11]. The article on the microenterprise exemption explains the details. Whether you build the site with Elementor, Divi or Gutenberg makes no difference.

I explain who else is affected in the guide to WordPress accessibility. To find out whether the BFSG applies to your website, use the BFSG relevance check. I audit against WCAG 2.2, Levels A and AA [12].

Elementor accessibility: 9 common barriers and how to fix them​

For each barrier, I name the WCAG criterion and the Elementor setting that fixes it. The code examples are simplified.

1. Headings and landmarks missing from the code​

On many pages, the heading level is chosen by font size. The result is an H1 followed directly by an H4. Or a section title is just bold text. But screen reader users navigate a page by jumping from heading to heading. Bold text in place of a heading fails WCAG 1.3.1 [13], [14]. Skipped levels such as H1 → H4 are confusing. The W3C advises avoiding them where possible [15].

In the Heading widget, you pick the level from H1 to H6 under "HTML Tag" [7]. According to Elementor, the tag does not change how the heading looks, as long as your theme or Site Settings do not style that tag [7]. So you can fix the level and keep the font size in the widget.

<!-- Before: level chosen by font size -->
<h1>Tax advice in Cologne</h1>
<h4>Our services</h4>
<p class="elementor-heading-title"><strong>Payroll</strong></p>

<!-- After: level chosen by page structure -->
<h1>Tax advice in Cologne</h1>
<h2>Our services</h2>
<h3>Payroll</h3>

The same goes for the main areas of the page. The header, navigation, main content and footer should be marked up as landmarks. Elementor recommends this in its own guide [6]. Landmarks let screen reader users jump straight to the content (WCAG 1.3.1 and 2.4.1) [13], [16], [17].

In the container settings, go to "Layout > HTML Tag" and pick the right element [18]. The options include header, nav, main and footer [9]. For Theme Builder templates, you set the tag in the template settings [19].

<!-- Before: the container's default tag -->
<div class="e-con">…</div>

<!-- After: HTML Tag "main" selected -->
<main class="e-con">…</main>

Also test the "Skip to content" link. The Hello theme includes one [6]. If you use the "Elementor Canvas" or "Elementor Full Width" template, one element needs the CSS ID content [6]. Otherwise, the skip link has no target.

In the Icon widget, an Instagram icon is a link without any text. Elementor hides the icon from screen readers with aria-hidden="true" [20]. So the link has no name. The Social Icons widget is different: it adds the network's name by itself [21]. Every control needs an accessible name (WCAG 4.1.2) [22], [23].

There is a trap here. Elementor's own guide tells you to add ARIA labels as "Custom attributes" [6]. It points to the field under "Advanced > Attributes" in Elementor Pro. But in classic widgets up to Editor V3, Elementor puts these attributes on the wrapper [1]. Your aria-label then ends up on a div, not on the link. WAI-ARIA 1.2 prohibits aria-label on elements with the role generic, such as a plain div [24]. Elementor closed a bug report about this and pointed to the link options [25].

Use the cog icon on the link field instead. There you will find a "Custom Attributes" field [2]. Elementor puts these attributes directly on the <a> element [2]. This feature is in the source code of the free version [26]. Enter, for example, aria-label|Barrierenlos on Instagram. A comma separates multiple attributes [2]. So keep commas out of your aria-label text.

<div class="elementor-widget-icon" aria-label="Instagram">
<a class="elementor-icon" href="https://www.instagram.com/…">
<svg aria-hidden="true">…</svg>
</a>
</div>

Use aria-label mainly where visible text is not possible [27]. To check the result, right-click the icon, choose "Inspect", and see whether the aria-label sits on the <a>. The glossary entry on aria-label has more details. If a button already has visible text, its name must contain that text (WCAG 2.5.3) [28]. A "Learn more" button with the name "View services" confuses people who use voice control.

The Button widget always outputs an <a> element. If the link field is empty, the element only gets role="button", but no href [3]. Under the HTML standard, an <a> is only focusable by default when it has an href [4]. So you cannot reach this button with the Tab key (WCAG 2.1.1) [29].

Popups cause a similar problem. Elementor lets you trigger a popup from any element through a CSS class [30]. If you add the class to an image or a container, only mouse users can open the popup. The W3C lists such constructs as failures [31], [32].

<!-- Before: no href, cannot be reached with Tab -->
<a class="elementor-button" role="button">Request a quote</a>

<!-- After: link field filled in -->
<a class="elementor-button elementor-button-link" href="/contact/">Request a quote</a>

So always fill in the link field. For popups, use the dynamic popup action in the link field [30]. This follows the W3C's first rule of ARIA use: use the native HTML element when it fits [33].

4. Forms without visible labels​

The Form widget has a switch that hides the labels [8]. Many designs then rely on the placeholder alone. But the placeholder disappears as soon as someone types, and it often has low contrast [34]. Screen readers do not treat it as a label [34]. WCAG 3.3.2 requires labels or instructions for every input [35].

Set the "Label" switch to "Show". Use the placeholder only for an example, such as "max@example.com". Show the required-field marker as well [8]. Our accessible form pattern explains the basics. If you use Contact Form 7 instead of the Form widget, read the article on Contact Form 7.

5. Popups without focus management​

A popup with an overlay is a modal dialog. When it opens, focus must move into the dialog [36]. The Escape key closes it. Focus then returns to the element that opened it [36].

Several switches in Elementor's popup settings work against this [30]:

  • Close Button: Set it to "Show". Otherwise, there is no close button.
  • Show Button After / Show Close Button After: Leave the field empty. Otherwise, the close button is missing for the first few seconds.
  • Prevent Closing on ESC Key: Leave this switch off. Otherwise, the Escape key no longer closes the popup.
  • Automatically Close After: Leave the field empty. Otherwise, the popup closes after a fixed time (WCAG 2.2.1) [37].

Then test every popup with the Tab key. Focus must not land on the page behind the popup. While the popup is open, focus stays inside it [36]. But keyboard users must be able to leave it, with Escape or the close button (WCAG 2.1.2) [38]. The focus order must be logical (WCAG 2.4.3) [39].

6. Tabs and accordions​

In the Accordion widget, you set the level of the titles under "Title HTML Tag" [40]. Match it to the page structure, for example H3 below an H2. The W3C pattern puts a button inside a heading [41].

Elementor does it the other way round. The Accordion widget uses <details> and puts the heading inside the <summary> element [42]. A <summary> counts as a button. Browsers and screen readers do not reliably recognize headings inside it [43]. So use a screen reader to check whether the titles appear in its list of headings.

<!-- W3C pattern: button inside the heading -->
<h3><button aria-expanded="false">Delivery times</button></h3>

<!-- Elementor: heading inside summary -->
<details>
<summary aria-expanded="false"><span><h3>Delivery times</h3></span></summary>
</details>

The source code reveals two more issues. On page load, only the first title can be reached with Tab. The others have tabindex="-1" [42]. In the W3C pattern, every title is part of the tab order [41]. Also, the wrapping div carries an English aria-label [42]. On a German-language site, that label does not match the page language.

In tabs, the Tab key moves focus to the active tab. The arrow keys switch between tabs [44]. Test both widgets with a keyboard and a screen reader. If you find a barrier inside the widget, you usually need custom code in a child theme or a different widget.

7. Sliders and carousels with autoplay​

The Carousel widget plays automatically until you set "Autoplay" to "No" [45]. But moving content needs a way to pause it (WCAG 2.2.2) [46]. For this, Elementor offers "Pause on hover" and "Pause on interaction" [45].

That is not quite enough. The W3C also recommends a visible button to pause and resume [47]. The carousel should also pause when it receives keyboard focus [47]. The simplest fix is to turn autoplay off. Our accessible carousel pattern has more details.

8. Global colors with too little contrast​

Elementor stores your site's colors in one place as global colors [48]. If a global color has too little contrast, the error shows up on every page. The upside: you fix it in one place.

Normal text needs a contrast of at least 4.5:1 against its background (WCAG 1.4.3) [49]. If an input field is only recognizable by its border, the border needs at least 3:1. The same applies to icons that people need to understand the content (WCAG 1.4.11) [50]. Check every global color with our contrast checker. When you correct a global color, the change applies everywhere.

9. Animations and motion effects​

Under "Motion Effects", Elementor offers scrolling effects such as parallax, mouse effects and entrance animations [10]. Elementor switches these motion effects off when the visitor has turned on "reduce motion" in their operating system [10]. You have to test other animations yourself, such as hover effects or Lottie.

If an animation starts automatically and runs longer than 5 seconds, users need a way to pause it. One example is text that changes in a loop. WCAG 2.2.2 requires this at Level A [46]. Nothing may flash more than three times per second (WCAG 2.3.1, Level A) [51]. WCAG 2.3.3, on animation from interactions, is Level AAA [52]. I still recommend it as a benchmark.

Elementor's "Web Accessibility" plugin (formerly Ally)​

Elementor offers its own accessibility plugin. It used to be called "Ally" and is now called "Web Accessibility" [5]. WordPress.org lists more than 500,000 active installations as of September 2026 [5]. It has three parts [5]:

  • Accessibility Assistant: a scanner for more than 180 issues under WCAG 2.1 AA, not WCAG 2.2 [53].
  • Usability widget: a floating menu that lets visitors change font size and contrast and stop animations.
  • Accessibility statement generator: creates a statement and publishes it as a page.

The scanner is useful for a first overview. Germany's federal and state monitoring bodies for the accessibility of information technology have assessed overlays [54]. They define an overlay as software that is meant to improve a website's accessibility [54]. The usability widget is such an overlay. According to their assessment, an overlay does not necessarily make a website accessible [54]. I explain this in more detail in the article on overlays and compliance.

Elementor itself says the plugin is no substitute for a thorough audit [5]. It is not meant to make a website fully legally compliant [5]. And no automated tool can promise full accessibility [5]. That is why I check all 55 WCAG 2.2 A and AA criteria by hand in the Basis-Audit for €490 plus VAT.

One thing stands out about the "Site-Wide Fixes". These fixes are only available on the paid plan [55]. If you remove a fix, the barrier counts as open again [55]. So fix barriers directly in the widget settings instead. The article on WordPress accessibility plugins compares more tools.

How to make Elementor accessible without a rebuild, step by step​

You do not need to rebuild your Elementor website. Most fixes are settings in your existing widgets.

Start with the Theme Builder templates​

The header, footer and popups appear on every page. Fix landmarks, icon links, the menu and the cookie banner there first. Each fix then applies to the whole website.

Check global colors and fonts​

Correct the contrast in your global colors. That way, you do not have to change every widget one by one.

Fix page templates and forms​

Next come the templates for posts and products, and all forms. A form is often where the customer enters into the contract.

Check individual pages and content​

Finally, check the headings, alt text and link text on every page. Elementor recommends entering the alt text in the Media Library [56]. The article on alt text for images shows what good alt text looks like.

Start with our free BFSG check. It tests 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, because a tool cannot judge things like the focus order in a popup. If you would rather not do the work yourself, I can fix the barriers in your existing Elementor layout for you.

Frequently asked questions (FAQ)​

Is an Elementor website BFSG compliant?​

Not by default. Elementor is a workable foundation. But many barriers come from settings in the editor, such as hidden form labels or buttons without a link. Whether the BFSG applies to your website depends on what you offer, not on your page builder [11].

Do I need Elementor Pro for accessibility?​

Not for everything. You add an aria-label to links through the link options [2]. This feature is part of the free version [26]. The "Advanced > Attributes" field is only available in Pro. In classic widgets up to Editor V3, it puts attributes on the wrapper [1].

Does the Ally plugin make my Elementor website BFSG compliant?​

No. Elementor itself says that the plugin does not replace an audit [5]. According to Germany's monitoring bodies for the accessibility of information technology, an overlay does not necessarily make a website accessible [54]. You need to fix the barriers in the widgets.

How do I add an aria-label in Elementor?​

Open the widget and click the cog icon in the link field. Under "Custom Attributes", enter something like aria-label|Call customer service [2]. Do not use a comma in the text, because a comma separates multiple attributes. Then check in your browser whether the attribute sits on the <a> element.


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 Elementor and its plugins comes from the sources cited, as of September 2026. Settings and features may change with new versions.

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. Elementor, “Custom attributes.” 2026. [Online]. Available: https://elementor.com/help/custom-attributes-pro/ ⤴
  2. Elementor, “Quellcode: includes/widgets/traits/button-trait.php.” 2026. [Online]. Available: https://github.com/elementor/elementor/blob/main/includes/widgets/traits/button-trait.php ⤴
  3. WHATWG, “HTML Living Standard.” 2024. [Online]. Available: https://html.spec.whatwg.org/ ⤴
  4. Elementor, “Web Accessibility (formally known as Ally) – WCAG Scanning, Guided Fixes, Usability Widget – WordPress-Plugin.” 2026. [Online]. Available: https://wordpress.org/plugins/pojo-accessibility/ ⤴
  5. Elementor, “Make your website accessible.” 2024. [Online]. Available: https://elementor.com/help/make-your-website-accessible/ ⤴
  6. Elementor, “Heading widget.” 2026. [Online]. Available: https://elementor.com/help/heading-widget/ ⤴
  7. Elementor, “Form widget.” 2026. [Online]. Available: https://elementor.com/help/form-widget/ ⤴
  8. Elementor, “Quellcode: includes/elements/container.php.” 2026. [Online]. Available: https://github.com/elementor/elementor/blob/main/includes/elements/container.php ⤴
  9. Elementor, “Motion effects.” 2026. [Online]. Available: https://elementor.com/help/motion-effects/ ⤴
  10. 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/ ⤴
  11. W3C, “Web Content Accessibility Guidelines (WCAG) 2.2.” 2023. [Online]. Available: https://www.w3.org/TR/WCAG22/ ⤴
  12. W3C, “Success Criterion 1.3.1 Info and Relationships,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#info-and-relationships ⤴
  13. W3C, “F2: Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text,” 2023, [Online]. Available: https://www.w3.org/WAI/WCAG22/Techniques/failures/F2 ⤴
  14. W3C Web Accessibility Initiative (WAI), “Page Structure Tutorial: Headings.” 2023. [Online]. Available: https://www.w3.org/WAI/tutorials/page-structure/headings/ ⤴
  15. W3C, “Success Criterion 2.4.1 Bypass Blocks,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#bypass-blocks ⤴
  16. W3C, “ARIA11: Using ARIA landmarks to identify regions of a page,” 2023, [Online]. Available: https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA11 ⤴
  17. Elementor, “Container Layout tab settings.” 2026. [Online]. Available: https://elementor.com/help/container-layout-tab-settings/ ⤴
  18. Elementor, “How to Add HTML Tags to My Templates.” 2023. [Online]. Available: https://elementor.com/help/how-to-add-html-tags-to-my-templates/ ⤴
  19. Elementor, “Quellcode: includes/widgets/icon.php.” 2026. [Online]. Available: https://github.com/elementor/elementor/blob/main/includes/widgets/icon.php ⤴
  20. Elementor, “Quellcode: includes/widgets/social-icons.php.” 2026. [Online]. Available: https://github.com/elementor/elementor/blob/main/includes/widgets/social-icons.php ⤴
  21. W3C, “Success Criterion 4.1.2 Name, Role, Value,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#name-role-value ⤴
  22. W3C, “F68: Failure of Success Criterion 4.1.2 due to a user interface control not having a programmatically determined name,” 2023, [Online]. Available: https://www.w3.org/WAI/WCAG22/Techniques/failures/F68 ⤴
  23. World Wide Web Consortium (W3C), “Accessible Rich Internet Applications (WAI-ARIA) 1.2.” 2023. [Online]. Available: https://www.w3.org/TR/wai-aria-1.2/ ⤴
  24. Amber Hinds, “Accessibility: Adding an aria-label in custom attributes on a button doesn’t add it to the a tag. Issue #25128.” 2024. [Online]. Available: https://github.com/elementor/elementor/issues/25128 ⤴
  25. Elementor, “Quellcode: includes/controls/url.php.” 2026. [Online]. Available: https://github.com/elementor/elementor/blob/main/includes/controls/url.php ⤴
  26. W3C, “ARIA14: Using aria-label to provide an accessible name where a visible label cannot be used,” 2023, [Online]. Available: https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA14 ⤴
  27. W3C, “Success Criterion 2.5.3 Label in Name,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#label-in-name ⤴
  28. W3C, “Success Criterion 2.1.1 Keyboard,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#keyboard ⤴
  29. Elementor, “Configure a popup.” 2026. [Online]. Available: https://elementor.com/help/popups/ ⤴
  30. W3C, “F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function,” 2023, [Online]. Available: https://www.w3.org/WAI/WCAG22/Techniques/failures/F54 ⤴
  31. W3C, “F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML without providing a role for the control,” 2023, [Online]. Available: https://www.w3.org/WAI/WCAG22/Techniques/failures/F59 ⤴
  32. W3C Web Accessibility Initiative (WAI), “W3C Using Aria: Erste Regel der ARIA-Nutzung.” 2018. [Online]. Available: https://www.w3.org/TR/using-aria/#firstrule ⤴
  33. W3C Web Accessibility Initiative (WAI), “W3C Forms Tutorial: Placeholder text.” 2023. [Online]. Available: https://www.w3.org/WAI/tutorials/forms/instructions/#placeholder-text ⤴
  34. W3C, “Success Criterion 3.3.2 Labels or Instructions,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#labels-or-instructions ⤴
  35. W3C Web Accessibility Initiative (WAI), “ARIA Authoring Practices Guide: Dialog (Modal) Pattern.” 2023. [Online]. Available: https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/ ⤴
  36. W3C, “Success Criterion 2.2.1 Timing Adjustable,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#timing-adjustable ⤴
  37. W3C, “Success Criterion 2.1.2 No Keyboard Trap,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#no-keyboard-trap ⤴
  38. W3C, “Success Criterion 2.4.3 Focus Order,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#focus-order ⤴
  39. Elementor, “Accordion widget with nested elements.” 2026. [Online]. Available: https://elementor.com/help/accordion-widget-with-nested-elements/ ⤴
  40. W3C Web Accessibility Initiative (WAI), “ARIA Authoring Practices Guide: Accordion Pattern.” 2023. [Online]. Available: https://www.w3.org/WAI/ARIA/apg/patterns/accordion/ ⤴
  41. Elementor, “Quellcode: modules/nested-accordion/widgets/nested-accordion.php.” 2026. [Online]. Available: https://github.com/elementor/elementor/blob/main/modules/nested-accordion/widgets/nested-accordion.php ⤴
  42. Scott O’Hara, “The details and summary elements, again.” 2022. [Online]. Available: https://www.scottohara.me/blog/2022/09/12/details-summary.html ⤴
  43. W3C Web Accessibility Initiative (WAI), “ARIA Authoring Practices Guide: Tabs Pattern.” 2023. [Online]. Available: https://www.w3.org/WAI/ARIA/apg/patterns/tabs/ ⤴
  44. W3C, “Success Criterion 2.2.2 Pause, Stop, Hide,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#pause-stop-hide ⤴
  45. Elementor, “View and edit global colors.” 2026. [Online]. Available: https://elementor.com/help/view-and-edit-global-colors/ ⤴
  46. W3C, “Success Criterion 1.4.3 Contrast (Minimum),” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#contrast-minimum ⤴
  47. W3C, “Success Criterion 1.4.11 Non-text Contrast,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#non-text-contrast ⤴
  48. W3C, “Success Criterion 2.3.1 Three Flashes or Below Threshold,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#three-flashes-or-below-threshold ⤴
  49. W3C, “Success Criterion 2.3.3 Animation from Interactions,” 2023, [Online]. Available: https://www.w3.org/TR/WCAG22/#animation-from-interactions ⤴
  50. Elementor, “Ally: Web accessibility plugin for WordPress.” 2026. [Online]. Available: https://elementor.com/products/ally-web-accessibility/ ⤴
  51. Ü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 ⤴
  52. Elementor, “Using Site-Wide Fixes with Web Accessibility.” 2026. [Online]. Available: https://elementor.com/help/using-global-remediation-with-ally-assistant/ ⤴
  53. Elementor, “Image widget.” 2026. [Online]. Available: https://elementor.com/help/image-widget/ ⤴

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.