Elementor, Divi, Astra
Elementor vs. Divi vs. Astra: WordPress Page Builder DOM & Keyboard Accessibility Scorecard
Verdict
WordPress powers over 40% of the web, and page-builder defaults determine whether millions of local business sites pass or fail WCAG 2.2 Level AA. Across our WordPress builder specimen tests (70/100 composite), Astra ships the cleanest semantic header and skip-link foundation, Elementor has improved ARIA attributes on newer Flexbox/Grid widgets while still risking popup focus traps, and legacy Divi modules require the heaviest manual remediation for keyboard navigation.
- Critical / serious
- 0 / 2
- Moderate / minor
- 0 / 0
- Keyboard
- Fail
- Overlay script
- None
axe-core rules triggered: color-contrast, link-name · Scanned
Key findings
- Astra Theme: Ships a working skip-to-content link, clean landmark structure, and lean DOM depth out of the box, scoring highest among the three when paired with native Gutenberg blocks.
- Elementor: Newer Accordion and Menu widgets include improved ARIA roles, yet Elementor Popup Builder modals and icon-only social/search links frequently ship without accessible names unless manually configured.
- Divi (Legacy 4.x vs. Divi 5): Historically relied on non-button div triggers for accordions/toggles and suppressed :focus outlines in starter layouts, requiring explicit CSS and keyboard verification.
- Universal Builder Trap: Starter template kits across all three ecosystems routinely use h4/h5 tags for visual sizing and set muted body copy below 4.5:1.
Breakdown
| Criterion | Astra (Block / Native) | Elementor (3.x Pro) | Divi |
|---|---|---|---|
| Default Skip Link (2.4.1) | Included & focus-visible | Supported with Hello + config | Often missing on custom headers |
| Mobile Hamburger Button (4.1.2) | Labeled <button> + aria-expanded | Needs label check on custom navs | Historically <span>/<a> without state |
| Accordion / FAQ Keyboard | Clean with native <details> blocks | Improved ARIA; check heading nesting | Legacy modules failed Space/Enter |
| DOM Depth & Speed | Lean (~400-700 nodes) | Moderate (~1,200-2,200 nodes) | Heavy on legacy shortcode layouts |
Failing markup and the fix
.elementor-button:focus { outline: none; }
<a href="https://instagram.com/example" class="social-icon">
<i class="fab fa-instagram"></i>
</a>
<h1>Roofing Services</h1>
<h4>Request an Estimate</h4>.button:focus-visible { outline: 3px solid #0b57d0; outline-offset: 3px; }
<a href="https://instagram.com/example" aria-label="Follow Example Roofing on Instagram">
<svg aria-hidden="true" viewBox="0 0 24 24">...</svg>
</a>
<h1>Roofing Services</h1>
<h2>Request an Estimate</h2>What are the first three fixes every Elementor or Divi agency should apply?
First, audit your global CSS for any rule setting outline: none on buttons, links, or inputs without restoring a high-contrast :focus-visible ring (>= 3:1 contrast). Second, inspect every icon-only link in your header and footer (magnifying glass search, shopping bag, Instagram, Facebook) and supply an explicit aria-label.
Third, stop choosing heading levels (h1 through h6) based on font size. Set sequential semantic levels (one h1, followed by h2 section titles and h3 card titles) and assign typography presets via classes.
Why does native WordPress Block Editor + Astra score cleaner than heavy builders?
Every extra wrapper div, custom slider script, and non-native popup adds surface area where ARIA state synchronization can drift after a plugin update. Native HTML elements (<nav>, <button>, <details>, <dialog>) carry browser-tested keyboard handling with zero JavaScript maintenance.
Questions
Can an existing Elementor website reach WCAG 2.2 Level AA without rebuilding from scratch?
Yes, in most cases. Fixing heading hierarchy, restoring :focus-visible outlines, labeling icon buttons and form fields, replacing broken popups, and darkening low-contrast color tokens resolves the vast majority of Elementor WCAG violations.
Has a vendor release fixed something above? Request a free re-test or read how we test.