17
edits
Changes
m
Chicago [https://cpl.org/aboutthelibrary/usingthelibrary/accessibility/ Cleveland Public Library's Web Accessibility Policy] [https://chipublibkcls.bibliocommons.com/infoorg/accessibility/ Bibliocommons policyKing County (Washington) Library System's Accessibility Policy] and their [https://www.chipublibnypl.org/library-policies/websiteweb-accessibilitymobile-policy/ general website accessibility policiesNYPL Web Accessibility Policy].
added wright state link, although it's pub'd from 2001, still useful
This page is intended to collect resources related to accessibility as and was created following a result discussion from the code4lib 2018 breakout discussions.
==Accessibility Resources==
===From C4L18C4L 18===
[https://osf.io/um7sn/ Critical Mass Accessibility] - Lightning talk given by Kate Deibel at C4L 2018; A call to create a library accessibility community.
===Other resources===
[https://github.com/mgifford/a11y-courses a11y courses] - comprehensive list of trainings and courses on web accessibility
[https://github.com/brunopulis/awesome-a11y Awesome-A11Y ] - pretty comprehensive list of specifications, guides, articles, and talks.
[http://diagramcenter.org/standards-and-practices/accessible-image-sample-book.html The Accessible Image Sample Book by DIAGRAM] - Very instructive guide to make accessible images (charts, maps, diagrams) in an educational contexts. It is also available on [https://github.com/benetech/AccessibleImageSampleBook Github].
[https://pressbooks.library.ryerson.ca/pwaa/ Professional Web Accessibility Auditing Made Easy] - by Digital Education Strategies, The Chang School. A liberally CC-licensed e-book on how to assess a website for accessibility
===Accessibility and Digital Collections===
[https://www.museumsandtheweb.com/mw2001/papers/anable/anable.html Wright State's University's Guide for writing alt-text for historical art] - also could be applicable for historical images and photographs
===Assessing Third Party Vendors for Accessibility===
Before purchasing electronic resources, you should verify if they are accessible and not take the vendor's word (or VPAT).
First, what questions should you ask a prospective vendor?
[https://depts.washington.edu/uwitats/checklist/ The University of Washington] and [https://kent.qualtrics.com/jfe/form/SV_bg9QMVI7bqyvPvL Kent State University (KSU)] require prospective vendors to complete a questionnaire. ''The questions on KSU's form can also be viewed as a [https://www.kent.edu/sites/default/files/file/ICT%20vendor%20form%20-%20question%20preview.pdf PDF]''
You'll also want to conduct verify the responses by manual testing based on those responses.
===Web Accessibility Policies===
Some public libraries (Sacramento, Chicago) are officially organized and structured as a government entity underneath and adopt policies of their general cityrespective municipality.
Others (NYPL) that are self -managed and adopt their own web accessibility policies.
For example: Chicago Public Library's [https://chipublib.bibliocommons.com/info/accessibility/ Bibliocommons policy] and their [https://www.nyplchipublib.org/library-policies/webwebsite-mobileaccessibility-policy/ general website accessibility NYPL Web Accessibility Policypolicies].
===Accessibility Complaints filed against libraries===
''(This list is not exhaustiveand does not include any academic institutions whose libraries may or may not have been included in the complaint)''
[https://nfb.org/national-federation-blind-settles-complaint-against-sacramento-public-library National Federation of the Blind vs. Sacramento Public Library], 2012.
