COI Toolkit Beta


4
Content Elements

How to provide images that are the correct format and that communicate your intended message quickly, clearly and with good accessibility.

How to avoid misusing pop-up windows and pop-outs (‘tool tip’ type elements).

Basic pointers on using and producing accessible PDFs


4c When and how to use PDFs


Ideally provide documents in accessible HTML form unless totally unpractical to do so:

  • The most appropriate uses of PDF are:
    • When the PDF is in addition to HTML
    • Long documents that are intended for printing – for which there is a HTML summary/abstract
    • Legally restricted documents
    • Foreign language publications (particularly if they use an alternative character set)
    • Claim and application forms for downloading and printing
    • Documents designed specifically for print, such as brochures, which require fine control over printing (although you could use print CSS on HTML for many print-friendly versions)

If using PDFs:

  • Create an HTML summary/abstract whenever possible
  • Use a table of contents for long PDF documents – this provides appropriate overview of the contents and navigation directly to different main sections
  • Add appropriate metadata / document properties
  • Warn in (or next to) the link that the document will be a PDF and state its size in Kb
  • Provide a link to download Adobe Reader
  • Ensure the source document and PDF has been made accessible
    • Add structure and alt text in the source document creation application (for example, use headings and add alternative text from within Microsoft Word)
    • Test and fix tags using Acrobat Professional
    • Save as PDF – do not use ‘print as PDF’ to generate the PDF or structure is lost

Notes and discussion points

What is the issue with PDFs?
The main issue used to be (and to an extent still is) to do with accessibility. Although PDFs can now be made accessible, it tends to be harder work than producing accessible HTML. If there is the option to do so, use HTML instead

PDFs can break the usual flow of browsing by changing some of the available controls – but this is becoming less of an issue

If the PDFs are well constructed, there should be little issue with providing PDFs

What about when there are lots of old PDFs?
It may be not practical to make HTML summaries of old or legacy PDFs, or make these accessible. If this is the case:

  • Prioritise very important and/or high traffic PDFs for making accessible
  • Ensure all new PDFs are provided with HTML summaries and are accessible

More information about accessibility and PDFs?

  • Visit the Webaim training materials for PDF – for PDF conversion, structuring appropriate documents using Microsoft Word (and other word processors) and a whole host of other accessibility tips
  • Visit the Adobe access site for step-by-step information – for step-by-steps guides on creating accessible PDFs

watch video about converting a Microsoft Word document 2003 and 2007 into a PDF

Converting a Microsoft Word document 2003 and 2007 into a PDF
Video showing some simple steps to help make accessible PDFs from Microsoft word 2003 and 2007.


 
Provide a link to the PDF reader a screenshot of this page in PDF format for printing – the visual form has changed to better match the needs of the printed page (the guidance is first followed by the examples rather than side by side) Summary diagram of the key steps involved in providing effective PDFs online (see the bullet points in the main text for the summary) Screenshot of using Microsoft Word 2007 to give structure to a source document using headings and styles Screenshot of using Microsoft Word 2007 to add alternative text to images Screenshot of using Microsoft Word 2007 to add metadata to a document

© Crown Copyright 2004-2010