Accessible PDF knowledge base

Readers need to find, understand and use the information without relying on the visual layout. Tags support that process.

Tags describe content. Reading order connects it. Bookmarks help readers find major sections.

Choose the format around the reader’s task. Everyday web information is often easier to use as HTML.

Fix the source when the problem would otherwise return with the next export. Repair the PDF where export falls short.

Short explanations of the terms used in tools, requirements and test reports.

PDF/UA-1 defines how PDF technology is used for accessible documents. It is not a complete WCAG assessment.

PDF/UA-2 is based on PDF 2.0. Choose it when the workflow and the recipient’s tools support the standard you need.

WCAG defines accessibility requirements. For a PDF, those requirements need to be assessed against the document’s content and functions.

EN 301 549 contains ICT accessibility requirements. Clause 10 addresses non-web documents.

PDF/A addresses long-term preservation. PDF/UA addresses accessibility. A file may need to meet both.

No. The result covers the rules the tool actually checked. The meaning of the content also needs review.

The directive covers public sector websites and apps. PDFs can form part of the content within its scope.

No. First determine whether the product or service is covered. Then assess the document’s role in it.

Public sector bodies need to assess PDFs used in their digital services. Responsibilities, exceptions and feedback are part of the same process.

The Act covers specified products and services. A PDF’s connection to the service is central to the assessment.

Norwegian requirements vary by organisation and context. Documents on a website need assessment as part of the web solution.

UK guidance points to WCAG 2.2 AA and an accessibility statement. Exceptions for older documents have limits.

Section 508 addresses federal ICT. It is distinct from ADA Title II rules for state and local governments.

DOJ guidance now gives 26 April 2027 and 2028. Older summaries quoting 2026 and 2027 need checking.

Find the purpose of standard tags and see which names differ between PDF 1.7 and PDF 2.0.

Heading tags make the document outline navigable. Levels should follow meaning, not font size.

A list needs a shared structure. Bullet characters before ordinary paragraphs are not enough.

Tagging a box as Table is not enough. Readers need to know which headers belong to each value.

Describe what the reader needs to know in this context. A list of colours and shapes is not always useful.

Readers need to understand where a link goes and activate it by keyboard. Link text, structure and destination must agree.

Decoration should not interrupt reading. Information must not be hidden just because it is difficult to tag.

Identify the text’s language and give the document a meaningful name. This supports pronunciation and orientation.

A character can look correct but fail during copying or speech. Investigate the underlying text representation.

A custom tag needs an understandable standard meaning. Calling something ChapterHeading does not tell assistive technology its level.

Use structure in Word, export with tags and check the final file. Printing to PDF is a different workflow.

Map styles to tags and plan reading order in the source. Then check what export actually produced.

A slide often contains many separate objects. Set their reading order before export and inspect the PDF afterwards.

Start with the document’s actual structure. Automatic tagging and accessibility checks support the work; they do not provide a final decision.

Text recognition makes content machine-readable. The characters and document structure then need checking.

Specify the documents, the reader’s tasks and the evidence required at handover.

PAC helps identify technical issues and inspect document structure. Content review and practical tests still matter.

veraPDF tests formal rules for standards including PDF/A and PDF/UA. For PDF/UA, the result covers machine-verifiable requirements.

Test what the reader needs to accomplish. Listening to the first page is not enough.

Follow the meaning through the document. Also check link and form order where those interactions exist.

Choose a data cell and try to understand it without seeing the table. Then test several routes through the table.

Use this checklist to gather evidence and expose gaps. It does not replace the requirements of the standard or law being assessed.

We created a synthetic report and processed it with our PDF engine. Its appearance stayed unchanged while structure and automated results changed.

A well-designed two-column page can have an incorrect reading order. Here is how the same text needs to be sequenced to make sense.

A number alone says little. Here we connect a value to its month, measure and column.

Use the short description to convey the finding and give readers access to detail. Here is our worked example.

Here are six recurring mistakes. Use the examples to check whether a repair actually helps the reader.