Skip to content
Accessibility library

Standards · 4 MIN READ

WCAG, PDF/UA, and Section 508 explained

Different standards and requirements serve different purposes. Agree on the target, version, and acceptance checks before remediation begins.

WCAG: accessibility guidance

The Web Content Accessibility Guidelines define success criteria organized around content being perceivable, operable, understandable, and robust. WCAG has versions and conformance levels; a project should identify the specific target rather than use “WCAG compliant” without qualification.

PDF/UA: PDF-specific requirements

PDF/UA addresses accessibility in PDF files. Its requirements go beyond a file’s appearance. Our automated pilot records a PDF/UA-1 machine-check result; that result does not establish all human-checkable requirements or every other accessibility obligation.

Section 508: a U.S. federal context

Section 508 concerns accessible information and communication technology in the U.S. federal context. Section508.gov provides PDF authoring, testing, and remediation resources. Which requirements apply to a particular organization or contract must be established for that project.

Explore the source guidance

These guides introduce the topic. Agree on the specific document requirements and review scope for your project.

Keep learning

What makes a PDF accessible?What automation can—and cannot—confirm

THE NEXT DOCUMENT CAN BE BETTER

Make accessibility part
of your publishing process.

Prepare your project