8 min read

WCAG 2.1 AA for PDFs: What Actually Applies

WCAG 2.1 was written for the web, so not every success criterion applies to a static PDF — there is no audio, no time limits, no client-side scripting in most documents. This guide focuses on the Level A and AA criteria that genuinely apply to PDFs and what each one means in practice.

Perceivable

  • 1.1.1 Non-text Content (A): every meaningful image needs alt text; decorative images are artifacted.
  • 1.3.1 Info and Relationships (A): structure conveyed visually (headings, lists, tables) must be tagged so it is programmatically determinable.
  • 1.3.2 Meaningful Sequence (A): the reading order must be correct.
  • 1.4.3 Contrast (Minimum) (AA): text needs at least 4.5:1 contrast (3:1 for large text).
  • 1.4.5 Images of Text (AA): use real text rather than pictures of text wherever possible.

Operable

  • 2.1.1 Keyboard (A): interactive elements (form fields, links) must be usable by keyboard, in a logical tab order.
  • 2.4.2 Page Titled (A): the document needs a meaningful title set to display.
  • 2.4.4 Link Purpose (A): link text must describe where the link goes.
  • 2.4.6 Headings and Labels (AA): headings and form labels must be descriptive.

Understandable

  • 3.1.1 Language of Page (A): the primary language must be declared.
  • 3.1.2 Language of Parts (AA): passages in another language must declare their language.
  • 3.3.2 Labels or Instructions (A): form fields need clear labels and instructions.

Robust

  • 4.1.2 Name, Role, Value (A): interactive controls must expose their name, role, and value to assistive technology — in a PDF this comes from correct form-field tagging and tooltips.

Which ones are easy to automate

Criteria like missing alt text (1.1.1), missing title (2.4.2), missing language (3.1.1), and untagged structure (1.3.1) are reliably caught by automated checkers. Others — whether alt text is meaningful, whether reading order makes sense, whether contrast on a complex graphic is sufficient — need human judgment. The efficient approach is to clear the automatable failures first, then do a focused manual review of what is left.

Section 508 in the US and the European Accessibility Act both reference WCAG 2.x Level AA, so meeting these criteria is what most legal compliance regimes actually require.

Run a free check on this site to see which of these criteria your PDF currently passes.

Check your PDF for free

See exactly which PDF/UA and WCAG 2.1 AA issues your document has — instant, no signup.

Check My PDF

Frequently asked questions

Does all of WCAG 2.1 apply to PDFs?
No. WCAG was written for the web, so criteria about audio, video, time limits, and client-side scripting rarely apply to a static PDF. The relevant subset covers alt text, tagged structure, reading order, contrast, keyboard-operable forms, titles, links, and language.
What WCAG level do PDFs need to meet?
Level AA is the practical target. Most legal regimes — Section 508 in the US and the European Accessibility Act — reference WCAG 2.x Level AA, which includes all Level A criteria plus the AA additions such as 4.5:1 text contrast.
Which WCAG criteria can a checker test automatically?
Missing alt text (1.1.1), missing document title (2.4.2), missing language (3.1.1), and untagged structure (1.3.1) are reliably caught by automated checkers. Whether alt text is meaningful, reading order makes sense, or contrast on a complex graphic is sufficient still needs human judgment.

Related how-to fixes