On Fri, May 22, 2009 at 1:34 PM, Walker, David <dwalker_at_calstate.edu> wrote:
>But it seems that many, if not most, 'next-generation' catalog systems implement Javascript without regard to accessibility considerations.
There's a lot of truth to that, but it should be noted that the
"last-generation" systems were also accessibility disasters, just in
different ways. For Library for Libraries—which *is* Javascript—we
spent a lot of effort to create an accessible, non-JavaScript version.
The absurdity of it was that LTFL plugs into your current catalog, and
they're often not accessible enough to get a blind person to the point
that they'd even know whether LTFL was accessible or not.
Tim
Received on Fri May 22 2009 - 15:04:01 EDT