What are the six new WCAG 2.2 criteria?

WCAG 2.2 adds Focus Appearance and Focus Not Obscured (2.4.11 and 2.4.12), Dragging Movements (2.5.7), Target Size Minimum (2.5.8), Consistent Help (3.2.6), Redundant Entry (3.3.7), and Accessible Authentication (3.3.8). One 2.1 criterion, 4.1.1 Parsing, was also removed.

Why are some results marked Manual check?

Several 2.2 criteria are visual or behavioural — whether a focused element is actually obscured, or whether a target's computed CSS size is large enough — and cannot be judged from static HTML alone. The tool marks these honestly so you know to verify them in a running page.

How does it check Target Size?

It reads inline width and height styles on interactive elements and flags any below 24 by 24 CSS pixels, the 2.5.8 minimum. Because most sizing comes from external CSS the tool cannot see, a clean result still warrants a manual computed-size check.

What does it look for in Accessible Authentication?

It flags password fields that block paste via onpaste, since blocking paste defeats password managers and effectively imposes a cognitive-function test. The full criterion also forbids puzzles and memorisation tests, which require manual review.

Does my markup leave the browser?

No. Parsing and all heuristics run locally with the browser's DOMParser, so your HTML is never uploaded and the report is generated instantly.

WCAG 2.2 New Criteria Checker

The WCAG 2.2 New Criteria Checker is built for teams moving from WCAG 2.1 to 2.2. Rather than re-running a full audit, it focuses only on the six success criteria that 2.2 added, so you can see at a glance which new requirements your markup already meets and which need attention.

How it works

Parse the HTML. The snippet is parsed locally and the tool collects interactive controls, fixed and sticky elements, draggable elements, form fields, and authentication inputs.
Run one heuristic per criterion. Each of the six criteria gets a targeted static check — for example, fixed or sticky elements are flagged for Focus Not Obscured, inline target sizes under 24px fail Target Size, and password fields that block paste fail Accessible Authentication.
Report honestly. Results are Pass, Review, Fail, or Manual check. Criteria that genuinely cannot be decided from static HTML, such as whether a focused control is visually covered, are marked Manual check rather than guessed.

What it can and cannot see

It can see inline styles, attributes like draggable and onpaste, repeated field names, and the presence of help links.
It cannot see external CSS, computed layout, focus visuals, or runtime behaviour. Treat clean results on the visual criteria (2.4.11/2.4.12, 2.5.8) as “no problem found inline”, not a guarantee.

Tips and notes

Give every interactive target at least 24 by 24 CSS pixels, or enough spacing to qualify for the 2.5.8 exception.
Never block paste on password fields — it breaks password managers and trips 3.3.8.
Keep your help and contact links in the same relative location on every page to satisfy 3.2.6 Consistent Help.