When we first argued our case with our database vendor, we went
far beyond singling out visually-challenged users.  For example, we
included an actual problem documented with a woman who has Parkinson's
and can't use a mouse, as well as users with repetitive strain injuries,
and others.  We tried to show them that this affects a larger percentage
of the population than they think, and that as government-funded
institutions, library services MUST be accessible to all patrons.
        Unfortunately, as I noted earlier, the response was less than
enthusiastic, and our Webpac isn't half bad compared to those that make
extensive use of Java and Javascript.  At 75 distinct libraries, we're
Innovative's biggest consortial customer so this is truly
disappointing, but it shows how little clout libraries have against
their vendors.  We migrated from GEAC last year, which was a big
deal (believe me, we're still putting some of the puzzle pieces back
together).  So we can't just up and leave them if they don't fix this
right away and I'm sure they realize this.
        That is why I say it truly will come down to dollars, so any
help ALA can provide (even just guidelines) would be quite welcome by
us.  Based on Section 508, I believe that any library that has ever
gotten or ever will get LSTA funding or grant money MUST make its
services fully accessible.  Maybe ALA could put this in writing?

Jenny Levine
Suburban Library System
[log in to unmask]

Julia wrote:
>
> Jenny,
> I agree with your accessment that the issue of accessibility comes down to
> dollars.  I perhaps am a little more hopeful as the baby boomers get older
> and need these features, or as in the case of cell phone, want them and
> view them as easier.  Sometimes I think our mistake is to try to sell
> "accessible" as only good for people who need special interfaces, the
> accessible interfaces I've seen in any industry make life easier for
> everybody.
>
> Julia Allegrini, Library Supervisor
> Northern Kentucky Talking Book Library
> 502 Scott Boulevard
> Covington KY41071
>
> ----------
> >         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/
> >
>
> Barrier-free Web Design Online Workshop
> Workshop starts June 7, 2000
> http://www.rit.edu/~easi/workshops/easiweb.htm

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