Check whether a PDF can be read in the right order

Write down the sequence before checking the file

For a fictional service report, the intended sequence is title, reference, period, summary, work-item table and explanatory note. In the table, a task identity must remain associated with its label and status. A sighted reader may reconstruct those relationships from position; a different reading route cannot be expected to guess them.

This is a proposed test, not a claim that any generator produces the correct structure. Keep the first fixture simple enough to identify a misplaced item. Add a second column, graphic or interactive field only when the report actually requires one.

Inspect the exported PDF, not just the designer

W3C’s PDF3 technique explains how tagged structure and content order affect reading sequence, and how keyboard order affects links and fields. It recommends checking with suitable accessibility/read-aloud tools and testing focus traversal. Complex layouts can require correction after export.

Record the exact file, viewer and checking method. Start at the beginning and compare the observed sequence with the fixture. When a heading, table or sidebar appears in the wrong place, record that location rather than calling the whole document “screen-reader ready.” An automated checker finding no errors is not a substitute for understanding the result.

Check interaction separately from reading

1. Identify any links or fields that genuinely belong in the report.
2. Use keyboard navigation in an appropriate PDF viewer.
3. Record whether each intended control is reached in a sensible sequence.
4. Check whether its label and nearby explanation make its purpose clear.
5. Retain a failing example and the corrected output as separate versions.

Do not activate a payment, approval or external account action merely to test focus. A report without interactive fields still needs meaningful content structure; absence of forms does not settle the rest of accessibility.

Treat a mandatory failure as a buying constraint

If your audience requires an accessible deliverable, put that requirement in the brief before subscribing. Ask for evidence of the actual output path you would use, not an unrelated sample or a claim about the vendor’s website. If a repair step is necessary, include its skill, tooling and review effort in the comparison.

PDF3 covers particular reading and focus-order concerns. It is not a complete conformance audit, and this publication has not certified CraftMyPDF or DocuGenerate output. Image alternatives, document language, headings, tables and other requirements need their own applicable review. Keep the unanswered requirement visible; use a suitable alternative format when the responsible owner determines that is appropriate.