PDF tags: structure, not a conformance guarantee
Source-backed explanations and practical guidance. Educational information, not a legal determination.
What tags contribute
PDF tags represent document structure, such as paragraphs, headings, lists, and tables. A tag tree is not the same as the visible page layout. Correct structure and reading order help assistive technology interpret a document. W3C’s PDF reading-order technique discusses checking tab and reading order.
A tagged file can still have barriers
Tags can be missing, incorrectly assigned, or ordered incorrectly. Images can lack meaningful alternatives and tables can have incorrect header relationships. Finding tags in a file is a starting point, not proof of WCAG conformance. Review the actual content and user tasks.
Check the actual export
Use an authoring workflow that preserves meaningful structure, then inspect the exported PDF. Application, version, platform, export settings, and source quality can affect the result. Do not infer tagging from a filename or assume that every export or print workflow behaves identically. Section508.gov’s PDF authoring and testing guidance is a useful starting point.
Text recognition and structure are separate checks
Optical character recognition (OCR) can add recognized text to image content. Some workflows also create tags; others do not. Verify recognized text for errors and inspect structure independently. A searchable scan is not automatically an accessible PDF. Read W3C’s OCR technique.
Specify the standard being evaluated
The Title II web rule adopts WCAG 2.1 AA. PDF/UA is a distinct PDF accessibility standard, not a replacement named in that rule. If PDF/UA is a project or procurement requirement, identify its version and evaluate it separately. This reference does not claim that a checker’s PDF/UA result establishes complete WCAG or legal conformance. Read the adopted web requirement.