PDF accessibility basics
How to check if a PDF is tagged
Inspect its tagging flag and structure tree. Our free checker shows both signals without uploading your document. Tags describe elements such as headings and paragraphs; their presence alone does not prove accessibility.
Check your PDF’s tagging signals →
Start with a real example
These two one-page teaching files contain similar visible text, but different underlying structure. Open either file if you want to inspect it yourself, or use the example buttons in the checker. They are demonstrations, not certified accessible documents.
Without tags
Text can be extracted, but the file has no tagging flag or page structure tree. Selectable text does not mean the PDF is tagged.
Open untagged example (PDF)With a simple tag tree
The file declares a tagging flag and includes a heading and two paragraphs in its structure. Those signals do not verify all accessibility requirements.
Open tagged example (PDF)Run the examples through the checker →
Check it in your browser
- Open the PDF checker and choose your file, or try an example.
- Expand Tagging signals in the report. Read the marked flag and how many pages expose structure.
- If structure is missing, revisit the source document and its export settings. If structure is present, inspect whether its tags describe the content correctly.
The checker reports two independent observations. A document can expose structure even when its tagging flag is absent. Neither a flag nor a tree proves that every image, table or paragraph has been tagged correctly. A page without an exposed tree also needs context: for example, it might be blank.
Check tags in Adobe Acrobat Pro
Open the Accessibility tags panel to inspect the document’s structure. Adobe’s current instructions place it under View → Show/Hide → Side panels → Accessibility tags; menu placement can vary by version and platform.
Expand the tree and compare its headings, paragraphs and other elements with the page. An empty tree calls for investigation. A populated tree still needs a review of completeness, semantics and sequence. See Adobe’s guide to checking PDF accessibility for the interface and repair options.
What to do when tags are missing
Start in the original authoring file when you have it. Use real heading styles and meaningful document structure, then choose an export option that preserves accessibility tags. Reopen the exported PDF and check it again. Export settings and their names depend on your software.
If you only have the PDF, use a PDF editing tool that supports tagging and inspect its output. Automatic tagging needs review, especially for columns, tables and complex layouts. This checker identifies signals; it does not add or repair tags.
Tagged does not mean fully accessible
A tag tree can still describe content incorrectly or put it in the wrong order. Review reading order and meaning with appropriate tools and assistive technology. W3C’s PDF reading-order technique explains why structure and navigation must match the document’s meaning.
Our first pass does not establish PDF/UA or WCAG conformance. It also does not fully assess contrast, forms, links, font encoding or alternative-text quality. For a fuller assessment, combine an appropriate validator with manual review. Read exactly what this checker covers.
Optional analytics
Help us measure visits. Your choice does not affect access to this guide or the checker. How measurement works.
Continue your review
PDF accessibility checklist: automated signals, manual checks and a printable workflow →