What does "WCAG AA" mean for a PDF?

WCAG (the W3C Web Content Accessibility Guidelines) defines accessibility success criteria at three conformance levels — A, AA, and AAA — and AA is the level most laws and policies require. Although WCAG was written for web content, its criteria apply to PDFs too, and meeting them means a PDF works for people using screen readers, low vision, and other assistive technology. In practice, a WCAG AA PDF is a properly tagged document with text alternatives, logical reading order, sufficient colour contrast, labeled form fields, and a declared language. PDF/UA (the PDF-specific accessibility standard) closely supports meeting these criteria, so the two are usually pursued together.

How does PDF/UA relate to WCAG?

They are complementary. WCAG is the broad, often legally-referenced accessibility standard; PDF/UA (ISO 14289) is the technical standard for how an accessible PDF must be built (tags, structure, alt text, and so on). Producing a PDF/UA-conformant document satisfies most of what WCAG AA requires for the PDF, because PDF/UA encodes the same accessibility principles in PDF-specific terms. So a common, practical target is "PDF/UA-conformant and WCAG 2.1 AA." You build the document to PDF/UA technical requirements and verify it also meets the WCAG criteria (especially contrast and meaningful alt text, which are judgment calls a validator cannot fully assess).

What is the contrast requirement, exactly?

WCAG AA requires a contrast ratio of at least 4.5:1 between normal text and its background, and at least 3:1 for large text (roughly 18pt, or 14pt bold). This is a measurable ratio, not a vibe — light-grey text on white, or coloured text on a busy background, often fails it. Check your document's text colours against their backgrounds with a contrast checker and adjust any that fall short. Contrast is one of the most commonly failed AA criteria and one of the easiest to fix, since it is just a colour adjustment. It matters enormously for low-vision readers, who are a large group.

What is the core checklist to get to AA?

Tag the document with proper structure (headings, paragraphs, lists, tables) in correct reading order; add meaningful alt text to informative images and mark decorative ones as artifacts; ensure text contrast meets 4.5:1 (3:1 for large text); do not use colour as the only way to convey information; label form fields with accessible names and correct roles; set the document language and title; and use descriptive headings. Then verify with automated checks plus a human review and ideally a screen-reader test. That set covers the AA criteria most relevant to a typical document; complex content (charts, multimedia) needs case-by-case treatment.

Can automated tools confirm WCAG AA?

Partially — and this is important to understand. Automated checkers reliably catch the machine-detectable failures: missing tags, missing alt text, missing document language, unlabeled form fields, and they can measure contrast. But they cannot judge whether reading order is logical, whether alt text is meaningful (vs. present-but-useless), or whether headings make sense — those need human review. So full WCAG AA conformance requires automated checks plus a manual review and, ideally, testing with an actual screen reader. "Passed the automated scan" is necessary but not sufficient; the human judgment on the parts machines cannot assess is what actually makes a document usable.

Do I legally have to meet WCAG AA?

Often, depending on who you are and where. Many jurisdictions and sectors — government, education, large organisations, and others — reference WCAG (commonly 2.1 AA) in accessibility laws and policies, and document accessibility is increasingly expected or required. Whether a specific WCAG version and level is legally mandatory for your situation depends on your jurisdiction and the applicable law, so confirm your specific obligations. Regardless of legal requirement, AA is a sensible target because it makes documents usable by far more people. This article covers how to meet the criteria technically; the legal applicability is a separate question for your context.

Is it safe to run accessibility checks online?

For confidential documents, prefer tools that process files locally. ScoutMyTool runs checks like image alt-text auditing, font-embedding verification, and form-label association in your browser tab, so the document never leaves your machine. For anything sensitive, confirm the tool does not upload before using it.

6 min read

How to make a PDF WCAG AA accessible

By ScoutMyTool Editorial Team · Last updated: 2026-05-22

“Make it WCAG AA” lands on a lot of desks without much explanation of what AA actually requires for a PDF. WCAG is the web accessibility standard, AA is the level most laws reference, and its criteria apply to PDFs as much as web pages: proper tags, text alternatives, sufficient colour contrast, logical reading order, labeled forms, a declared language. The good news is the work is concrete and checkable. This guide maps the WCAG AA criteria that matter to PDFs, explains how PDF/UA supports meeting them, gives the contrast number you need (4.5:1), and covers how to verify conformance — automated checks plus the human review that machines cannot replace.

WCAG AA criteria that matter for PDFs

Criterion	What it means for a PDF
Text alternatives	Alt text on meaningful images; decorative marked artifact
Info & relationships	Tagged structure: headings, lists, tables, reading order
Contrast (Minimum) AA	Text contrast ratio ≥ 4.5:1 (≥ 3:1 large text)
Use of color	Don’t convey meaning by color alone
Name, role, value	Form fields labeled, with correct roles
Language of page	Document language set
Headings & labels	Descriptive headings; logical structure

Step by step — to WCAG AA

Start from real text. OCR scans first — an image-only PDF cannot meet AA because there is nothing to tag or read.
Tag the structure in reading order. Headings, lists, tables, paragraphs, correctly ordered — the foundation, covered in depth in screen-reader accessibility.
Add alt text; fix colour use. Describe meaningful images (audit with Image Alt-Text Audit), mark decoration as artifact, and never convey meaning by colour alone.
Meet the contrast ratio. Ensure text is at least 4.5:1 against its background (3:1 for large text); adjust any low-contrast colours.
Label forms and set language. Accessible names and correct roles for fields (with Form Label Association), and set the document language and title; embed fonts (see PDF compatibility).
Validate. Run automated checks and validate PDF/UA / PDF-A (see validating compliance).
Do the human review. Read the tag/reading order and alt text yourself, and ideally test with a real screen reader — machines cannot judge these.

Screen-reader accessibility: the tagging deep guide.
PDF accessibility: the practical overview.
Validate PDF/A compliance: checking conformance.
PDF compatibility: real text, fonts, structure.
Add fillable form fields: accessible forms.
Image Alt-Text Audit: find images missing alt text.
All ScoutMyTool PDF tools: the full toolkit.

FAQ

What does "WCAG AA" mean for a PDF?: WCAG (the W3C Web Content Accessibility Guidelines) defines accessibility success criteria at three conformance levels — A, AA, and AAA — and AA is the level most laws and policies require. Although WCAG was written for web content, its criteria apply to PDFs too, and meeting them means a PDF works for people using screen readers, low vision, and other assistive technology. In practice, a WCAG AA PDF is a properly tagged document with text alternatives, logical reading order, sufficient colour contrast, labeled form fields, and a declared language. PDF/UA (the PDF-specific accessibility standard) closely supports meeting these criteria, so the two are usually pursued together.
How does PDF/UA relate to WCAG?: They are complementary. WCAG is the broad, often legally-referenced accessibility standard; PDF/UA (ISO 14289) is the technical standard for how an accessible PDF must be built (tags, structure, alt text, and so on). Producing a PDF/UA-conformant document satisfies most of what WCAG AA requires for the PDF, because PDF/UA encodes the same accessibility principles in PDF-specific terms. So a common, practical target is "PDF/UA-conformant and WCAG 2.1 AA." You build the document to PDF/UA technical requirements and verify it also meets the WCAG criteria (especially contrast and meaningful alt text, which are judgment calls a validator cannot fully assess).
What is the contrast requirement, exactly?: WCAG AA requires a contrast ratio of at least 4.5:1 between normal text and its background, and at least 3:1 for large text (roughly 18pt, or 14pt bold). This is a measurable ratio, not a vibe — light-grey text on white, or coloured text on a busy background, often fails it. Check your document's text colours against their backgrounds with a contrast checker and adjust any that fall short. Contrast is one of the most commonly failed AA criteria and one of the easiest to fix, since it is just a colour adjustment. It matters enormously for low-vision readers, who are a large group.
What is the core checklist to get to AA?: Tag the document with proper structure (headings, paragraphs, lists, tables) in correct reading order; add meaningful alt text to informative images and mark decorative ones as artifacts; ensure text contrast meets 4.5:1 (3:1 for large text); do not use colour as the only way to convey information; label form fields with accessible names and correct roles; set the document language and title; and use descriptive headings. Then verify with automated checks plus a human review and ideally a screen-reader test. That set covers the AA criteria most relevant to a typical document; complex content (charts, multimedia) needs case-by-case treatment.
Can automated tools confirm WCAG AA?: Partially — and this is important to understand. Automated checkers reliably catch the machine-detectable failures: missing tags, missing alt text, missing document language, unlabeled form fields, and they can measure contrast. But they cannot judge whether reading order is logical, whether alt text is meaningful (vs. present-but-useless), or whether headings make sense — those need human review. So full WCAG AA conformance requires automated checks plus a manual review and, ideally, testing with an actual screen reader. "Passed the automated scan" is necessary but not sufficient; the human judgment on the parts machines cannot assess is what actually makes a document usable.
Do I legally have to meet WCAG AA?: Often, depending on who you are and where. Many jurisdictions and sectors — government, education, large organisations, and others — reference WCAG (commonly 2.1 AA) in accessibility laws and policies, and document accessibility is increasingly expected or required. Whether a specific WCAG version and level is legally mandatory for your situation depends on your jurisdiction and the applicable law, so confirm your specific obligations. Regardless of legal requirement, AA is a sensible target because it makes documents usable by far more people. This article covers how to meet the criteria technically; the legal applicability is a separate question for your context.
Is it safe to run accessibility checks online?: For confidential documents, prefer tools that process files locally. ScoutMyTool runs checks like image alt-text auditing, font-embedding verification, and form-label association in your browser tab, so the document never leaves your machine. For anything sensitive, confirm the tool does not upload before using it.

Citations

W3C — “WCAG” overview, the standard and its A/AA/AAA conformance levels. w3.org/WAI — WCAG
W3C — “Understanding Contrast (Minimum),” the 4.5:1 / 3:1 AA contrast requirement. w3.org — Contrast (Minimum)
Wikipedia — “PDF/UA” (ISO 14289), the PDF accessibility standard supporting WCAG. en.wikipedia.org/wiki/PDF/UA

Meet AA, reach everyone

Audit alt text, check fonts and form labels, and validate compliance with ScoutMyTool’s in-browser tools — your document never leaves your machine.

Open the Alt-Text Audit →