WebAIM - Web Accessibility In Mind

E-mail List Archives

Testing PDfs for accessiblilty

for

From: vennila murugesan
Date: Sep 12, 2017 9:01PM

Hi, 
I'm with the City of Ottawa and we use CommonLook PDF GlobalAccess as well for remediating. But a free alternative for simply validating and obtaining a report would be CommonLook PDF Validator.

|
|
|
| | |

|

|
|
| |
CommonLook PDF Validator - CommonLook by NetCentric Technologies
| |

|

|


Vennila Murugesan


On Wednesday, July 19, 2017 7:43 PM, Philip Kiff < <EMAIL REMOVED> > wrote:


> My question is: what would you recommend as an alternative to Acorbat Pro for the various aspects of accessibility testing and remediation, in particular the tags structures?

My impression is that there are really only two tools that are worth looking at for doing advanced PDF remediation:

CommonLook "PDF GlobalAccess"
http://commonlook.com/accessibility-software/commonlook-pdf-globalaccess/

and

axesPDF "QuickFix"
https://www.axes4.com/axespdf-quickfix-overview.html

Neither of these pieces of software replaces Adobe Acrobat DC. CommonLook is a plugin for Acrobat. AxesPDF is standalone software but like CommonLook, it only supplements and augments what you can do with Acobrat Pro. There are essential editing functions for PDF remediation that are only available in Acrobat Pro DC. And if you are not using DC, then your cheapest first step would be to upgrade to DC. And upgrade to Word 365 or 2016. And the latest version of InDesign. Those upgrades alone could save you countless hours.

I have extensive experience with axesPDF but limited experience with CommonLook. I keep meaning to find the time to do a proper comparison and review of the two tools, but never seem to find that time - oh, by the way, each of them will run you around $1000 USD (or more).

Allayne Woodford wrote:

> Commonlook doesn't auto-generate tags, you would still need to do that in Acrobat for a 'No tags available' PDF but it gives you something to work with. Using just Acrobat Pro for PDF remediation, particularly when you don't have the source document, is not something I'd want to go back to.

My experience with axesPDF is similar to what Allayne writes about
CommonLook: I would never, ever want go back to editing PDFs just with
Acrobat.

> Can anyone recommend a tool that autogenerates clean tag structures that conform to HTML5-like semantics? Is there a better way to generate PDFs from Word, Powerpoint, etc. than the usual Save as PDF options in those products?

This is a multi-prong question.

First, neither axesPDF nor (as Alan notes) CommonLook will autogenerate tags in a separate process from what Acrobat does.

Second, yes, there are better ways to generate PDFs from Word and InDesign in particular. The better way is to make better source files! If you follow all the recommended techniques from Microsoft and Adobe for creating accessible files in those programs along with some additional advice from this list and elsewhere, then you should be able to generate PDFs from those pieces of software that don't require an inordinate amount of retagging or remediation. There will be exceptions for particular structures of course, but those two programs have come a long way in the last 5-10 years and if files from recent versions of those programs are generating tag soup, then there are probably significant problems with the way the source files were created.

Both CommonLook and axesPDF offer Word plugins that claim to be able to give Word editors the possibility of generating PDF/UA compliant PDFs directly from Word. They may prove useful for files that require ongoing updates and that require regular conversion of substantially the same file to PDF.

Regarding the autotag function in Acrobat DC, it seems to me that different PDF editors have different approaches about when and where to use it most efficiently. I personally don't use it on most files that already have a tag structure in place - even if that tag structure is flawed. I find it faster to fix the tag structure in most cases, rather than starting fresh. Or to edit the source Office/InDesign file and then recreate the PDF before editing it further. But as with most things related to PDF remediation, it depends on the content.

Lastly, I've seen multiple references on this list to HTML 5 and connecting it to PDFs. I would keep those issues separate. HTML 5 elements don't always correspond to PDF tags. There is a loose relationship, and some patterns and tags are similar, but PDF structure is its own little world with its set of rules and sometimes bizarre quirks.

Phil.

On 2017-07-17 7:31 PM, Allayne Woodford wrote:
> Hi Alan,
>
> I'm a frequent user and fan of Commonlook. Granted, it's an Acrobat plug-in and is quite costly but for the volume of work I have I think it's well worth it, and I was skeptical at first. It allows for super quick markup of tables, one-step removal of empty tags, removal of role maps from InDesign styles (love this feature!) an undo feature, and the ability to tag something once then tag all the same text styles in one go. This is great for headings.
>
> Commonlook doesn't auto-generate tags, you would still need to do that in Acrobat for a 'No tags available' PDF but it gives you something to work with. Using just Acrobat Pro for PDF remediation, particularly when you don't have the source document, is not something I'd want to go back to.
>
> Ally Woodford
> Accessibility Services Manager
> Media Access Australia
[snip]