WCAG 2.1 vs 2.2: key changes and which version to audit
WCAG (Web Content Accessibility Guidelines) are international recommendations for web accessibility. European and contractual requirements apply them through the relevant standards and rules; the required version must be verified for the specific framework. Version 2.2 builds on 2.1 and adds criteria for modern interfaces.
Why choosing can be difficult
A business hears two version numbers and does not know which to follow. One adviser says “2.1 is enough”, another says “2.2 already applies”, creating concern that work will be unnecessary or need to be done twice.
Most criteria from version 2.1 remain in version 2.2, with nine new criteria added. One important exception prevents the simple claim that 2.2 is a pure superset: success criterion 4.1.1 Parsing was removed from WCAG 2.2. If a legal or contractual framework requires WCAG 2.1, the method used to assess and report it must be confirmed under that framework. W3C now marks this criterion as obsolete and always satisfied for content using HTML or XML.
What changed between the versions
WCAG 2.2 adds nine new success criteria. Those you will encounter in an online shop include:
- Target Size (Minimum) (2.5.8). Controls must be at least 24 × 24 CSS pixels or meet one of the exceptions, such as the requirement for sufficient spacing. A small close icon must therefore also be assessed in relation to the targets around it.
- Accessible Authentication (Minimum) (3.3.8). Authentication must not require a cognitive function test unless a suitable alternative or assistance mechanism is available. For CAPTCHAs or retyping passwords, the particular mechanism and the exceptions must be assessed.
- Dragging Movements (2.5.7). Functionality that uses a dragging movement must have a single-pointer alternative unless dragging is essential to that functionality.
- Redundant Entry (3.3.7). Information that a user has already entered during the same process must be auto-populated or made available for selection unless an exception applies.
- Focus Not Obscured (Minimum) (2.4.11). An element receiving keyboard focus must not be entirely hidden by author-created content such as a fixed bar.
Version 2.2 also removes one criterion—4.1.1 Parsing. W3C now marks it as obsolete and always satisfied for content created in HTML or XML. If a particular framework requires WCAG 2.1, its rules must be used to confirm how this criterion should be addressed in the assessment and report.
How to choose a version for an audit
WCAG 2.2 is the more current W3C Recommendation, and W3C recommends using the latest version. It includes the requirements from version 2.1 except for the removed criterion 4.1.1, and adds new criteria relevant to modern interfaces.
We therefore recommend WCAG 2.2 for professional improvement. If an audit is intended to demonstrate a legal or contractual requirement, however, the report will also state the version required by that framework. Automated checks can be integrated into CI/CD, but they cover only the machine-testable portion.
What a clearly selected version gives you
- Clarity about which requirements to follow, without switching back and forth between two versions.
- A lower risk that an interface you have already corrected will need further rework when the required framework changes in the future.
- Coverage of issues that genuinely obstruct mobile users, rather than merely ticking a formal WCAG 2.1 box.
Next step
Would you like to know how your website performs against WCAG 2.2? Contact us—an initial scan will reveal the first machine-detectable findings, and a subsequent assessment will determine which new criteria are relevant to the interface reviewed. You can also find more context in what the EAA is and who it applies to.