PDF accessibility and browser plug-ins

11th August 2017 | by Ted Page

Overview

Organisations that invest in making their online PDFs accessible should be aware that much of their good work could be undone by the way their websites are configured. However, there is an easy solution.

The problem

The problem is that many websites are configured so that PDFs that they host are opened by default in browser plug-ins. An article on the Adobe website, Configure browser to use the Adobe PDF plug-in to open online PDF files, lists a number of reasons why such a situation may not be ideal. These include:

  • Parts of a PDF don’t display
  • Poor performance or image quality
  • Large file sizes when printing to PDF
  • 3D models don’t render
  • Embedded SWF files don’t play 

Accessibility

Conspicuous by its absence from this list is accessibility. To put it mildly, the accessibility of PDFs rendered in browser plug-ins is awful, for almost every assistive technology in every browser. In short, all the care and effort that you put into ensuring that your PDFs are authored correctly may be completely lost on your readers. 

Options for end-user customisation

The Adobe article explains how individuals can configure their browsers to avoid this problem. For example, in Firefox on Windows:

  1. Choose Firefox, Options, Applications
  2. In the Content Type area, select Portable Document Format (PDF)
  3. In the Actions column the default is Preview in Firefox. Change this to Use Adobe Acrobat DC
Firefox Options screenshot
Figure 1: configuring Firefox on Windows 10

The article also lists similar instructions for Chrome and Safari on Windows and Mac, as well as for Firefox on Mac. 

Once done, your online PDFs will open in Adobe Reader or Acrobat Professional and, if authored correctly, will be fully accessible to screen readers, magnifiers, literacy software solutions and more.  In addition, important accessibility features such as text/background colour customisation and text reflow will also be available (they aren’t in any browser plug-in).

Fixing the problem at source

But of course, the above solution depends on the end user knowing that there is a problem and how to fix it. In many cases this will not be a safe assumption. Organisations that care about the accessibility of their PDFs should therefore consider addressing the problem at source, by configuring their websites so that PDFs open by default in Acrobat or Adobe Reader.

Fortunately, as stated earlier, the solution is simple. If you work for a large organisation your IT department will know of several ways of forcing PDFs to open in a dedicated PDF viewer, rather than in a browser plug-in. Doing so should be just a few minutes’ work, after which all PDFs on the site will open as desired. 

For those who manage their own sites, the following article by Sybren A. Stüvel, Offering PDFs that download, explains how to fix the problem for a range of different servers.

We have advocated this kind of solution in our Accessible PDFs from Acrobat training courses for the past 10 years, and will continue to do so for as long as the problem persists.