WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: automatic document testing

for

From: Ryan E. Benson
Date: Oct 25, 2011 8:45PM

Lucy,
The problem with making sure documents of this type is that there
isn't a simple fix, this is coming from a person who was a student and
worked in a large AT lab. The scanned articles are 2nd,3rd maybe 4th
generation copies. The built in OCR into Acrobat usually destroyed the
text. The disabled student's services at the university would require
that if a student needed an accessible version, bring their reading
into the office and the disabled student's services office hires
students who takes a hard or soft-copy version and run it through
ABBYY FineReader, then editing as need be. We started to work with the
library, who manages the e-reserves, I moved onto another job, so I
cannot say what the current status is. The university that I worked at
is equal size to Berkeley. We are too large to make each e-reserve
accessible, even though people are trying. We try to advocate the use
of HTML files whenever possible, for example, professors tend to grab
an article from Lexus Nexus and turn that into a PDF. While the HTML
version doesn't have headings, it is usually easier to use over a PDF.

--
Ryan E. Benson



On Mon, Oct 24, 2011 at 2:53 PM, Lucy Greco < <EMAIL REMOVED> > wrote:
> Hi:
>  This is meant to be steps used while moving forward. I have been asked to give a three or four step process to make sure readings for students are accessible basically it's a set of instructions I am to give to faculty to assure that the documents they put online e are accessible. These documents might be scanned articles  library readings exerts from books and so on. I have been told that it cannot be more than three or four steps so that it would not be intimidating and that talking about structure and tagging  is getting to technical. I am at a loss really because what I think I am being asked to say is that providing the text is all that is needed. And I really don't want to say that. One of the other things I was asked was if there was a way to flag a potential problem document on the way to it being uploaded. I am really frustrated on this process I know access is not extraordinarily hard but three or four steps is not enough ether.  At least I am not looking at making
>  forms in this project.  I have to have the documents be usable by a highly intelligent group. but I have also been told that the faculty don't want steps that will take more than a few minutes to do.
>
>
> Lucy Greco
> Assistive Technology Specialist
> Disabled Student's Program UC Berkeley
> (510) 643-7591
> http://attlc.berkeley.edu
> http://webaccess.berkeley.edu
>
>
> -----Original Message-----
> From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Duff Johnson
> Sent: Monday, October 24, 2011 11:30 AM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] automatic document testing
>
> Lucy,
>
> Can you say a little more about precisely who are the users who are trying to make these documents more accessible? Are they... the authors? The people running scanners? The web-content administrators? Who?
>
> Also, are we talking about one specific body of existing documents that just has to be fixed, or are we talking in more general terms about how to improve the process of creating new documents, or... what?
>
> Duff.
>
> On Oct 24, 2011, at 2:25 PM, Lucy Greco wrote:
>
>> Yes I actually gave these instructions but once again I was told to
>> complicated
>>
>> Lucy Greco
>>
>> -----Original Message-----
>> From: <EMAIL REMOVED>
>> [mailto: <EMAIL REMOVED> ] On Behalf Of Mark
>> Guisinger
>> Sent: Monday, October 24, 2011 11:21 AM
>> To: WebAIM Discussion List
>> Subject: Re: [WebAIM] automatic document testing
>>
>> Lucy,
>> Did you try the built in accessibility checking tools in Adobe Acrobat
>> Pro 9 and above?  I find them easy to use and it does provide some
>> suggestions on how to correct the issues.  You will find them under the Advanced menu.
>>
>> MarkG
>>
>>
>>
>> ----- Original Message ----
>> From: Lucy Greco < <EMAIL REMOVED> >
>> To: "WebAIM Discussion List ( <EMAIL REMOVED> )"
>> < <EMAIL REMOVED> >
>> Sent: Mon, October 24, 2011 2:04:12 PM
>> Subject: [WebAIM] automatic document testing
>>
>> Hello:
>> I have been given the task of helping users provide accessible
>> documents. The more I tell my director that the task of providing
>> accessible documents is not an easy three step  process the more he
>> wants a simple  way to check the accessibility of documents and quick fix. Does anyone have a tool that will
>> check PDF files and indicate if   the document is accessible. And if it is not
>> accessible what to fix in it. I tried the web aim instructions on how
>> to create accessible files but was told they were too complicated.
>> Someone please help me find a way to give a simple answer to a hard
>> problem thanks Lucy
>
>