WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: PDFs that read one word per line

for

From: Karlen Communications
Date: Jan 26, 2010 7:18AM

This is an untagged PDF document so there may be several problems with the
source document that would cause the Virtual Tags to misread the content.

If I use Adobe acrobat to add Tags to the document, the Tags are pretty
accurate and reflect the corresponding content. JAWS reads the document just
fine.

Yes, a tagged PDF document does have structural elements that correspond
with the visual representation of the document. As this is an untagged PDF,
you may or may not get the results you are experiencing.

I offer consulting and training on creating accessible PDF documents from
several different applications including InDesign and dynamic database PDF
generation.

Many companies and organizations in Ontario do not know how to create
accessible PDF and are scrambling to figure it out for AODA. I, among other
companies, am trying to connect with companies and organizations who need
the training in how to make source documents and PDF documents accessible.

But the short answer to your question is that this is an untagged PDF
document.

Cheers, Karen



-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of E.J. Zufelt
Sent: January-26-10 8:29 AM
To: WebAIM Discussion List
Subject: [WebAIM] PDFs that read one word per line

Good morning,

Once in a while I run across a PDF that reads with JAWS one word per
line (example URL below). Even when saving the PDF as text the
content is saved one word per line. Can anyone tell me if there is a
common structural error that people are making with these documents,
and if so what it might be?

Example PDF document that reads and saves one word per line:
http://www.torontopubliclibrary.ca/pdfs/board/10jan18/12.pdf

Thanks,
Everett

Follow me on Twitter
http://twitter.com/ezufelt

View my LinkedIn Profile
http://www.linkedin.com/in/ezufelt