Why is visual review alone insufficient?
W3C WCAG 2.2 Technique PDF3 explains that tagged PDF reading order is primarily determined by tag order, while keyboard focus order controls navigation through interactive content. It describes how visually clear columns can be read across in a confusing sequence when the structure is wrong.
PDF3 is an informative technique for tagged PDFs, not a requirement that every tender use a particular authoring tool. Returnables Agency is independent and is not affiliated with W3C. This guide does not certify WCAG conformance or determine legal accessibility obligations.
Sources: World Wide Web Consortium: WCAG 2.2 Technique PDF3, updated 15 July 2025
Which checks belong in the response export review?
Use the buyer's actual submission instructions and required accessibility basis. Review the final exported file, because edits and conversion can change structure. Keep a sample of the reading sequence and any unresolved issue linked to its page and response requirement.
| Content | Practical check | Evidence to retain |
|---|---|---|
| Question and answer | Question is followed by its intended response | Observed sequence and page reference |
| Columns | First column is completed before the next when intended | Read-aloud or accessibility-API review |
| Supporting table | Headers and data remain understandable together | Table-specific sequence issue or confirmation |
| Links or fields | Keyboard focus follows the intended document sequence | Actual tab navigation observation |
| Decorative content | Does not interrupt substantive response meaning | Reviewer observation under required basis |
| Final version | Reviewed PDF matches approved response and upload file | Filename, version and sign-off reference |
How can an exported answer become misleading?
Illustrative example. A synthetic tender response places the proposed electrical methodology in a left column and limitations in a right column. The visual reviewer reads the full methodology and then the limitations. A read-aloud review instead alternates between both columns, mixing unrelated sentence fragments.
The writer records the affected page and fixes the source document structure or exported tags through the authorised document workflow. The writer then repeats the sequence check on the new final PDF. A screenshot of a neat page does not close the reading-order issue.
Keep the response's substantive limitations in the correct sequence. Do not remove them merely to simplify a layout. This check supports faithful access to the approved answer, not rewriting the commercial position.
What should the final reviewer retain?
W3C PDF3 proposes checking reading order with a screen reader, read-aloud tool or accessibility API, and checking tab order for focusable content. Use those observations alongside the actual required review process; passing one check does not establish all accessibility requirements.
Record the final PDF version, pages reviewed, method used, issues corrected and remaining actions. If the buyer mandates a template, preserve its required content and obtain approval for any structural change. Review the file actually submitted rather than assume it matches a previously checked draft.
Common questions
What else should the bid team know?
Is a visually neat PDF enough?
No. Check the logical sequence and relevant keyboard focus order.
Does this checklist certify WCAG conformance?
No. It addresses a specific export-review task.
Should the source document or final PDF be reviewed?
Structure the source carefully and check the actual final exported PDF.
Primary sources
- WCAG 2.2 Technique PDF3, updated 15 July 2025World Wide Web Consortium