Framer WCAG 2.2 Checker

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

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

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

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

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

• Text that looks like a heading. Large styled text layers become headings only when you choose a heading tag, so pages can end up with no h1 or with levels in the wrong order.
• Icon-only buttons and links. Social icons, menu toggles and arrow buttons made from a vector frame have no name until you add an ARIA label.
• Tickers, marquees and autoplay. Scrolling logo tickers, looping carousels and background video move constantly, with no way for a visitor to pause them.
• Hover-only interactions. Menus and cards that reveal content only on hover are out of reach for keyboard and touch users unless the same state is available on focus and tap.
• Contrast and focus over imagery. Text over photos and gradients can fail contrast, and custom components often hide or replace the default focus indicator.

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

What to Test by Hand on Framer

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 2.2.2 Pause, Stop, Hide Explained in Plain EnglishWCAG 2.2.2 Pause, Stop, Hide explained simply: what moving and auto-updating content needs, the 5-second rule, carousel fixes and how to test your pages.
• WCAG 2.4.12 Focus Not Obscured (Enhanced) Explained in Plain EnglishWCAG 2.4.12 Focus Not Obscured (Enhanced) explained simply: how it differs from 2.4.11, who it helps, CSS scroll-padding fixes and how to test for it.
• 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 Success Criteria LibraryLook up any criterion the scan flags, in plain language.

Framer WCAG 2.2 Checker: Frequently Asked Questions