WCAG 2.2 became a W3C Recommendation in October 2023 and is now the version most accessibility policies point to, including newer laws and procurement rules. It added nine new success criteria and removed one. Most of the new criteria are about websites and apps, but several apply to interactive PDFs, especially forms.
What WCAG 2.2 changed
New criteria at levels A and AA:
- 2.4.11 Focus Not Obscured (Minimum) (AA)
- 2.5.7 Dragging Movements (AA)
- 2.5.8 Target Size (Minimum) (AA)
- 3.2.6 Consistent Help (A)
- 3.3.7 Redundant Entry (A)
- 3.3.8 Accessible Authentication (Minimum) (AA)
Plus three at AAA level. One criterion was removed: 4.1.1 Parsing, which had become obsolete.
Which apply to PDFs
Focus Not Obscured. When a user tabs through a PDF form, the focused field should not be hidden behind other content. In PDFs, this rarely fails unless sticky headers or overlapping annotations are involved, but check forms with comments or floating notes.
Target Size (Minimum). Interactive targets should be at least 24 by 24 CSS pixels, or have enough spacing. In PDF forms, tiny checkboxes and radio buttons crammed together are the classic failure. Make them larger or space them out. See how to add checkboxes to a PDF form.
Redundant Entry. Information a user has already entered in the same process should be filled in automatically or available to select. In a multi-page PDF form, asking for the same name and address on page one and page four fails this. Use fields with the same name so values carry over, or a "same as above" checkbox.
Consistent Help. If a set of documents offers help (a phone number, a contact link), it should appear in the same place in each. For document series, put contact information in a consistent position.
Accessible Authentication. Mainly about logins, but relevant if a PDF portal asks users to transcribe codes from a document. Avoid processes that rely on memorising or retyping.
Dragging Movements rarely applies to PDFs.
What did not change
Everything from WCAG 2.0 and 2.1 still applies: alt text, headings, reading order, contrast, form labels and keyboard access. Those are still where most PDFs fail. See WCAG 2 for PDF accessibility.
Updating your form templates
- Increase checkbox and radio button size to at least 24 by 24 pixels at 100% zoom.
- Reuse field names for repeated data so it fills automatically.
- Put help and contact details in the same spot on every page or form.
- Test the tab order with a keyboard only. See accessible PDF forms checklist.
What about WCAG 3?
WCAG 3 is a long-term draft with a different scoring model. It is not expected to replace WCAG 2.x in law for years. Target 2.2 today.
Takeaway
WCAG 2.2's changes for PDFs are mostly about forms: bigger targets, no retyping, and consistent help. They are small template changes that make forms easier for everyone. For the regulatory side, see the European Accessibility Act checklist.
