Skip to main content
Home / Compliance Hub / WCAG 2.2 Checklist
Legal & Technical Alert

The WCAG 2.2
Standard.

WCAG 2.2 introduces updated guidelines to enhance web accessibility. This is the new legal baseline for ADA Title III compliance across healthcare, banking, and retail sectors.

View Checklist Request An Audit

Supported Audit Frameworks

WCAG 2.1 / 2.2 AA ADA Title III Section 508 AODA (Canada)

WCAG 2.2 Criteria Additions.

These represent the most significant additions to the AA standard. If your website was audited before October 2023, it likely fails these specific criteria. Automated tools cannot reliably detect these issues; they require manual code review.

2.4.11
Focus Not Obscured (Minimum)
When an interface component receives keyboard focus (like a user hitting the Tab key), it cannot be fully hidden by sticky headers, sticky footers, floating chat widgets, or non-modal dialogs.
2.4.12
Focus Not Obscured (Enhanced)
AAA Requirement: The targeted focused element cannot be hidden *at all* (even partially) by any author-created content.
2.5.7
Dragging Movements
Any action that requires complex dragging (e.g., custom price sliders, Kanban boards, dragging a product into a cart) must have an alternative, simple point-and-click interface mechanism.
2.5.8
Target Size (Minimum)
Interactive targets (buttons, links, form inputs) must be at least 24x24 CSS pixels in size, or have sufficient empty spacing around them to prevent accidental clicks by users with motor tremors.
3.2.6
Consistent Help
Contact details, human support numbers, or automated help mechanisms (like chatbots) must be located in the exact same relative order across multiple web pages (e.g. pinned to the bottom right globally).
3.3.8
Accessible Authentication
Cognitive function tests (like memorizing a password, solving complex math CAPTCHAs, or identifying street signs) cannot be required for login without an alternative method (like a login link sent via email or WebAuthn).
Audit_Report_Widget_Header_v4.pdf FAIL (2.4.11)

Technical Remediation Summary

Failing Element: <button class="support-chat-trigger">

Issue Discovered: The global sticky header (z-index: 50) completely obscures this interactive button when the user navigates via the 'Tab' key, violating WCAG 2.4.11 Focus Not Obscured. The user cannot see what they have focused on.
Recommended Fix: Implement CSS scroll-padding-top: var(--header-height); on the html element to offset the sticky header height natively during keyboard focus jumps.

Automated & Manual
Reporting

Automated scanning tools (like Lighthouse or WAVE) only catch about 30% of actual WCAG violations. They cannot test if a dragging movement has a logical alternative, or if error suggestions are contextually helpful to a human.

We provide comprehensive VPATs (Voluntary Product Accessibility Templates) and detailed technical remediation reports that combine automated pipeline scanning with rigorous manual screen-reader testing (NVDA, VoiceOver).

Development Pipeline Auditing
Manual Screen Reader Verification
Defense Documentation

Don't Wait For A
Demand Letter.

Protect your business from serial Title III litigation while opening your digital properties to everyone. Schedule a technical WCAG 2.2 audit of your most critical user flows today.

Request A Full Audit