Making PDFs Accessible: Tags, Read Order, Alt Text, and PDF/UA Compliance

PDF accessibility depends on meaningful structure, readable content and support for assistive technology. This guide explains common requirements and checks; a visual preview or a successful automated check alone is not proof of accessibility.

Why PDF Accessibility Matters

  • Legal requirements — accessibility duties vary by jurisdiction, organization and service. Check the law, procurement terms and standards that apply to your document rather than assuming a universal PDF/UA mandate.
  • Government requirements — US Section 508 and European requirements using EN 301 549 can apply to electronic documents within their defined scope. Applicable criteria and exceptions require a context-specific review.
  • Education — students with visual impairments need accessible course materials, syllabi, and exam papers.
  • Searchability — extractable text helps search and indexing. Tags provide semantic structure but are not a prerequisite for Google to index a PDF.
  • Reflow — properly tagged PDFs can reflow text for mobile viewing and zoom without horizontal scrolling.

Tagged PDF vs Untagged PDF

The foundation of PDF accessibility is the tag tree — a logical structure that describes the document's content hierarchy.

AspectUntagged PDFTagged PDF
What a screen reader seesText and structure inferred by the viewer; results varyHeadings, paragraphs, lists, tables, images with alt text
Reading orderInferred from content and layout; may be incorrectDefined by the tag tree; must be checked for correctness
TablesRead as disconnected text fragmentsRead as rows and columns with headers
ImagesMeaning may be unavailable without suitable alternativesAnnounced with alt text description
ReflowSome viewers infer reflow, with variable resultsCan support reflow when structure and viewer support are correct
Quick test: Open any PDF in Adobe Acrobat and try View → Reflow. Reflow can expose layout problems, but viewers may infer structure. It does not establish that tags exist or prove accessibility; inspect the tag tree and test reading order separately.

Essential PDF Tags

PDF tags map to familiar HTML-like semantics:

PDF TagHTML EquivalentPurpose
<Document><html>Root element of the tag tree
<H1> — <H6><h1> — <h6>Heading hierarchy for navigation
<P><p>Paragraph text
<L>, <LI><ul>/<ol>, <li>Lists and list items
<Table>, <TR>, <TH>, <TD>Same namesTable structure with header cells
<Figure><figure>Images and illustrations (holds alt text)
<Link><a>Hyperlinks
<Form><form>Interactive form containers
/Artifact marked content (outside the tag tree)n/aDecorative content to be ignored (headers, footers, page numbers, watermarks)

Reading Order

PDFs are not like HTML — there's no inherent "top to bottom" reading order. Content can appear anywhere on the page in any byte order. The tag tree defines the logical reading sequence.

Common reading order problems:

  • Multi-column layouts — a two-column page may read left column top to bottom, then right column, or it may zigzag between columns depending on how it was created.
  • Headers and footers — page numbers and running titles should be marked as /Artifact outside the structure tree so screen readers skip them.
  • Sidebars and call-out boxes — must be placed in the correct position in the tag tree, not just visually on the page.
  • Footnotes — should be linked to their reference points and positioned logically in the reading order.

Alt Text for Images

Every meaningful image needs alternative text. The rules:

  • Describe the content, not the appearance — "Bar chart showing Q3 revenue up 15% to $2.3M" is useful. "Image of chart" is not.
  • Be concise — aim for one or two sentences. For complex images like data charts, consider a longer description or a data table alternative.
  • Skip decorative images — purely decorative borders, dividers, and background images should be marked as /Artifact outside the structure tree with no alt text.
  • Avoid "image of" or "picture of" — screen readers already announce it as an image. Saying "image of a dog" is redundant; just say "Golden retriever in a park".

Accessible Tables

Tables are one of the hardest elements to make accessible in PDF:

  • Data tables need appropriate header semantics and associations so readers can relate cells correctly. Do not add misleading header tags to layout-only content; complex tables need additional manual checking.
  • Use the Scope attribute on headers to specify whether they apply to the row or column.
  • Avoid merged cells when possible — they confuse screen readers. If you must merge, define the header relationships explicitly.
  • Don't use tables for layout — only for tabular data. Layout tables are a major accessibility barrier.

Language Settings

The document language tells screen readers which pronunciation rules and dictionaries to use:

  • Set the primary language in the document properties (e.g., "en-US" for American English).
  • For multilingual documents, tag individual sections with their language (e.g., a French quote within an English document).
  • Without language settings, screen readers may mispronounce every word using the wrong language model.

Accessible Forms

  • Every form field must have a label that describes what to enter (not just placeholder text).
  • Group related fields (e.g., "Address" fields) using <Form> tags.
  • Provide tool tips for fields — screen readers announce these as instructions.
  • Ensure tab order follows the logical reading order (top to bottom, left to right).
  • Include error messages that are announced when validation fails.

PDF/UA Standard

PDF/UA (ISO 14289) is the international standard for accessible PDF. Key requirements:

  • All meaningful content needs appropriate structure; decorative content is marked as artifacts outside the structure tree.
  • Tags must be in a correct, meaningful order.
  • All images have alt text or are marked as artifacts.
  • Document language is set.
  • Font information allows Unicode mapping (for text extraction and search).
  • Bookmarks reflect the document's heading structure.
  • Security settings don't block assistive technology access.

Testing Tools

ToolCostWhat It Checks
Adobe Acrobat Accessibility CheckPaid (Acrobat Pro)Automated structural checks; reading order and alternative-text quality also require manual review
PAC (PDF Accessibility Checker)FreeAutomated PDF/UA checks and reports; human checks remain necessary
NVDA (Screen Reader)FreeReal-world screen reader testing on Windows
VoiceOverFree (built into macOS/iOS)Real-world screen reader testing on Apple devices
veraPDFFreeMachine-verifiable PDF/UA requirements; not a replacement for human checks

Accessibility Checklist

  • Tag tree with proper heading hierarchy (H1 → H2 → H3, no skipping)
  • Alt text on all meaningful images
  • Decorative elements marked as artifacts
  • Correct reading order (inspect tags and test with assistive technology)
  • Table headers defined with TH tags and scope
  • Document language set
  • Form fields labeled
  • Tab order matches logical reading order
  • Sufficient color contrast (4.5:1 for body text)
  • Bookmarks match heading structure
  • Tested with PAC and a screen reader

Frequently Asked Questions

A tagged PDF contains a structure tree describing meaningful content and logical relationships. Decorative material may be marked as artifacts rather than semantic content. Correct tags can help assistive technology, but missing or incorrect structure and reading order still require review.
Use a current PDF accessibility checker such as PAC or Acrobat for the supported automated checks. Also review reading order, alternatives and actual assistive-technology use. A passing automated check does not establish complete PDF/UA, WCAG or legal compliance.
Provide appropriate text alternatives for meaningful non-text content. Mark purely decorative material as artifacts so it can be skipped. For images, describe the content or purpose in context; complex charts may also need a longer description or data table.
PDF/UA is an ISO standard for accessible PDFs. Whether a particular conformance standard is required depends on the applicable law, contract and document context. Correct tags and automated checks are not enough by themselves: review reading order, alternatives and usability with assistive technology.
Partially. Run OCR (Optical Character Recognition) first to convert the image to selectable text. Then add tags, reading order, and alt text manually. Scanned PDFs are inherently harder to make fully accessible because OCR may introduce errors and the original structure is lost.

Need to organize your PDFs? Our tools run entirely in your browser — no uploads required.

Explore All PDF Tools →