Accessible PDF Checklist: Points to Verify

Updated · 4 min read

On this page
  1. Structure
  2. Text and reading order
  3. Images
  4. Tables
  5. Forms
  6. Metadata
  7. Verification

An accessible PDF checklist is only useful if it covers the failures that actually happen, and those cluster in seven groups: structure, text and reading order, images, tables, forms, metadata, and verification. A file can sail through one group and fail the next, so the checklist is meant to be worked end to end. Use this one before a document is published, and again after any edit that changes its structure.

Structure

Structure is the foundation, and everything else depends on it.

  • The document has a structure tree, meaning it is tagged rather than a flat page.
  • Headings use heading tags, not bold text that looks like a heading.
  • Heading levels are nested correctly, without skipping from H1 to H4.
  • Lists use list tags, including nested lists.
  • Decorative elements such as borders and running headers are marked as artefacts.

A file with no tags fails here before anything else is worth checking. Bold text styled to look like a heading is the most common trap, because it looks right on the page and reads as body text to a screen reader.

Text and reading order

  • The reading order matches the logical order of the content.
  • Multi-column layouts read down each column, not across.
  • Sidebars, captions and footnotes appear where a reader would expect them.
  • The text is real text, not an image of text, so it can be selected and enlarged.
  • Any language change within the document is marked.

Reading order is the item people skip and the one that matters most. A two-column page is the classic failure: the tag tree follows the geometry and the reader hears alternating lines from each column. See tag PDF for accessibility for why the tree drives this.

Images

  • Every meaningful image has alternative text that describes what it conveys.
  • Decorative images are marked as artefacts and skipped.
  • Charts and diagrams have a description or an adjacent data table.
  • Logos that carry information have a short description; purely decorative logos do not.

Alt text is the clearest place where no tool can decide for you. A machine can find an image; only a person knows whether a photo of a ribbon cutting needs a description or is decoration.

Tables

  • Data tables use table tags with rows and cells.
  • Header cells are marked as headers, not data cells.
  • The table has a clear relationship between a cell and its column and row.
  • Tables are used for data, not for page layout.

A table used for layout confuses assistive technology, because it announces a structure that is not there. Convert layout tables to a proper layout and keep table tags for real data.

Forms

  • Every field has a description a screen reader can announce.
  • The tab order follows the visual order of the fields.
  • Fields are grouped logically, and required fields are indicated.

Interactive forms are the hardest category, and they are where a browser-based fixer cannot help. If your document is a fillable form, plan for a desktop tool or a specialist.

Metadata

  • The document language is set.
  • The document has a meaningful title, not a filename.
  • The flag that tells a reader to announce the title is set.

These are quick to set and easy to forget, and a validator will catch them.

Verification

CheckToolWhat it catches
Structural conformancePAC 2024, veraPDFTag, metadata and table failures
Reading orderScreen reader passSequence errors a validator misses
Alt text qualityHuman reviewDescriptions that are present but wrong
ContrastHuman reviewText that is hard to read

Run a validator such as PAC 2024 or veraPDF and keep the report. Then read the file with a screen reader yourself. The automated half is fast; the manual half is where the remaining failures hide, as PDF accessibility testing explains.

Two habits make the checklist stick. Keep the validator report with the document, so the evidence travels with the file. And re-run the whole checklist after any edit, because a new table or image can break a file that passed last month. If you are working through a set of documents rather than one, sort them into the routine and the complex first. The routine files clear this checklist quickly; the complex ones, forms and dense tables in particular, are where the time goes and where a specialist earns their fee.

A worked example: a district office publishes a policy PDF. The validator passes it, so the automated checks are clean. A screen-reader pass then reveals the headings are tagged as paragraphs, so the document cannot be navigated by heading, and two images have alt text that reads as the filename. The file was tagged and still failed the checklist, which is exactly why both halves are needed.

TagRight covers the first pass: it tags a PDF in the browser and returns a report of the heading outline and what still needs a human, which is a fast way to find the items above that a tool can and cannot settle. It does not write alt text, does not support interactive forms, and cannot tag a scan with no text layer, and it is a remediation aid rather than a certification. Work through the accessible PDF guide for the concepts, start with a free document to see what the first pass catches, and see the plans and pricing if you are handling documents in volume.

Frequently asked questions

What should an accessible PDF checklist cover?

Seven groups: structure, text and reading order, images, tables, forms, metadata, and verification. A file can pass some groups and fail others, so work through all of them before you publish.

What is the single most important item on the checklist?

A correct reading order. A file can have every tag and every alt text and still be unusable if the reading order is wrong, and that is the failure a validator is least likely to catch for you.

Can I check all of this automatically?

No. Validators such as PAC 2024 and veraPDF catch structural and metadata problems, but alt text quality, reading order and contrast need a human, and usually a screen-reader pass.

How often should I run the checklist?

On every document before it is published, and again after any edit that changes structure. A file that passed last year can fail after a new table or image is added.

Does passing this checklist mean my PDF is compliant?

It means the document is in good shape, not that it is certified. Compliance depends on the rule you are under, such as Section 508 or ADA Title II, and on verifying with a recognised tool. Treat the checklist as diligence, not a guarantee.

Tag a PDF free