PDF accessibility errors, explained.

Why does “title failed” appear?

A filename is not the same thing as a document title. A finding can refer to missing title metadata, a viewer preference such as DisplayDocTitle, or another profile-specific rule. Expand the finding and read its rule description before changing anything.

For example, a PDF called annual-report-final-v3.pdf might need the descriptive title “Annual report 2026” in its document properties, and the viewer preference to show that title. Changing the filename alone will not address those checks.

• Set an accurate, useful title in your authoring application or a PDF editor.
• If the finding names the display-title preference, enable the option that displays the document title in the viewer.
• Export again and recheck. Open the PDF as well: a technical pass does not tell you whether the chosen title is helpful.

“Tagged PDF failed” or missing document structure

A tagged PDF has structural information that identifies content such as paragraphs, headings, lists, and tables. A flag that says the document is tagged is only one part of that structure. A missing structure tree or content that is neither tagged nor marked as an artifact can produce different findings.

Start with the editable source where possible. Apply real heading, list, and table structure, then export with the application’s accessibility or tagged-PDF options. If you only have the PDF, use a capable tagging editor and inspect the result. Merely setting a “tagged” flag does not create meaningful tags or a correct reading order.

A scanned page may be an image without usable text. OCR can provide text, but it still needs accuracy checks and an appropriate structure. Converting a scan does not by itself make it accessible.

Document or passage language is missing

Language information helps assistive technology pronounce text correctly. A check can detect absent or invalid language information; it cannot reliably decide that every passage is marked with the right language.

Set the document’s primary language, then mark passages written in a different language where your editor supports it. Re-export and listen to representative passages with assistive technology. Changing the visible text or the filename does not set the PDF’s language metadata.

Fonts, text mapping, and readable characters

Font-related findings do not all mean the same thing. An embedding finding concerns the font program being available in the PDF. A character-mapping finding concerns how encoded characters relate to usable text. Use the exact rule to choose your next step.

For embedding problems, check the export settings and whether the font license permits embedding. For mapping problems, try copying text, searching for a phrase, and reading the document with assistive technology. Export from the original text where possible. Converting text into outlines or a picture can remove usable text rather than solve the accessibility problem.

Visual appearance alone is an incomplete test: a page can look correct while text extraction or pronunciation is wrong.

What does “tagged annotations failed” mean?

Links, comments, and form controls can be represented as PDF annotations. A finding may concern an annotation’s association with the document structure or another requirement for that annotation type. Read the rule and any object or page context in the report; not every annotation follows the same rules.

Inspect the affected link, control, or comment in a PDF editor that exposes accessibility structure. Check its structural association and accessible description as appropriate. For forms, also test labels, instructions, keyboard focus, and operation. Deleting all annotations can remove useful content and is not a general repair strategy.

Our checker preserves the validator’s rule context where available. It does not promise a visual highlight or a page number for every object.

A passing automated report still needs human review

veraPDF’s validation scope is machine-verifiable requirements. A technical pass cannot establish that a diagram’s alternative text communicates its purpose, that reading order makes sense, or that a table is understandable.

• Reading order: follow multi-column text, footnotes, captions, and sidebars in a meaningful sequence.
• Alternative text: judge whether it explains the purpose of each meaningful image without needless repetition.
• Structure and tables: check heading hierarchy, lists, table headers, and how relationships are conveyed.
• Interaction: try links and forms using a keyboard and suitable assistive technology.
• Visual and content review: inspect contrast, use of color, instructions, language changes, and text at increased zoom.

The tool includes a separate manual checklist. Marking an item reviewed records your own review in the downloaded report; it is not a new automated test or an accessibility certificate.