What the reader needs

A designed PDF can be useful for meetings and offline review, but it is not always the easiest format for a quick mobile question. Put the key explanation, assumptions and next step on an accessible web page as well. Tell readers what the download contains and identify its format before they open it. Avoid using a giant image of each PDF page as the only web version; that may preserve appearance while making the text harder to use.

How to review it

Review the web page and document together so important qualifications do not appear in only one format. Check document reading order, selectable text, links and visible headings through an appropriate PDF accessibility workflow. Test the download on a phone and confirm it opens without unintended access restrictions. If a document requires specialist remediation, record that work rather than declaring it accessible based only on visual inspection. Give readers a contact route for reporting a format barrier.

Imagine this

Hypothetical example

A company publishes an A4 growth presentation and a web summary containing the same assumptions and key table. A mobile reader can understand the proposal without downloading first, while someone preparing for a meeting can save the designed document for later review.

Make it practical.

Use this checklist as you read. Checks are not stored.

References & further reading

Further reading: W3C WAI: Writing for web accessibility ↗

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.