WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Thoughts on PDF Accessibility

for

From: Ryan E. Benson
Date: Sep 27, 2019 9:01AM

I was the primary author of the previous version of the HHS checklist, and
an editor of the current one. We left some of the more arcane parts of the
ISO Standard off, and tweaked the language of others. All items in our
checklist must be tested against, none are optional. The answers are Yes
(as in yes, the PDF meets the standard), No (as in No the PDF doesn't
meeting the standard), or N/A (as in the PDF does not contain that
specific element. There's 7 items on our list for tables, if you know that
the PDF you are reviewing, does not contain tables, you can put n/a for
all 7 and move on instead of testing those individually. I tell people to
review the checklist before starting. While I have an advantage of being
the author, by reviewing the checklist before starting, it allows you to
effectively test for multiple things at once. For example, checking tag
order, checking if there are headings, and making sure the headings flow
correctly - like you would do with HTML. As you gain experience, things
like lists to that sweep. Now you're testing for 10-15 things at once.

--
Ryan E. Benson


On Fri, Sep 27, 2019 at 9:31 AM Ramshif Richu < <EMAIL REMOVED> > wrote:

> Thanks for the reply. But I am trying to understand in a testing
> perspective, I assume there would be certain things which we shouldn't test
> or avoid when testing PDF Accessibility, I would like to know what are
> those areas, kind of limitations and or things that should be avoided when
> testing PDF Accessibility.
>
> Thanks.
>
> On Fri, 27 Sep 2019, 6:41 pm , < <EMAIL REMOVED> > wrote:
>
> > For starters, PDF accessibility is defined by the ISO 14289-1 (PDF/UA-1)
> > standards so a review of them would be essential.
> >
> > As yet, there isn't an official how-to guide from the PDF/UA committee
> (or
> > any other authoritative entity) on the steps to make a PDF accessible or
> > how
> > to check a PDF for compliance or what to check.
> >
> > However, the PDF Association released a syntax guide that can be helpful.
> > It's designed for programmers who write software that creates PDFs, not
> for
> > content creators and remediators, but if you glean through the
> programming
> > blah blah you'll find quite a bit of useful information on how a
> complaint
> > PDF should be tagged.
> >
> > Download a copy from the PDF Association's website,
> > https://www.pdfa.org/resource/tagged-pdf-best-practice-guide-syntax/
> >
> > We have a 12-point checklist for content creators and remediators to
> check
> > the major accessibility points of PDFs at
> > https://www.pubcom.com/books/bevi_cheatsheet/cheatsheet-accessdocs.shtml
> > There are many more nuances involved, but these are the big ones.
> >
> > HHS has a good checklist at
> >
> >
> https://www.hhs.gov/web/section-508/making-files-accessible/checklist/pdf/in
> > dex.html
> > <
> https://www.hhs.gov/web/section-508/making-files-accessible/checklist/pdf/index.html
> >
> >
> > --Bevi Chagnon
> > (US delegate to the PDF/UA ISO standards committee and member of the PDF
> > Association)
> >
> > - - -
> > Bevi Chagnon, founder/CEO | <EMAIL REMOVED>
> > - - -
> > PubCom: Technologists for Accessible Design + Publishing
> > consulting . training . development . design . sec. 508 services
> > Upcoming classes at www.PubCom.com/classes
> > - - -
> > Latest blog-newsletter - Accessibility Tips at www.PubCom.com/blog
> >
> >