WCAG 2.2 Changes — New Requirements for Your Website

Dragging Movements (2.5.7): Any action that requires dragging must have a simple pointer alternative. Focus Not Obscured (Minimum) (2.4.11): When an element receives keyboard focus, it can't be fully hidden by sticky headers, footers, or other content.

Focus Not Obscured (Enhanced) (2.4.12): Focused elements must be at least partially visible. Focus Appearance (2.4.13): Focus indicators must be at least 2px thick with sufficient contrast. Minimum Target Size (2.5.8): Interactive targets must be at least 24×24 CSS pixels. Consistent Help (3.2.6): Help mechanisms must appear in the same location across pages. Redundant Entry (3.3.7): Don't ask users to re-enter information they've already provided. Accessible Authentication (Minimum) (3.3.8): Login can't require cognitive function tests (like CAPTCHA) without alternatives.

WCAG 2.2 removed success criterion 4.1.1 (Parsing), which required valid HTML. Modern assistive technology handles parsing errors well enough that this criterion was no longer necessary. This doesn't mean invalid HTML is fine — it just means it's not a WCAG failure.

If you're starting a new compliance effort, target WCAG 2.2 AA. The new criteria address real usability issues, especially for mobile users and people with cognitive disabilities. If you're already WCAG 2.1 AA compliant, the gap to 2.2 is manageable. ADA CodeFix scans against current standards and will alert you to issues.