What is WCAG for PDF

Source: Dev.to

Overview

The Web Content Accessibility Guidelines (WCAG) are a set of recommendations developed by the W3C’s Web Accessibility Initiative (WAI) to make digital content more accessible for people with disabilities and for a wide range of user agents, including limited devices and services such as digital assistants.

WCAG is not detailed for PDF. Its four principles—perceivable, operable, understandable, and robust—apply broadly across digital formats, but they do not cover the technical specifics required to make a PDF truly accessible (e.g., tagging, reading order, alternative text).

WCAG and PDF/UA

When it comes to PDFs, WCAG compliance is usually interpreted through PDF/UA (PDF Universal Accessibility), the ISO standard specifically designed for accessible PDF documents.

• PDF/UA provides the technical blueprint for achieving the accessibility goals set by WCAG within the PDF format.
• PDF/UA is defined in two parts:
  • ISO 14289‑1: Electronic document file format enhancement for accessibility – Part 1: Use of ISO 32000‑1 (PDF/UA‑1)
  • ISO 14289‑2: Document management applications — Electronic document file format enhancement for accessibility – Part 2: Use of ISO 32000‑2 (PDF/UA‑2)

In practice, WCAG compliance for PDFs is often treated as equivalent to PDF/UA compliance with a few additional checks:

WCAG for PDF = PDF/UA + contrast requirements of WCAG – XMP metadata identification of PDF/UA + extra minor sanity checks

More details can be found at the validation service: .

Tagged PDF

PDF/UA covers all relevant accessibility requirements for tagged PDFs, ensuring proper structure, reading order, and usability for people with disabilities.

• PDF4WCAG visualizes the structure tree in the right pane of the error preview.
• For deeper inspection of structure elements, properties, and attributes, the tool ngPDF is recommended.
• See the PDF Association’s Q&A about Tagged PDF for additional guidance.

Contrast Checks

WCAG Success Criterion 1.4.3 (Contrast Minimum) requires:

• A contrast ratio of at least 4.5:1 for normal text.
• A contrast ratio of at least 3:1 for large text (18 pt or larger).

PDF4WCAG incorporates these contrast checks into both its WCAG 2.2 Machine and Human profiles, supporting all PDF color models when computing contrast.

Metadata Requirements

Both PDF/UA and WCAG require certain metadata, such as the presence of a dc:title (Dublin Core) property in the PDF document metadata. This satisfies WCAG Success Criterion 2.4.2 (Page Titled).

Basic Sanity Checks (PDF4WCAG)

The WCAG 2.2 Machine Validation for PDFs performs a set of basic sanity checks to ensure essential accessibility criteria are met:

1. Document Structure and Tagging – Verifies inclusion of the ISO Technical Specification 32005 (PDF 1.7 and 2.0) structure namespace as defined in ISO 32000‑2.
2. Tagged Links and Annotations – Ensures links are tagged with meaningful, descriptive text (per WCAG 2.2 link‑purpose guidelines).
3. Page Orientation – Confirms that all pages share the same orientation, satisfying WCAG Success Criterion 1.3.4 (Orientation).
4. Non‑Empty Structures – Checks that structural elements are not empty, helping maintain a usable document hierarchy.

Using PDF4WCAG to automate these validations saves time and helps ensure PDFs comply with the latest accessibility standards.