The short answer
Report against WCAG 2.2 unless your buyer specifically asked for 2.1. WCAG 2.2 is the current version, it includes everything in 2.1 except one obsolete criterion, and a 2.2 report answers a 2.1 request too. Many contracts and RFPs written before 2024 still name WCAG 2.1, so that version is still common in procurement.
| Level A and AA | WCAG 2.1 | WCAG 2.2 |
|---|---|---|
| Success criteria in the report | 50 | 55 |
| Level A | 30 | 31 |
| Level AA | 20 | 24 |
The six new Level A and AA criteria
WCAG 2.2 added nine success criteria in total. Three are Level AAA, which most VPATs don’t evaluate. These are the six that will appear in your report:
| Criterion | What to check |
|---|---|
| 2.4.11 Focus Not Obscured (Minimum)Level AA | Is the focused element never completely hidden by sticky headers, footers, or overlays? |
| 2.5.7 Dragging MovementsLevel AA | Can anything done by dragging also be done with a single click or tap? |
| 2.5.8 Target Size (Minimum)Level AA | Are click and tap targets at least 24 by 24 CSS pixels, or spaced so they don’t crowd each other? |
| 3.2.6 Consistent HelpLevel A | Is help, such as contact details, chat, or a help link, in the same relative place on every page? |
| 3.3.7 Redundant EntryLevel A | Is information already entered in a process filled in or selectable, rather than asked for again? |
| 3.3.8 Accessible Authentication (Minimum)Level AA | Can people sign in without a memory or transcription test, or is an alternative offered? |
Where software teams most often find gaps:
- Focus Not Obscured. Sticky headers, cookie banners and chat widgets that cover the field you just tabbed to.
- Target Size. Small icon buttons packed together in toolbars and table rows.
- Dragging Movements. Kanban boards, sliders and reorderable lists with no click or keyboard alternative.
- Accessible Authentication. Sign-in that blocks password managers or pasting, or relies on a puzzle CAPTCHA with no alternative.
The one that was removed: 4.1.1 Parsing
WCAG 2.2 removed 4.1.1 Parsing because modern browsers and assistive technologies handle markup errors consistently, so the criterion no longer protected users. The W3C also issued errata for WCAG 2.0 and 2.1 stating that 4.1.1 is always satisfied for content using HTML or XML.
In practice: leave 4.1.1 out of a WCAG 2.2 report. In a WCAG 2.1 report, it’s still listed, and you can mark it Supports with a remark that cites the errata.
How to choose for your VPAT
- The buyer named a version: use it. If they asked for 2.1 and you’re ready for 2.2, ask whether 2.2 is acceptable. It usually is.
- The buyer didn’t say: use 2.2.
- The buyer asked for Section 508: the Revised 508 standards incorporate WCAG 2.0 AA. A WCAG 2.1 or 2.2 report covers those criteria and more, but some federal buyers want the 508 edition specifically. Ask.
Switching versions doesn’t mean starting over. Every 2.1 answer except 4.1.1 carries over to 2.2; you only need to add the six new rows. Our WCAG 2.2 AA checklist lists them all.
VPAT Draft Desk supports both versions and switches the criteria list for you, with the WCAG 2.2 additions marked.
Start your VPAT