Structure and sequence
Review headings, lists, tables, and meaningful reading order. The tag structure must represent the content and its relationships.
Start with the WCAG version your project requires
WCAG defines accessibility outcomes across content and technologies. Level AA conformance includes all applicable Level A and AA success criteria. For PDFs, the applicable checks depend on the document’s content and interactive features, rather than a fixed shortlist.
ADA Title II’s web rule uses WCAG 2.1 AA. The Revised Section 508 Standards incorporate WCAG 2.0 A and AA for covered electronic content, with specified exceptions for non-web documents. WCAG 2.2 is a useful target for current accessibility work when the project permits it.
Check the document people will use
Images and visual information
Provide meaningful text alternatives and check contrast, use of color, and information conveyed through images.
Forms and keyboard access
Check labels, instructions, keyboard operation, focus order, and error handling for interactive elements.
Navigation and readability
Review the title, document language, descriptive links, zoom and reflow behavior, and navigation appropriate to the file.
For interpretation across non-web documents, use W3C’s WCAG2ICT guidance. Review every applicable success criterion; a checklist of common issues does not replace that assessment.
How PDF/UA supports the work
PDF/UA defines PDF-specific requirements for accessible structure and use. In most cases, it provides a strong foundation for PDF accessibility work. WCAG conformance also depends on the applicable criteria and the content’s actual usability; PDF/UA conformance alone does not establish it.
Combine PDF-specific validation with review of meaning, visual presentation, keyboard interaction, and the reading experience. See the PDF/UA and WTPDF guide.
WCAG 2.0, 2.1, and 2.2
Keep the required legal or contractual baseline separate from the version you choose as a product target. WCAG 2.1 extends 2.0, and 2.2 extends 2.1. Check the W3C recommendation and the specific requirements your project must meet.
Set the target before remediation
Public entities should review ADA Title II requirements. Federal agencies and suppliers should review Section 508 and the applicable procurement criteria. Other organizations should confirm their legal, contractual, and user requirements.
Questions before you start
Is meeting PDF/UA-1 enough for WCAG?
In most cases, PDF/UA-1 provides a strong foundation for PDF accessibility. Confirm the remaining applicable WCAG criteria, including visual and interactive requirements, before making a WCAG conformance claim.
Can an automated pass replace a document review?
Automated checks provide evidence about the rules they test. Meaningful descriptions, logical relationships, and the reading experience still need appropriate review.