A brochure can look polished and still be the wrong place for a customer to find today’s service information. A web page can explain the offer well and still be awkward to take into a meeting. Before choosing a format, decide what the reader needs to do with the information.
For many business sites, the useful answer is a maintained web page with a download that has a specific purpose. That is a content-planning choice, not a rule that every PDF should disappear. The important part is knowing which version to update and what happens when someone lands directly on the file.
Start with the task, not the existing file
Write one sentence describing the customer’s task: “Check whether this service suits my project,” “Share these specifications with a colleague,” or “Keep a copy for an upcoming meeting.” Then note where they are likely to read it and which facts could change before they act.
If the only reason for offering a PDF is that the brochure already exists, pause before making it the entire service page. A visitor who needs one answer should not have to work through a long document to discover whether the service is relevant. Conversely, a useful downloadable reference does not need to be removed merely because a web page exists.
The UK Government Digital Service’s document guidance favours HTML where possible so readers can use their browser preferences. That is a useful publishing consideration, not a statement of Canadian legal requirements or proof that any particular web page is accessible.
Compare three fictional cases
These businesses and situations are invented examples, not ZXP clients or measured results. They illustrate different jobs for content; they do not establish that one format always produces more enquiries.
| Customer task | Useful starting format | What to maintain |
|---|---|---|
| Check a catering company’s current service area and enquiry options | A web page with the current facts and next step | Service area, availability wording and enquiry route |
| Send an equipment specification to a purchasing colleague | A clearly labelled PDF beside a short product page | Document version, product identity and confirmation route |
| Take a design studio’s service summary to an internal meeting | A concise downloadable handout supported by a web page | Date, scope summary and link to current information |
In the equipment example, a PDF is useful because a colleague needs a self-contained reference. It is not permanently accurate just because its layout is fixed. A changed specification still needs a controlled update. The product page should help the reader identify the file and confirm that it applies to the product they are considering.
Give each format a job
Use the web page to answer the questions a new visitor needs before deciding whether to continue: what the offer covers, who it is for, important limitations and how to ask for more information. Treat a download as a deliberate next step, not a substitute for that basic explanation.
The downloadable version might contain a printable summary, detailed reference material or a meeting handout. Label the link with its purpose and format rather than “Click here.” If you display a file size or version, confirm it from the file you actually publish. Do not leave a previous version’s label beside a replacement.
Do not choose HTML on the assumption that Google cannot read PDFs. Google’s supported file-type list includes PDF. That does not guarantee that a particular file will be indexed or rank. Plan for someone to reach the document directly without first seeing the web page.
Give that reader enough context inside the document: the business name, what the document covers, its version or issue date where relevant, and a useful route back to current information. Avoid writing “see the website” without identifying which page the person should use.
Review the document itself
A PDF needs its own review. Check whether the text can be selected and read, whether headings and links are meaningful, and whether the reading order makes sense. A flattened image of a brochure is not the same as a structured document. An attractive visual layout alone does not establish that assistive technology can interpret it.
Ask the person preparing the file how its structure, meaningful images, tables and reading order will be checked. W3C’s WCAG2ICT overview explains how accessibility principles apply to documents and software, while making clear that its guidance is informative. A brief reading check is not an accessibility audit or certification.
The web page needs review too. Moving the same material into HTML does not automatically fix unclear headings, weak contrast or confusing navigation. Choose a format that supports the task, then test the actual implementation rather than relying on the file extension as a quality label.
Keep copies from contradicting each other
When the same offer appears in a page, a PDF and a sales handout, assign someone to maintain the shared facts. Record the current document, where it is linked, who owns it and what should trigger a review. A change to an included service may affect all three; a new photograph may affect only one.
For the fictional catering company, the register might say: “Service-area page is the current source; operations confirms changes; the brochure is checked whenever that area changes.” For the equipment supplier, it might instead identify a controlled specification document and require the product page to point to its current approved version. The source of truth should follow the business process, not a universal preference for one format.
Before replacing a file, ask what should happen to its existing address. Old links may still appear in emails, bookmarks or search results. Have the website owner or developer decide how visitors will reach the appropriate current information, and test that route. Do not assume that uploading a new file removes every older copy.
A download already saved on someone else’s device cannot be treated as updated when you change your website. Version details and a link back to the current source help the reader check what they have. Avoid putting rapidly changing facts into a widely circulated document unless there is a clear reason and a maintenance plan.
Test both routes before sharing
Start from the web page on a phone-sized screen. Find the essential answer, open the download and return to the relevant enquiry step. Then open the file directly, as if a colleague had forwarded it. Can you tell what it is, whether its details apply and where to confirm current information?
Check the actual PDF and the actual web page, including their links, text readability and any tables. Where printing is part of the task, inspect a print output too. Record what was tested and what still needs specialist review. This exercise identifies practical problems; it is not evidence that every device or assistive technology will work.
Bring that short format plan to your website project discussion with ZXP: the customer’s task, the current files, the facts that change and the person who approves them. It gives the project a clearer starting point than a request to put the existing brochure online unchanged.
Sources & references
- 01Publishing accessible documents
Government Digital Service and Central Digital and Data Office
- 02File types indexable by Google
Google Search Central
- 03WCAG2ICT Overview
W3C Web Accessibility Initiative
A perspective from the ZXP team.
Designed to help you ask better questions and take a clearer next step.



