WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: PDF vs. HTML

for

From: julian.rickards
Date: Aug 5, 2004 2:33AM

Part of my job function is to create accessible PDFs which according to the
Acrobat Accessibility Checker, mine are fine. I also incorporate checking
that does cannot be automatically checked such as "don't depend on colour".
Nevertheless, the accessibility of an accessible PDF is no where near the
same degree of accessibility of an accessible web page. Tables do not have
header cells (using a PDF generated from Word) and even if you do mark up
the top row of a table as a series of header cells (using PDF tags after the
PDF has been generated), neither Read Out Loud, nor JAWS are able to
associate the cells in the table with the header cells which is a feature
that JAWS can provide if HTML tables are marked up properly. In JAWS using
an HTML page, you can skip from heading to heading but neither JAWS nor Read
Out Loud understand headings in a PDF. In JAWS using an HTML page, you are
told the number of items in a list but this is not available to readers of
PDFs.

Despite the efforts that Adobe has been applying to making PDFs accessible,
I don't "see" the results. My experience with JAWS is limited - I am a
sighted person and used JAWS 5.0 (trial) for a while to try to experience
what JAWS users experience.

Because of my experience with "accessible" PDFs and accessible HTML, one of
my job functions will be changing over the next couple of months to reduce
the use of PDFs and to publicize our new publications in HTML format (with a
PDF as an alternate, not guaranteed to be accessible, printable format).

Jules

-----------------------------------------------
Julian Rickards
A/Digitial Publications Distribution Coordinator
Publication Services Section,
Ministry of Northern Development and Mines,
Vox: 705-670-5608 / Fax: 705-670-5960