Drupal WCAG 2.2 Checker

WCAG 2.2 for Drupal 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 Drupal 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 Drupal accessibility checker with the WCAG 2.2 AA preset, so the results include the 2.2 rules that automated testing can check.

On Drupal sites, WCAG 2.2 issues usually come from the theme and plugins rather than core: icon-only social links below 24 pixels, sticky headers that cover focused links, and login or comment forms that block password managers.

Who Should Run the Drupal WCAG 2.2 Checker

• Drupal site owners who want the most current, future-proof target.
• Teams redesigning a Drupal 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 Drupal

• 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 Drupal Sites Usually Fail WCAG 2.2

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

• Custom theme markup. Twig overrides that replace core templates can drop landmarks, heading levels, skip links or ARIA attributes that core would have added.
• Views output. Views tables, grids and exposed filters are generated from configuration, so a table can lack header cells and a filter form can lack labels without any code being wrong.
• Layout Builder and Paragraphs. Flexible page assembly makes it easy to put headings out of order, repeat identical link text such as "Read more" and use images with no alt text.
• Webform fields. Complex forms with conditional fields, multi-page steps and custom error messages often hide labels visually, or change fields without telling assistive technology.
• Rich text and media content. Editors using CKEditor can bold text instead of making a heading, paste inline styles that reduce contrast, or embed media without alt text.

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

What to Test by Hand on Drupal

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 1.3.2 Meaningful Sequence Explained in Plain EnglishWCAG 1.3.2 Meaningful Sequence explained simply: why reading order matters, how CSS and layout tables break it, how to fix it and how to test your pages.
• WCAG 3.3.2 Labels or Instructions Explained in Plain EnglishWCAG 3.3.2 Labels or Instructions explained simply: visible labels, format hints, grouped fields and required markers, with code examples and a test routine.
• ADA Website Accessibility – How to Use AccessBell to Help Avoid LawsuitsADA website accessibility explained: who the ADA covers, whether websites count, the WCAG standard, and how AccessBell helps you find and fix issues behind lawsuits.
• WCAG Success Criteria LibraryLook up any criterion the scan flags, in plain language.

Drupal WCAG 2.2 Checker: Frequently Asked Questions