WCAG 2.2

2.4.11 Focus Not Obscured (Minimum), level AA. When a user interface component receives keyboard focus, the component is not entirely hidden by author-created content.

2.4.12 Focus Not Obscured (Enhanced), level AAA. The stricter form of the same requirement: no part of the focused component may be hidden by author-created content.

2.4.13 Focus Appearance, level AAA. When the keyboard focus indicator is visible, its area must be at least as large as a 2 CSS pixel thick perimeter of the unfocused component, and the contrast ratio between the focused and unfocused states must be at least 3:1. Exceptions apply, among others, where the focus indicator is determined by the user agent and cannot be adjusted by the author.

2.5.7 Dragging Movements, level AA. Any functionality operated by a dragging movement must also be achievable with a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author.

2.5.8 Target Size (Minimum), level AA. The target for pointer inputs is at least 24 by 24 CSS pixels. Exceptions apply, among others, to smaller targets with sufficient spacing, to equivalent controls on the same page, and to essential cases.

3.2.6 Consistent Help, level A. Where help mechanisms are repeated across multiple pages in a set of pages, they occur in the same order relative to other page content. The mechanisms in question are human contact details, a human contact mechanism, a self-help option and a fully automated contact mechanism.

3.3.7 Redundant Entry, level A. Information previously entered by or provided to the user and required again in the same process is either auto-populated or available to select. Exceptions apply where re-entering is essential, where it is required for security, or where the earlier information is no longer valid.

3.3.8 Accessible Authentication (Minimum), level AA. No step of an authentication process may require a cognitive function test, such as remembering a password or solving a puzzle. Exceptions apply, among others, where another authentication method without a cognitive function test is offered, or where a mechanism is available to help the user complete the test.

3.3.9 Accessible Authentication (Enhanced), level AAA. The same requirement, but with only the two exceptions of an alternative method and an assisting mechanism.

Success criterion 4.1.1 Parsing, part of WCAG 2.0 and WCAG 2.1, is treated as obsolete in WCAG 2.2 and has been removed from the standard. It required markup to be correctly nested, to use unique IDs and to have complete start and end tags.

The standard notes expressly that authors who are required by policy to conform with WCAG 2.0 or 2.1 can update their content to WCAG 2.2, but may need to continue to test and report 4.1.1. For the German and European legal framework that is the normal case, because WCAG 2.1 remains the applicable benchmark there.

Each new success criterion has been appended to the end of the guideline it belongs to, rather than inserted where it would fit thematically. The W3C gives backwards compatibility as the reason: this way every success criterion from WCAG 2.0 and WCAG 2.1 keeps its familiar number.

That is why 2.4.10 Section Headings is followed directly by 2.4.11 Focus Not Obscured (Minimum), and why the new authentication criteria sit at 3.3.8 and 3.3.9 even though they have little in common with 3.3.1 to 3.3.6.

Not at present. Neither the BFSG nor the BITV 2.0 names the WCAG directly. Both attach to harmonised standards whose references have been published in the Official Journal of the European Union.

According to the European Commission, two versions of EN 301 549 have been harmonised so far: V2.1.2 in December 2018, since replaced and no longer carrying a presumption of conformity, and V3.2.1 on 18 August 2021. The currently harmonised version V3.2.1 is based on WCAG 2.1.

A revised version, EN 301 549 V4.1.0, exists at ETSI as a final draft dated June 2026. Whether and when such a version carries a presumption of conformity is decided only when its reference is published in the Official Journal of the European Union. Until then, WCAG 2.1 at level AA remains the legally applicable benchmark.

The technical question is separate. WCAG 2.2 is backwards compatible: meeting WCAG 2.2 at level AA also means meeting WCAG 2.1 at level AA, apart from the removed criterion 4.1.1. Teams building something new can work to WCAG 2.2 without missing the legal benchmark.

For how the WCAG are applied in practice, see the topic page on the WCAG. Related fact pages: the fact page on the WCAG covering structure and conformance levels, the fact page on the BITV 2.0 and the fact page on the BFSG. All fact pages are listed on the facts overview.

WCAG 2.2 does not supersede WCAG 2.1 or WCAG 2.0. All three are valid W3C Recommendations at the same time. A higher version number does not invalidate the earlier ones.

WCAG 2.2 is not WCAG 3. WCAG 3 is a separate draft still in development, with a different structure, and is not the subject of this page.

The nine new success criteria are not all at level AA. Two are at level A, four at level AA and three at level AAA. An audit against level AA therefore covers six of the nine new criteria.

The removal of 4.1.1 Parsing does not mean broken markup no longer matters. Other success criteria, notably 4.1.2 Name, Role, Value, still impose requirements on the technical implementation.