WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: automatic document testing

for

From: John E Brandt
Date: Oct 26, 2011 8:18PM

In reading this later comment, these thoughts comes to mind....

If you are dealing with resistant faculty you might encourage them to think
of their digital documents as being similar to their published material.
They would never submit an article to a refereed journal without making sure
all of the headings, titles, running heads, graphics, and indices were
perfect. Why would they then publish their work on-line without the same
level of care?

For students, it's a tougher sell. You might be able to use a similar
analogy noting that what they put on-line is like what they would put in
print, it's permanent and they will be judged accordingly. But students
might also respond to the egalitarian and moral aspects of accessibility.

~j

John E. Brandt
www.jebswebs.com
<EMAIL REMOVED>
207-622-7937
Augusta, Maine, USA


-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of Lucy Greco
Sent: Monday, October 24, 2011 2:54 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] automatic document testing

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