WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: PDF Accessibility Checker (PAC) vs. AdobeAcrobatProXI full check

for

From: John E Brandt
Date: Apr 3, 2014 2:25PM

Ditto to all the above...but the most important statement is this one made
by Bevi.

It almost ALWAYS comes down to...

***How well the document's author understands accessibility and how to
create an accessible document***

PDF's are not to blame...the people who create them are. And this means we
need to train people to do a better job of creating digital documents.

~j

John E. Brandt
jebswebs: accessible and universal web design,
development and consultation
<EMAIL REMOVED>
207-622-7937
Augusta, Maine, USA

@jebswebs

-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of Chagnon | PubCom
Sent: Thursday, April 03, 2014 2:38 PM
To: 'WebAIM Discussion List'
Subject: Re: [WebAIM] PDF Accessibility Checker (PAC) vs. Adobe Acrobat Pro
XI full check

Chiming in with agreement with Monir ElRayes and Lucia Greco re:
accessibility of PDFs.

They can be just as accessible as any other form of information, but the key
is having users trained in how to make accessible Word documents, InDesign
layout files, and PDFs. And, of course, having the right software tools to
do this.

PDFs are central for any organization or enterprise, so they are not going
to go away or be replaced by HTML websites. They have a defined purpose of
"locking down" a document in a particular state at a particular point in
time. A snapshot, so to speak. That's nearly impossible to do with a
webpage, which in theory is a living document.

Todd, re: your findings that different AT report or voice items differently
could be due to two factors:

1) The version of the software that created the source document. Example,
Word 2013 does a better job of converting to accessible tags that Word 2017,
and InDesign CC does a better job than InDesign CS 5.5. Each new version of
these programs incorporates newer standards and more accurate tags.

2) The version of the Acrobat conversation engine/module used to create the
PDF from the source document. Acrobat XI does a better job than Acrobat X
and we're hoping that the future Acrobat XII does an even better job.

So many variables affect how accessible a document will be:
- The software that creates the source document; for example, Word is better
than WordPerfect.
- The version of that software; newer is usually better.
- The PDF conversion engine; newer versions are better.
- How well the document's author understands accessibility and how to create
an accessible document.
- Knowledge of and tools used by those who remediate the PDFs.
- The AT used by the end user; newer versions are better.
- How well the AT user can control or customize their AT for their needs.

That's a lot of variables!

-Bevi Chagnon
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - -
www.PubCom.com - Trainers, Consultants, Designers, Developers.
Print, Web, Acrobat, XML, eBooks, and U.S. Federal Section 508
Accessibility.
New Sec. 508 Workshop & EPUBs Tour in 2014 - www.Workshop.Pubcom.com

messages to <EMAIL REMOVED>