Divi WCAG 2.2 Checker

WCAG 2.2 for Divi Sites

WCAG 2.2 became a W3C Recommendation in October 2023. It keeps every WCAG 2.1 requirement except 4.1.1 Parsing and adds six success criteria at Level A and AA, mostly about people with low vision, motor disabilities and cognitive disabilities. A Divi site that meets WCAG 2.2 AA also meets 2.1 AA and 2.0 AA.

This checker runs the same free scan as the Divi accessibility checker with the WCAG 2.2 AA preset, so the results include the 2.2 rules that automated testing can check.

On Divi, WCAG 2.2 issues often come from design choices made in the editor: small icon buttons, sticky headers and announcement bars, and carousels that only respond to swiping or dragging. Check each section template once and fix it there.

Who Should Run the Divi WCAG 2.2 Checker

• Divi site owners who want the most current, future-proof target.
• Teams redesigning a Divi site, where adopting the latest version costs little extra.
• Organizations selling into the EU, where EN 301 549 V4.1.1 now uses WCAG 2.2.
• Anyone preparing for new rules, which tend to adopt the latest WCAG version.

The New WCAG 2.2 Criteria to Check on Divi

• 2.4.11 Focus Not Obscured (Minimum)

  Sticky headers, cookie banners and chat widgets must not completely hide the element that has keyboard focus.

• 2.5.7 Dragging Movements

  Anything that works by dragging, such as sliders, carousels and sortable lists, needs a single-pointer alternative.

• 2.5.8 Target Size (Minimum)

  Buttons and links need a target of at least 24 by 24 CSS pixels, or enough space around them. Icon buttons and pagination links often fail.

• 3.2.6 Consistent Help

  Help such as a contact link or chat must appear in the same place on every page that has it.

• 3.3.7 Redundant Entry

  Do not ask for the same information twice in one process, such as shipping and billing addresses, without offering to fill it in.

• 3.3.8 Accessible Authentication (Minimum)

  Sign-in must not depend on a cognitive test, such as remembering a password without paste support or solving a puzzle.

Where Divi Sites Usually Fail WCAG 2.2

These problems come up again and again on Divi sites, and each one fails WCAG 2.2. 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.2 failures. Check these yourself after the scan:

1. Tab through each page and check the focused element is never fully covered by sticky content (2.4.11).
2. Try every drag interaction with a single click or tap instead (2.5.7).
3. Sign in with a password manager and check paste works (3.3.8).
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.2 AA CheckerThe WCAG 2.2 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.2 Checker: Frequently Asked Questions