Apologies for cross-posting...
Hello!
I'm trying to put together a standardized accessibility vetting procedure
of sorts for all of our 3rd party database or e-resource subscriptions. So
far we're thinking...
-Evaluate the interface on our end (using WAVE tool or similar)
-Compile results/problems
-Communicate problems/non-compliance to vendor
-Track vendor response and changes
I've also started requesting VPATs along with the license agreements.
I'd love to hear any information or experiences related to similar
procedures at your own schools for evaluating e-resource purchases in
regard to accessibility.
I hate to think of many different schools replicating each other's work
considering we generally deal with such a large number of shared vendors
and platforms. The closest thing I could find to a compiled list was on
the ASCLA wiki<http://ascla.ala.org/toolkit/index.php?title=Accessibility_to_Library_Databases_and_Other_Online_Library_Resources_for_People_with_Disabilities>.
Any other suggestions?
Thanks so much!
Erin
Erin Finnerty
Electronic Resources Librarian
Temple University
Samuel L. Paley Library
1210 Polett Walk | Philadelphia, PA 19122
(t) 215-204-3275 | (f) 215-204-8550
erinf_at_temple.edu
_______________________________________________
ACQNET-L mailing list
ACQNET-L_at_lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/acqnet-l
Received on Wed Apr 03 2013 - 12:55:24 EDT