Meeting WCAG 2.2 in PDF documents
Through clause 10 of EN 301 549, WCAG applies to PDFs too. Only part of the success criteria matter for reports, contracts, invoices and forms, and most of those are met through tags and metadata. The open question at the moment is whether WCAG 2.1 or 2.2 is the legal reference.
Last updated:
Four principles, three levels
The W3C’s WCAG are written to be technology-neutral. They do not prescribe a file format; they describe what users should experience. They are grouped under four principles, known by the acronym POUR. Content has to be perceivable, available to at least one sense, for example through alternative text or sufficient contrast. It has to be operable: links, form fields and navigation work with a keyboard and with assistive technologies. Understandable covers language, labels and error messages. Robust means readers and screen readers can interpret the markup reliably.
Each success criterion belongs to a conformance level: A (essential), AA (standard) or AAA (enhanced). Legal requirements in the EU generally call for level AA via EN 301 549, meaning every level A and AA criterion. AAA is not required across the board.
How WCAG is applied to PDFs
WCAG was written for web content. The European standard EN 301 549 carries the success criteria over to downloadable files such as PDFs in clause 10 (“non-web documents”), with some wording adapted. The W3C Group Note WCAG2ICT also explains how to read the criteria outside the web.
For implementation, the W3C has published dedicated PDF techniques, numbered PDF1 to PDF23. They are classed as “sufficient techniques”: applying one correctly meets the criterion on that point. Other solutions are equally acceptable. Some criteria, contrast among them, have no PDF-specific technique at all because the general techniques apply.
The success criteria that count for PDFs
The table is limited to level A and AA criteria that come up in typical PDFs such as reports, contracts, invoices and forms. Criteria on video, audio or time limits rarely affect static PDFs.
| Criterion (level) | Implementation in the PDF | W3C technique |
|---|---|---|
| 1.1.1 Non-text Content (A) | Alternative text in the Alt entry of Figure; decorative graphics marked as artifacts | PDF1, PDF4 |
| 1.3.1 Info and Relationships (A) | Headings, lists, tables with header cells and form fields tagged correctly | PDF6, PDF9, PDF10, PDF21 and others |
| 1.3.2 Meaningful Sequence (A) | Order in the structure tree matches the logical reading order, including columns and boxes | PDF3 |
| 1.4.1 Use of Color (A) | Information in charts or tables conveyed by text, patterns or labels as well as colour | no PDF-specific technique |
| 1.4.3 Contrast (Minimum) (AA) | At least 4.5:1 for normal text and 3:1 for large text; best fixed in the template | no PDF-specific technique |
| 1.4.5 Images of Text (AA) | Real text instead of text images; scanned pages given a text layer via OCR | PDF7 |
| 2.1.1 Keyboard (A) | Links and form fields reachable and operable by keyboard | PDF3, PDF11, PDF23 |
| 2.4.2 Page Titled (A) | Meaningful document title in the metadata, displayed via DisplayDocTitle | PDF18 |
| 2.4.3 Focus Order (A) | Tab order follows the structure (/Tabs /S) | PDF3 |
| 2.4.4 Link Purpose (In Context) (A) | Links tagged as Link elements; link text or context describes the target | PDF11, PDF13 |
| 3.1.1 Language of Page (A) | Default language in the document catalog (/Lang) | PDF16 |
| 3.1.2 Language of Parts (AA) | Different language for quotes or passages via Lang on the structure element | PDF19 |
| 3.3.1 Error Identification (A) | Required fields and input errors in PDF forms made identifiable | PDF5, PDF22 |
| 3.3.2 Labels or Instructions (A) | Form fields labelled in the tooltip entry (TU) | PDF5, PDF10 |
| 4.1.2 Name, Role, Value (A) | Form fields expose name, role and state to assistive technologies | PDF10, PDF12 |
Two more AA criteria regularly matter for PDFs: 1.4.11 Non-text Contrast (3:1 for chart lines, icons and form field borders) and 2.4.6 Headings and Labels (headings describe their content). With 1.4.4 Resize Text and 1.4.10 Reflow, much depends on the PDF reader. It can only enlarge and reflow content, though, if the tag structure is clean. The full list of checks is in our accessible PDF checklist.
What changes for PDFs with WCAG 2.2
WCAG 2.2 became a W3C Recommendation in October 2023 and was updated in December 2024. It adds nine criteria to WCAG 2.1, six of them at levels A and AA, and drops 4.1.1 Parsing. Static PDFs are affected far less than websites.
- 2.4.11 Focus Not Obscured (Minimum) (AA) and 2.5.7 Dragging Movements (AA) are aimed at interactive interfaces. In PDFs the reader largely determines the behaviour.
- 2.5.8 Target Size (Minimum) (AA) requires at least 24 × 24 CSS pixels or sufficient spacing. Links in running text are exempt, but buttons and fields in PDF forms are not.
- 3.2.6 Consistent Help (A) applies, for documents, to sets of related documents rather than a single PDF.
- 3.3.7 Redundant Entry (A) and 3.3.8 Accessible Authentication (Minimum) (AA) concern multi-step forms and sign-in processes. Ordinary PDFs rarely contain either.
If your static PDFs already meet WCAG 2.1 AA, little usually needs to change for 2.2. Interactive PDF forms are worth a closer look.
Which version applies legally
The Web Accessibility Directive (EU) 2016/2102 and the European Accessibility Act do not name a WCAG version. They rely on harmonised standards, in practice EN 301 549. The version cited in the Official Journal of the EU for the Web Accessibility Directive is EN 301 549 V3.2.1 from 2021, which is based on WCAG 2.1 level AA. No harmonised standard has yet been cited for the European Accessibility Act. V3.2.1 is nevertheless the usual benchmark there too.
In September 2026, ETSI published EN 301 549 V4.1.1, which aligns the clauses for web, documents and software with WCAG 2.2. It only takes effect as a harmonised standard once the European Commission cites it in the Official Journal, and at the time of writing (October 2026) that had not happened.
We still recommend aligning new documents with WCAG 2.2 now. Content that meets WCAG 2.2 generally meets WCAG 2.1 as well. The one exception is criterion 4.1.1, removed in 2.2, and it carries little weight for PDFs anyway.
WCAG 2.2 also has standing as an international standard: since 2025 it has been published as ISO/IEC 40500:2025. The previous edition, ISO/IEC 40500:2012, corresponded to WCAG 2.0.
What checkers can and cannot do
Whether a title, language, tags and alternative text entries are present can be checked technically, for instance with the EasyPDFUA PDF/UA check in the browser, or with PAC and veraPDF. Many WCAG criteria are about content, however. No tool can fully judge whether alternative text describes the image well, whether link text is clear or whether contrast is sufficient.
Where WCAG and the technical standard PDF/UA diverge is covered in PDF/UA vs. WCAG. For the basics of the PDF standard itself, see What is PDF/UA?.
Frequently asked questions
Does WCAG apply to PDFs at all?
Yes, through the European standard EN 301 549. Its clause 10 carries the success criteria over to non-web documents such as PDFs. The W3C has also published dedicated PDF techniques, PDF1 to PDF23.
Do my PDFs need to meet WCAG 2.1 or 2.2?
The current reference is EN 301 549 V3.2.1, cited in the Official Journal of the EU, which points to WCAG 2.1 level AA. V4.1.1, published in September 2026, is based on WCAG 2.2 but only becomes the reference once it is cited. New PDFs made to WCAG 2.2 AA cover both cases.
Which conformance level do I need?
Level AA, meaning every level A and AA criterion. AAA is not required across the board, though individual AAA criteria can still be worthwhile.
Are the W3C techniques PDF1 to PDF23 mandatory?
No. They are sufficient techniques: applying one correctly meets the criterion. Other solutions are acceptable as long as the success criterion is met.
Can EasyPDFUA confirm that a PDF meets WCAG?
No. EasyPDFUA checks technical foundations such as tags, title, language, fonts and links. Contrast, link text and the quality of alternative text have to be reviewed manually.