AXSLIB-L Archives

Liberation Throough IT Accessibility (an EASI member list)

AXSLIB-L@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Arnold,Mike [NCR]" <[log in to unmask]>
Reply To:
Library Access -- http://www.rit.edu/~easi
Date:
Mon, 29 May 2000 10:13:54 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (130 lines)
I am comforted to see so many others involved in with these issues.  We
continue to search for opinions and/or experience with CD-ROM index
accessibility (post made 2000 05 10).  It seems Webpacs has its own set of
access issues.  Our non-library ORACLE experience is similar to other posts.

Audrey - Does the ALA have a formal position on accessibility?  Are there
any ALA procurement checklists, guidelines, requirements, standards, or
policies?  If so perhaps they can be easily referenced (ie website).  If
not, I suggest that an ALA position statement be drafted.  This way
individual library concerns (ie arguments with vendors, what to purchase,
etc) can be draped in the context of larger library policy.

Ron - You quoted some accessibility stats in your 2000 05 23 post (ie 80% to
95% degrade).  Could you please reference this?  Perhaps you have on hand a
list of vendors who were contacted, who responded, who is accessible etc.
This may provide Audrey (and the rest of us) some help in getting going.

Kelly - Thanks for raising this.  Accessibility work-arounds in java land
are not straight-forward.  On something so fundamental to inclusion, I think
it appropriate to demand accessibility in the original software design ( ie
not a work-around).  I had truly thought there would be many accessible
software catalog alternatives but Ron's post makes me think otherwise.  May
I respectfully suggest you make your own accessibility clause in your
procurement efforts.  You could request for example that the vendor
successfully demonstrate and/or guarantee accessibility parameters as
defined by Section 508.  Recently, I have seen a few examples where
accessibility was mentioned in the tendering documents.

Anyone had to make CD-ROM Indexes accessible?

Mike Arnold
e-mail/courriel: [log in to unmask] <mailto:[log in to unmask]>
Tel:    (819) 997-2903
Fax:    (819) 953-5995

-----Original Message-----
From:   Jenny Levine [mailto:[log in to unmask]]
Sent:   Tuesday, May 23, 2000 2:31 PM
To:     [log in to unmask]
Subject:        Re: Accessibility of Webpacs

        At my Library System, we talked to Innovative last year and
they actually tried to tell us that their frames-based out-of-the-box
interface was ADA-compliant.  They don't seem to grasp the scope of
the issue, so at the very least, we plan to add accesskey and tabindex
tags into the HTML we can control as the browsers begin to implement
HTML 4.  This will be a small step though, as we can't control 95% of
the results screens.
        I'd love to see ALA address this, but I'm not optimistic (about
impact on the vendors, not ALA!).  Until it comes down to dollars for
the vendors, they won't devote resources to this.  Especially for
catalogs like DRA's that are built on client-side Java.

Jenny Levine
[log in to unmask]
Internet Development Specialist
Suburban Library System
http://www.sls.lib.il.us/

> -----Original Message-----
> From: Audrey Gorman [mailto:[log in to unmask]]
> Sent: Tuesday, May 23, 2000 9:40 AM
> To: [log in to unmask]
> Subject: Re: Accessibility of Webpacs
>
> Does anyone know what's been done to approach vendors of these products?
> Has anyone raised this issue to anyone else at ALA (just so I know, since
> that's where I am!)?  What suggestions do people have for an approach to
> this issue?
>
> Audrey
> [log in to unmask]
>
> <<< [log in to unmask]  5/22 12:02p >>>
> Through some pretty intensive investigations we have not found any web
based
> library packages, and have contacted almost all of the library software
> vendors, with no response.
>
> Two years ago about 80% of the library systems were inaccessible, six
months
> ago it had climbed to 95%, primarily due to the issues you found with the
> Webpacs system.
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~
> Ron Stewart, Director
> Technology Access Program
> Information Services
> Oregon State University
> 109 Kidder Hall
> Corvallis, Oregon  97331
> Phone: 1.541.737.7307
> Fax:   1.541.737.2159
> E-mail: [log in to unmask]
> WWW: http://tap.orst.edu
>
> -----Original Message-----
> From: Kelly Ford [mailto:[log in to unmask]]
> Sent: Monday, May 22, 2000 9:00 AM
> To: [log in to unmask]
> Subject: Accessibility of Webpacs
>
> Hello Everyone,
>
> I was recently talking with officials at the Multnomah County Library in
> Portland, Oregon and learned that they are soon going too be using a
> graphical (web-based) library catalog system called Webpacs.  Apparently
it
> comes from the vendor of their existing catalog system.
>
> The person I was talking with gave me URLs of some other libraries that
are
> already using this system.  From my preliminary explorations it would
> appear that Webpacs is both a Java application and virtually inaccessible
> to screen readers.  Does anyone know if the accessibility option is
correct
> and if so anything about efforts to address it?
>
> Below are the examples the person I spoke with provided to me.
>
> Kelly

Check the URL below to register your institutions
Web page in EASI's Batteri-free Web contest.
http://www.rit.edu/~easi

Barrier-free Web Design Online Workshop
Workshop starts June 7, 2000
http://www.rit.edu/~easi/workshops/easiweb.htm

ATOM RSS1 RSS2