Divi WCAG 2.1 Checker

WCAG 2.1 for Divi Sites

WCAG 2.1 became a W3C Recommendation in June 2018. It added criteria for mobile, low vision and cognitive accessibility to WCAG 2.0, and it is the standard named in the US Department of Justice rule for state and local government websites, in EN 301 549 V3.2.1 and in most accessibility settlements.

This checker runs the free scan with the WCAG 2.1 AA preset, so the results match the standard your contract, policy or regulator is most likely to name for a Divi site.

On Divi, WCAG 2.1 issues often come from layout settings: sections with fixed heights that cut off text when spacing increases, pale button borders, and hover effects that hide content from keyboard users.

Who Should Run the Divi WCAG 2.1 Checker

• Divi site owners whose contracts or policies name WCAG 2.1 AA.
• State and local government bodies, under the ADA Title II rule.
• Businesses responding to an ADA demand letter, which usually cites WCAG 2.1 AA.
• Public sector bodies in the EU, under the Web Accessibility Directive.

WCAG 2.1 Criteria That Often Fail on Divi

• 1.3.5 Identify Input Purpose

  Form fields that collect personal data, such as name, email and address, need the right autocomplete attribute.

• 1.4.10 Reflow

  Content must reflow at 320 CSS pixels wide, the same as 400% zoom, without scrolling in two directions.

• 1.4.11 Non-text Contrast

  Buttons, form borders, icons and focus indicators need a contrast ratio of at least 3:1.

• 1.4.12 Text Spacing

  Text must stay readable when users increase line, paragraph, letter and word spacing.

• 1.4.13 Content on Hover or Focus

  Tooltips and menus that appear on hover or focus must be dismissible, hoverable and stay visible.

• 4.1.3 Status Messages

  Messages such as “added to cart” or form errors must be announced to screen readers without moving focus.

Where Divi Sites Usually Fail WCAG 2.1

These problems come up again and again on Divi sites, and each one fails WCAG 2.1. The Divi accessibility checker explains how to fix them in Divi.

• Headings and text modules. Text and Blurb modules let you pick a heading tag, and layout packs often choose it for the look, so pages skip levels or have more than one h1.
• Hover-only dropdown menus. Menus that open on hover and cannot be opened with the keyboard cut off every page below the top level for keyboard and touch users.
• Contact form fields. The Contact Form module often uses a field’s title as its placeholder, so the visible name vanishes as soon as someone types.
• Sliders, video backgrounds and parallax. Auto-advancing sliders, looping video backgrounds and scroll effects can start on their own with no way to pause them.
• Text over images and overlays. Fullwidth headers and hero sections set text on top of photos, where contrast depends on the image and the overlay color.

Worried about ADA claims as well? The Divi ADA compliance checker covers the Divi risks behind most complaints.

What to Test by Hand on Divi

Automated testing finds many, but not all, WCAG 2.1 failures. Check these yourself after the scan:

1. Zoom to 400% and check nothing is cut off or needs scrolling in two directions (1.4.10).
2. Apply increased text spacing with a bookmarklet and check text is still readable (1.4.12).
3. Open hover menus and tooltips and check you can dismiss them with Escape (1.4.13).
4. Rescan after each fix. Continuous monitoring rescans up to 500 URLs per domain daily and keeps a dated record in the Compliance Vault.

Start 3-day free trial

Related Guides

• WCAG 2.1 AA CheckerThe WCAG 2.1 standard in full, for any website.
• WCAG 4.1.2 Name, Role, Value Explained in Plain EnglishWCAG 4.1.2 Name, Role, Value explained simply: give every control a name, role and state with native HTML and ARIA, with code examples and how to test.
• WCAG 1.4.3 Contrast (Minimum) Explained in Plain EnglishWCAG 1.4.3 Contrast (Minimum) explained simply: the 4.5:1 and 3:1 ratios, what counts as large text, the exceptions, fixes and how to test your colors.
• Keyboard Accessibility TestingA practical guide to keyboard accessibility testing: what to check, the exact keys to use, and a component-by-component reference table mapped to WCAG.
• WCAG Success Criteria LibraryLook up any criterion the scan flags, in plain language.

Divi WCAG 2.1 Checker: Frequently Asked Questions