Webflow WCAG 2.2 Checker

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

On Webflow, 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 Webflow WCAG 2.2 Checker

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

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

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

• Styled divs instead of real headings. Text boxes styled with heading-sized fonts, instead of an actual Heading element, look identical visually but are invisible to screen reader navigation.
• Empty alt text fields. Webflow prompts for alt text on every image, but it is optional, and images imported or duplicated quickly often keep it blank.
• Custom interactions and animations. Webflow’s interactions panel makes it easy to build scroll and click animations that move focus unpredictably or hide content from keyboard users.
• Embedded custom code. Custom code embeds and third-party widgets (booking tools, chat, video players) bring their own accessibility issues that Webflow’s Designer has no control over.
• Color contrast in the style guide. Brand color palettes chosen for visual design are not automatically checked against WCAG contrast ratios anywhere in the Designer.

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

What to Test by Hand on Webflow

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.
• What Is a Website Accessibility Checker? How Automated Testing WorksA plain-English guide to website accessibility checkers: what they test, how they map results to WCAG, what they miss, and how to choose one.
• Automated vs Manual Accessibility Testing: Where Each FitsWhat automated accessibility testing catches, what needs a human, and how to combine both into a repeatable process for finding and fixing WCAG issues.
• WCAG 2.2 Checklist: What Changed and How to Test Each CriterionA practical WCAG 2.2 AA checklist: the nine new success criteria, the one that was removed, and how to test your website against each requirement.
• WCAG Success Criteria LibraryLook up any criterion the scan flags, in plain language.

Webflow WCAG 2.2 Checker: Frequently Asked Questions