Elementor accessibility: what the builder covers, what to fix and how to check
Elementor accessibility depends mostly on how you build each page, not on the plugin itself. Elementor gives you the controls to make a page accessible: a heading widget where you choose h1 to h6, an image widget that takes alt text, labels on form fields and a free scanner from Elementor, but it does not apply them for you. The errors we see on pages like these repeat: missing or poor alt text, form fields with only placeholders, low colour contrast, headings chosen for size and not order, icon links with no name and menus or popups that keyboard users cannot use. This guide lists each one, where to fix it in the editor, what Elementor's own accessibility plugin does and does not cover, and how to check your result. We are not lawyers; this is not legal advice.
Is Elementor accessible out of the box?
Partly. Elementor produces ordinary HTML, and WordPress themes supply the page frame, so the result depends on three layers: the theme (the header, menu and footer), Elementor's widgets (heading, image, button, form, accordion, tabs) and what you put in them. A well-built page can meet WCAG 2.1 AA. A page built by choosing whatever looks right often does not. Elementor's own materials describe accessibility as something you set up with its tools; read them as vendor claims and test your own pages. The standard most owners are held to is WCAG 2.1 AA; see ADA website compliance requirements for what the law says.
What is Elementor's accessibility plugin, and what does it do?
Elementor sells and gives away an accessibility plugin first called Ally; the WordPress.org listing now reads "Web Accessibility (formerly known as Ally)". As Elementor describes it, the plugin has a scanner that checks pages against WCAG 2.1 AA and claims to cover more than 180 common issues, an assistant that walks you through each issue and, on some plans, automatic fixes for common errors using AI credits. Some features are gated: AI fixes use credits included with Elementor One. Elementor also offers a free online accessibility checker.
What that means in practice:
- The scanner is a scanner. Like every automated tool it finds only part of the problems in WCAG 2.1 AA. A clean report does not mean a clean site. See WordPress accessibility checker plugin for what plugin scans see and miss.
- Auto-fix is not the same as fixing the page. Ask where a fix is stored. A change saved into your page content stays when you remove the plugin; a patch applied in the browser by a script does not. Read the plugin's description for each fix, and test by switching it off on a staging copy.
- Features and prices change. Confirm what the free and paid versions include on Elementor's page before you rely on a feature.
If you are weighing a plugin against fixing the build, our guide on WordPress accessibility plugin vs fixing the theme covers the trade-off.
The seven errors most Elementor pages have, and the fix for each
1. Headings chosen for size, not order
Builders make it easy to pick a heading level because it looks right. Screen reader users move through a page by headings, so the order matters: one h1, then h2 for sections, h3 under them, no skipping. In the Heading widget, set the HTML tag under Content and use the typography settings to change how it looks. A big line of text that is not a heading should be a text editor widget, not an h2.
2. Images with no alt text, or file names
Alt text comes from the WordPress media library by default, so an upload with a file name like IMG_4022 gives you that as the alt text. Open the media library, write a short description of what the picture shows and why it is there, and leave it empty for purely decorative images. Check the Image widget and the background images too: a picture set as a section background has no alt text at all, so move meaningful pictures into an Image widget.
3. Forms that rely on placeholders
A placeholder disappears when you type and is not a reliable label for a screen reader. In the Form widget, turn on labels for each field (Show Labels) and keep the placeholder as a hint only. Mark required fields in the label text and not by colour alone, and check that error messages say what went wrong.
4. Low colour contrast
Text needs a contrast ratio of 4.5 to 1 against its background, or 3 to 1 for large text. Light grey on white, white on a pale brand colour and text over a photo fail often. Test the colours in the global colour settings and fix them once so every page follows. Our WCAG colour contrast checker guide lists tools and fixes for common colours.
5. Icon links and buttons with no name
An icon button for a phone number, a social link or a menu toggle may have no text for a screen reader to announce. Add a visible label or an accessible name in the link or button settings (the ARIA label field in the advanced options), and make link text mean something out of context: "Book a consultation", not "click here".
6. Menus, popups and sliders that need a mouse
Hover menus, popups and carousels are where keyboard users get stuck. Check you can open a menu with Tab and Enter, reach every submenu item, close a popup with Escape and return to where you were. Stop auto-playing sliders or give a visible pause control. If a popup traps focus with no way out, make it simpler or remove it.
7. Focus you cannot see
Many themes and custom CSS remove the outline that shows which link or button is selected. Tab through the page: if you lose track of where you are, restore a clear focus style in your theme or custom CSS settings.
Elementor accessibility checklist you can run this week
- Scan the home page, your contact or booking page and your most visited service page with two free tools. See the free checker guide.
- Walk each of those pages with only the keyboard: Tab, Shift+Tab, Enter, Space, Escape.
- Check the heading outline: one h1, no skipped levels.
- Write alt text for every meaningful image in the media library.
- Turn on labels in every Form widget.
- Test your main text and button colours for contrast and fix them in the global settings.
- Name every icon-only link and button.
- Open the mobile menu and popups with the keyboard alone.
- Publish an honest accessibility statement. See the statement template.
The longer list is our ADA compliant website checklist, and the WCAG 2.1 AA checklist covers all the criteria.
A worked example: a 10-page Elementor site for an electrician
An electrician has a ten-page site on WordPress with Elementor. A free scan of the home and quote pages finds nine errors: five gallery photos with file names as alt text, a quote form with placeholders and no labels, a pale grey footer that fails contrast, and a heading on the home page set as an h4 because it looked right. A keyboard test shows the mobile menu opens only on tap. The owner does the fixes in an afternoon: writes alt text in the media library, turns on form labels, darkens the footer colour in the global settings, changes the heading tag, and asks the theme developer to make the menu toggle a real button. A rescan shows the counts drop and the menu opens with the keyboard. The owner then writes a short statement that lists a remaining issue in the scheduling embed. No plugin was needed for any of it, though one could have helped find the errors. The fixes live in the page content and the theme, so they stay.
Do you need an accessibility plugin or overlay on Elementor?
You need a scan and a person who fixes what it finds. A scanning plugin can be a convenient way to see issues inside the editor, and some owners like the assistant's step-by-step prompts. An overlay widget is a different product: it adds a toolbar and patches pages in the visitor's browser. The accessibility professionals' Overlay Fact Sheet argues overlays do not make a site compliant and can interfere with assistive technology, and sites with widgets have been sued. See accessiBe alternatives and accessibility overlay lawsuit. A one-time fix of the errors costs less over three years than a subscription for most small sites; see ADA website compliance cost.
When to ask for help
Ask a developer to fix the theme layer if the menu, the focus style or the header markup is the problem, because Elementor's editor cannot change those. Ask for help if you have received a demand letter, and speak to a lawyer who handles ADA website cases first. For the typical page-level errors above, a written list with the fix for your platform is usually enough; that is what Site Record provides. See accessibility remediation services for how to hire for the harder cases.
On another platform? See ADA compliance Shopify and ADA compliant website builder for Wix, Squarespace, Webflow and others.
Frequently asked questions
Is Elementor ADA compliant?
Elementor can produce an accessible page, but compliance depends on how you build it: headings, alt text, labels, colour and keyboard use. The law judges your site, not your builder.
Does Elementor have an accessibility plugin?
Yes. Elementor offers a plugin first called Ally, now listed as Web Accessibility, with a scanner and an assistant. Some features need paid credits.
Can I make an Elementor site WCAG 2.1 AA compliant?
Often yes, for common errors, by fixing alt text, labels, contrast, headings and keyboard use. Check with a scan and a keyboard walk.
Is an Elementor accessibility widget enough?
No script on its own makes a site compliant. A toolbar does not change the code of your pages.
Where do I set alt text in Elementor?
In the WordPress media library for the image, and check it in the Image widget. Background images have no alt text, so use an Image widget for meaningful pictures.
How do I check my Elementor site?
Scan with two free tools, then walk the page with the keyboard. Repeat after fixes.
Sources
- Elementor, Ally web accessibility product page, help centre and blog; WordPress.org plugin listing (vendor descriptions, read 2026-11-15).
- Overlay Fact Sheet, overlayfactsheet.com.
- W3C, Web Content Accessibility Guidelines 2.1, including contrast (1.4.3) and labels (3.3.2).