1. Decide what should remain on the page
GOV.UK guidance prefers HTML where possible, including to respect browser settings. Our practical recommendation is to let visitors understand the subject and next action before opening a file. Requirements specific to British public bodies are not presented here as universal rules.
In a fictional appointment preparation sheet, keep essential steps on the page and offer a printable copy if useful. Identify the audience, required languages and person responsible for keeping both versions current. Do not label a summary as a full alternative when information is missing.
2. Structure the document before exporting
WAI technique PDF9 describes tagged headings that assistive technologies can recognize for navigation between sections. Use real heading styles in the source file, then check that the exported PDF retains that structure. Larger or bold text alone does not demonstrate heading tags.
For the fictional sheet, organize sections such as “Before the appointment”, “Documents to prepare” and “On the day”. Also review lists, tables and image explanations according to their purpose. Assign complex content to someone qualified. Keep the source document as the starting point for future corrections.
3. Check the text and document title
WAI explains that a scan made only of images provides no usable text. Optical character recognition can produce text, but the result needs checking. PDF18 separately describes a document title that is set and displayed by the viewer; it is distinct from the filename.
Search for several words and copy a passage from the final PDF to spot missing characters. This initial check does not establish accessibility. Review names, numbers and accents, then check the title in document properties and its display in a compatible viewer. Repeat for every translation actually offered.
Source : W3C WAI — PDF7: Actual text and OCR · Source : W3C WAI — PDF18: Document title
4. Check reading order and links
Technique PDF3 relates logical order to document tags and describes checks with a screen reader or suitable tool. Columns may look clear while being read in a confusing order. Keyboard-focusable elements also need a meaningful sequence.
Have someone equipped for this check work through the final document. In the fictional sheet, requested documents should be read with their corresponding explanations. Then try links with the keyboard, their destinations and returning to the document. Record the viewer, pages checked and corrections; visual inspection alone does not validate this point.
5. Make the download predictable
As an editorial rule for your page, name the content in the link and state the format, language and actual file size. For example: “Preparation sheet — PDF in English”. Add the measured size at publication; you do not need an invented size to draft the label.
In an isolated preview, open the link on desktop and phone, then check the document, version and return to the page. Try reading the HTML version too. If the link or viewer fails, the page should still provide the agreed essential information and a way to find the alternative. A successful download alone does not justify calling the file accessible.
6. Keep a traceable publication decision
Use the worksheet below to connect the page, source file and final PDF. Run the checks available in your tools and complement them with human checks suited to the content. The cited WAI techniques are implementation examples, not an exhaustive requirement list or a certificate.
After corrections, export again and repeat affected checks. When replacing a document, check that the public link serves the new version and that the page retains no outdated dates or descriptions. If a language or check is missing, record that limit and its owner before deciding to publish.
Downloadable document preparation worksheet
| Area | Result to check | Evidence to keep |
|---|---|---|
| Page | Essential information and alternative identified | Address and scope |
| Source | Structured headings and content | Source file version |
| Text, title and order checked | Viewer, observations and corrections | |
| Link | Correct document, actual language and size | Address and served version |
| Mobile | Opening and return checked | Device and result |
| Follow-up | Known limits and owner | Dated decision |
Frequently asked questions
Is a PDF/A file automatically accessible?
No. GOV.UK explains that the A refers to archiving. It does not replace checking content and structure. Define preservation and accessibility needs separately.
Is selectable text enough?
No. It is a useful initial sign, but structure, reading order and information carried by images still need checking, among other things. The result depends on the document and agreed requirements.
Must every attachment be translated?
Agree the required languages with your team. State which are available and check each file. Do not send a link described as English to another language without clearly saying so.
Prepare your next document
Choose an existing document, find its source file and complete the worksheet with the content owner. Then decide on the HTML version and necessary checks before setting a publication date.
Sources and scope
Primary sources checked on November 4, 2026. References support the cited technical points. The example, worksheet and acceptance process are editorial proposals. No real document audit, client outcome, service commitment or legal advice is claimed.
