# Accessible PDF: Tags, Reading Order and Alt Text

Source: https://allyway.ai/glossary/accessible-pdf

An accessible PDF is a tagged PDF whose structure – headings, lists, tables, links and form fields – is stored in the file, with a logical reading order, text alternatives for images, a document title and a language. This is how a PDF meets WCAG 1.3.1 Info and Relationships at Level A.

An accessible PDF is a PDF that a screen reader can read in the right order, with headings to jump between, tables it can navigate and images it can describe. Many PDFs on websites – price lists, menus, brochures, terms and conditions – are just pictures of text or untagged exports, so assistive technology reads them as one long stream of words or as nothing at all. The fix starts in the source document, long before the file is exported.

## What it means

WCAG applies to PDFs just as it does to web pages. The key criterion is [WCAG 1.3.1 Info and Relationships](https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html) (Level A): information, structure and relationships conveyed through presentation must be programmatically determined or available in text. In a PDF, that structure lives in **tags** – a hidden tree that says "this is a heading", "this is a list", "this is a table header". Without tags, a large bold line is just large bold text.

W3C publishes a set of PDF techniques. The most important ones:

| Technique | What it covers |
|---|---|
| PDF9 | Headings marked with heading tags |
| PDF6 / PDF20 | Tables with table tags, mistagged tables repaired |
| PDF21 | Lists with list tags |
| PDF3 | Correct tab and reading order |
| PDF1 | Alt text for images with the Alt entry |
| PDF4 | Decorative images hidden as artifacts |
| PDF10 / PDF12 | Labels, name, role and value for form fields |
| PDF16 | Document language in the document catalog |
| PDF18 | Document title in the document information |
| PDF7 | OCR for scanned documents, so they contain real text |

For EU law, the standard EN 301 549 handles downloadable documents in its own chapter 10 ("Non-web documents"); 1.3.1 becomes clause 10.1.3.1. The [European Accessibility Act](https://allyway.ai/regulations/eaa) points to this standard – see [EN 301 549](https://allyway.ai/regulations/en-301-549).

> **Tip:** > **Start in the source file**
> Use real heading styles, list buttons and table tools in your word processor, add alt text to images there, and export with the option to create a tagged PDF. Repairing an untagged PDF afterwards takes far longer.

## Examples

A tagged PDF stores a structure tree next to the visible page. Simplified, a well-tagged price list looks like this:

```html title="Example"
<Document lang="en">
  <H1>Price list 2026</H1>
  <P>All prices include VAT.</P>
  <Figure Alt="Our shop in Vienna, front view"/>
  <Table>
    <TR><TH>Service</TH><TH>Price</TH></TR>
    <TR><TD>Basic check</TD><TD>€49</TD></TR>
  </Table>
  <L>
    <LI><Lbl>•</Lbl><LBody>Free parking</LBody></LI>
  </L>
</Document>
```

The heading is an `H1`, the image has an `Alt` entry, the table has `TH` header cells and the list uses `L`, `LI`, `Lbl` and `LBody` – the same ideas as in [accessible tables](https://allyway.ai/glossary/accessible-tables) and a good [heading structure](https://allyway.ai/glossary/heading-structure) on the web.

**Do:** Do

Export from a source with real styles, keep tags on, write [alt text](https://allyway.ai/glossary/alt-text) for meaningful images, mark decorative images as artifacts, set title and language, and offer an HTML version of key content where possible.

**Don't:** Don't

Publish scanned pages without OCR, convert text to outlines or images, build tables from tab stops, rely on visual formatting alone, or ship a PDF form without field labels.

## How to check an accessible PDF



## Questions

Q: What is a tagged PDF?
A: A tagged PDF contains a hidden structure tree that marks headings, paragraphs, lists, tables, figures and links. Screen readers use these tags to read the content in order and to let users navigate. Without tags, structure only exists visually.

Q: Does WCAG apply to PDF documents?
A: Yes. W3C publishes dedicated PDF techniques for WCAG, for example PDF9 for headings and PDF1 for alt text. In the EU, EN 301 549 covers downloadable documents in chapter 10, so a PDF on your website falls under the same success criteria.

Q: Can a scanned PDF be accessible?
A: Only after optical character recognition (OCR), W3C technique PDF7. A scan without OCR is an image of text: screen readers find nothing to read. After OCR, check the recognized text, then tag the structure.

Q: Should I offer HTML instead of a PDF?
A: Where the content is important – opening hours, prices, terms – an HTML page is usually easier to make accessible, adapts to small screens and is easier to keep up to date. A PDF can still be offered as a download next to it.

Q: How do I find accessibility problems on my web pages?
A: For PDFs, use the checks above. For the web pages that link to them, a free [WCAG scanner](https://allyway.ai/free-wcag-accessibility-scanner-for-websites) shows issues such as missing alt text or unclear headings in seconds.
