The Web Content Accessibility Guidelines (WCAG) are the global standard for making web content accessible to people with disabilities. Published by the World Wide Web Consortium (W3C), WCAG provides a shared framework that governments, organizations, and developers use to build inclusive digital experiences. WCAG 2.2, released in October 2023, is the latest stable version and introduces nine new success criteria that address gaps in mobile accessibility, cognitive disability support, and user interface interaction.
Why WCAG 2.2 Matters in 2025
The regulatory landscape has shifted dramatically. The European Accessibility Act (EAA) became enforceable in June 2025, requiring all digital products and services sold in the EU to meet WCAG 2.2 Level AA. In France, the RGAA (Referentiel General d'Amelioration de l'Accessibilite) directly references WCAG. Germany's BITV 2.0, the UK's Equality Act, and the US ADA all either mandate or strongly reference WCAG conformance. Non-compliance now carries real financial penalties, including fines up to 2% of annual turnover in some EU member states.
The Four WCAG Principles (POUR)
Every WCAG success criterion falls under one of four principles, collectively known as POUR:
- Perceivable — Information and user interface components must be presentable to users in ways they can perceive. This includes providing text alternatives for images, captions for video, and sufficient color contrast for text.
- Operable — Users must be able to operate all interface components and navigation. This means full keyboard accessibility, enough time to read content, and no content that could cause seizures.
- Understandable — Information and interface operation must be understandable. Text should be readable, pages should behave predictably, and input assistance should help users avoid and correct errors.
- Robust — Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies like screen readers and voice control software.
Conformance Levels: A, AA, and AAA
WCAG defines three levels of conformance. Level A covers the most basic accessibility requirements — things like providing alt text for images and making all functionality available from a keyboard. Level AA, the standard required by most legislation, adds requirements like minimum contrast ratios (4.5:1 for normal text), resizable text up to 200%, and visible focus indicators. Level AAA is the highest standard and includes requirements like enhanced contrast (7:1), sign language for all prerecorded audio, and extended audio descriptions.
For most organizations, Level AA is the target. It strikes a balance between meaningful accessibility and practical implementation. All EU regulations, including the EAA and RGAA, require Level AA conformance.
What's New in WCAG 2.2
WCAG 2.2 introduces nine new success criteria that were not present in WCAG 2.1. These address common pain points that real users with disabilities face on the modern web:
2.4.11 Focus Not Obscured (Minimum) — Level AA
When a user interface component receives keyboard focus, it must not be entirely hidden by author-created content such as sticky headers, cookie banners, or chat widgets. At least part of the focused element must be visible to the user.
2.4.12 Focus Not Obscured (Enhanced) — Level AAA
The enhanced version requires that the focused component is not obscured at all by other content. The entire focused element must be visible.
2.4.13 Focus Appearance — Level AAA
Focus indicators must meet a minimum size (at least a 2px solid outline or equivalent area) and have a 3:1 contrast ratio between the focused and unfocused states.
2.5.7 Dragging Movements — Level AA
Any functionality that uses dragging must also be operable with a single pointer without dragging. For example, a drag-and-drop sortable list must also offer up/down buttons or another click-based alternative.
2.5.8 Target Size (Minimum) — Level AA
Interactive targets must be at least 24x24 CSS pixels, or have sufficient spacing from other targets. This is critical for users with motor impairments who cannot precisely click small targets. Inline links within text are exempt.
3.2.6 Consistent Help — Level A
If a website provides help mechanisms (contact information, chat, FAQ link), they must appear in the same relative order across pages. Users who need help should be able to find it reliably.
3.3.7 Redundant Entry — Level A
Information previously entered by the user during a session must be auto-populated or available for selection. Users should not be asked to re-enter the same data in a multi-step process.
3.3.8 Accessible Authentication (Minimum) — Level AA
Authentication must not rely on cognitive function tests like puzzles, memorization of passwords, or transcription. Alternatives such as copy-paste support, password managers, or biometric authentication must be available.
3.3.9 Accessible Authentication (Enhanced) — Level AAA
The enhanced version further restricts authentication to not require any object or image recognition at all.
WCAG 2.2 and Removed Criteria
One notable change: WCAG 2.2 removed success criterion 4.1.1 (Parsing). Modern HTML parsers and browsers are now robust enough that parsing errors rarely cause accessibility issues. The W3C decided this criterion no longer served its original purpose.
How to Achieve WCAG 2.2 AA Compliance
Achieving compliance involves a combination of automated scanning, manual testing, and ongoing remediation. Automated tools can catch approximately 30-40% of WCAG violations — things like missing alt text, insufficient contrast, and missing form labels. The remaining violations require manual review with assistive technologies. An accessibility widget like Accessify can handle many runtime fixes automatically, including AI-generated alt text, contrast adjustments, and keyboard navigation enhancements, providing an immediate accessibility layer while you work on deeper structural fixes.
Next Steps
Understanding WCAG 2.2 is the first step. From here, we recommend running a WCAG audit on your website, prioritizing Level AA violations, and implementing a combination of automated remediation and manual fixes. The cost of inaction is rising — both legally and in terms of the users you exclude.