HTML generally adapts more readily to screen size and text enlargement. It suits instructions, frequently updated terms and information people need to find quickly on a phone. PDF can be useful when fixed pages, downloading or a specific document version serve a clear purpose.
Moving text to HTML does not automatically make it accessible. The web page still needs appropriate structure, contrast and working interactions.
A course publishes eligibility rules, an application deadline and required evidence. Putting everything in a PDF can look tidy. A reader opening it on a bus may first have to download the file, zoom, pan sideways and search for one date.
A web page can organise the same information under clear headings with a direct route to the application. The editor updates one source when a date changes. A PDF can still offer a saved edition of that term’s rules, labelled with a version and linked back to current information.
This is an editorial format choice. Start with what people are trying to do, not the export command available in your word processor. A formal attachment with fixed pagination can justify PDF. A six-sentence instruction rarely needs a separate document simply because the organisation has an attractive footer template.
| Reader’s need | A reasonable starting point |
|---|---|
| Read a short instruction on a phone | Publish the instruction on the web page. |
| Keep a specific version of a report | Offer an accessible PDF and make key findings easy to find on the web. |
| Complete an application | Consider an accessible web form before choosing a PDF form. |
Decide which version is authoritative and who updates the other. Include version dates and descriptive links. Conflicting application deadlines create a new barrier even when both formats are technically sound.
An HTML version does not automatically exempt a PDF you also publish from applicable requirements. Assess the format choice and the legal scope separately.
Equivalent information involves more than identical body text. Check table values, image explanations, link destinations, contact details and attachments wherever readers need them. A full set of terms in PDF and a short HTML summary are not equivalent alternatives.
Define an update routine. Whoever changes the master needs to know which versions must follow. A dated report may need a clearly labelled correction rather than a silent replacement. An ongoing instruction may retain its web address while the information changes. The appropriate approach depends on the document’s purpose, rather than a universal rule that one format always wins.
Sources
Examples are our own unless stated otherwise. These guides distinguish legal requirements, standards and practical advice. Passing an automated check is not a complete assessment of document accessibility.