WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Sample Inaccessible PDFs

for

From: Peter Shikli
Date: Apr 28, 2017 6:44PM

Krista,

You're indeed right about OCR being a big job and sometimes the first
step in making PDFs accessible. We are lucky in that the inmates, yes
I'm training accessibility to prison inmates, already have an
affordable, nearby scanning and OCR operation that I can turn to for
that. Unfortunately, OCR doesn't introduce the tags I'd like my
students to have to dig through.

Sincerely,
Peter Shikli
Web4VI
A Division of Bizware Online Applications, Inc.
29030 SW Town Center Loop East
Suite 202-187
Wilsonville, OR 97070
503-570-6831 - <EMAIL REMOVED>
Cell: 949-677-3705
FAX: 213-337-7029
www.web4vi.com
Prison inmates helping the visually impaired


Krista Greear wrote on 4/28/2017 5:27 PM:
>
> I didn't understand you were looking for a specific kind of
> inaccessible PDFs.
>
> I shared a series of image-based PDFs, realistic documents that many
> of us encounter in higher ed. WebAIM's webpage assumes you are
> starting with a text-based PDF. This could be setting a false
> expectation. Optical Character Recognition (OCR) can be a large part
> of the remediation process and is certainly a necessary first step in
> remediating image-based PDFs. After that, tags, headings, tables, etc.
> can be addressed.
>
> What you could do is use the files I gave you, have your student use
> Adobe Acrobat Pro's built-in OCR engine to make a text-based file,
> then complete the exercises on WebAIM's webpage. Or use an OCR engine
> like ABBYY FineReader or OmniPage to turn the image PDF into a
> text-based one, then complete the exercises.
>
> Sounds like a lot of work? You are completely right. Document
> remediation is not for the faint of heart.
>
> I would strongly argue that teaching someone about OCR is imperative.
> While it may not be the bulkiest step in the process, OCR can become
> one of the most time consuming parts. My employee spent 3 hours OCRing
> the attached 32 page PDF, then had to pass it off to another team
> member to remediate the headings, tables, tags, etc.
>
> Take luck!
>
> *KRISTA GREEAR*
>
> Assistant Director
>
> Disability Resources for Students
>
> 011 Mary Gates Hall
>
> Box 352808
> Seattle, WA 98195-2808
>
> Direct: 206.221.4136 / Main: 206.543.8924
>
> <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >/ http://disability.uw.edu
> <http://disability.uw.edu/>;__
>
> *From:*Peter Shikli [mailto: <EMAIL REMOVED> ]
> *Sent:* Friday, April 28, 2017 5:04 PM
> *To:* Krista Greear < <EMAIL REMOVED> >; WebAIM Discussion List
> < <EMAIL REMOVED> >
> *Subject:* Re: [WebAIM] Sample Inaccessible PDFs
>
> Krista,
> Whereas one of your dropbox files was a true PDF with tag markup, the
> rest were images only inside a PDF container -- unless I missed
> something. With the images-only files, I can't ask my students to go
> through tutorials like WebAIM's
> <http://webaim.org/techniques/acrobat/acrobat>; as exercises to check
> and fix accessibility. That's the kind of practice they need.
> Cheers,
> Peter
>
> Krista Greear wrote on 4/28/2017 9:20 AM:
>
> I keep a collection just for this purpose! See the Dropbox link
> with 18 files
> <https://www.dropbox.com/s/unu8vgsm2xp88da/inaccessible%20PDF%20examples.zip?dl=0>.
>
>
> KRISTA GREEAR
>
> Assistant Director
>
> Disability Resources for Students
>
> 011 Mary Gates Hall
>
> Box 352808
>
> Seattle, WA 98195-2808
>
> Direct: 206.221.4136 / Main: 206.543.8924
>
> <EMAIL REMOVED> / <mailto: <EMAIL REMOVED> /> http://disability.uw.edu
> <http://disability.uw.edu>;
>
>