Difference between revisions of "Accessibility to Library Databases and Other Online Library Resources for People with Disabilities"

From ASCLA Wiki
Jump to: navigation, search
m
Line 32: Line 32:
 
http://www5.oclc.org/downloads/accessibility/508template-fs.html  
 
http://www5.oclc.org/downloads/accessibility/508template-fs.html  
  
* '''Proquest''' (12/08)
+
* '''Proquest''' (12/2008)
 
http://support.proquest.com/al/12/1/article.asp?aid=2789&bt=4n  Says “Compliant with Section 508 of the Americans with Disabilities Act.” Section 508 is part of the Rehabilitation Act of 1973, not the Americans with Disabilities Act, so I don’t know what to think about this statement.  
 
http://support.proquest.com/al/12/1/article.asp?aid=2789&bt=4n  Says “Compliant with Section 508 of the Americans with Disabilities Act.” Section 508 is part of the Rehabilitation Act of 1973, not the Americans with Disabilities Act, so I don’t know what to think about this statement.  
 
Also says “There are…limitations on usability that are imposed by the format of the primary source materials contained in our products - whether they be a periodical, dissertation or other type of content. The format of the materials we receive may prevent some impaired users from being able to use certain of the works where the format is incompatible with the person’s disability and/or the ability of third party applications such as screen readers to render a useable version of the work.  For example, while a PDF rendered from a work submitted in text format may allow the Adobe Reader screen reader functionality, a PDF rendered from a work submitted in hard copy form is rendered as an image of the hard copy work (also known as a Scanned Image PDF) and therefore is not compatible with the screen reader functionality. Again, this is a consequence of the format of the works provided to UMI for inclusion within our products.”
 
Also says “There are…limitations on usability that are imposed by the format of the primary source materials contained in our products - whether they be a periodical, dissertation or other type of content. The format of the materials we receive may prevent some impaired users from being able to use certain of the works where the format is incompatible with the person’s disability and/or the ability of third party applications such as screen readers to render a useable version of the work.  For example, while a PDF rendered from a work submitted in text format may allow the Adobe Reader screen reader functionality, a PDF rendered from a work submitted in hard copy form is rendered as an image of the hard copy work (also known as a Scanned Image PDF) and therefore is not compatible with the screen reader functionality. Again, this is a consequence of the format of the works provided to UMI for inclusion within our products.”
 
http://www.proquest.com/en-US/site/accessibility.shtml  
 
http://www.proquest.com/en-US/site/accessibility.shtml  
  
* '''WilsonWeb''' (12/08)
+
* '''WilsonWeb''' (12/2008)
 
http://www.hwwilson.com/documentation/WilsonWeb/rehabilitation_act_compliance.htm
 
http://www.hwwilson.com/documentation/WilsonWeb/rehabilitation_act_compliance.htm
 
During the 2008 Midwinter ALA ACRL-ANSS meeting, representatives said they communicated with at least one adaptive technology vendor. They did not say if they had done user testing with people who use any adaptive technologies.  
 
During the 2008 Midwinter ALA ACRL-ANSS meeting, representatives said they communicated with at least one adaptive technology vendor. They did not say if they had done user testing with people who use any adaptive technologies.  
Line 81: Line 81:
 
* Is the product compliant with accessibility guidelines for people with disabilities such as Section 508 or Web Content Accessibility Guidelines (WCAG) from WC3? If not, which guidelines does it follow or not follow?  For WCAG, what level?
 
* Is the product compliant with accessibility guidelines for people with disabilities such as Section 508 or Web Content Accessibility Guidelines (WCAG) from WC3? If not, which guidelines does it follow or not follow?  For WCAG, what level?
 
* If the database includes full text, are the documents in pdf, html, or other formats? Especially if some of the full text is only in pdf, is it tagged to be accessible for text to speech synthesis software? (such as screen readers like Jaws and Window Eyes for vision impaired users and Kurzweil 3000 for people with learning disabilities)  
 
* If the database includes full text, are the documents in pdf, html, or other formats? Especially if some of the full text is only in pdf, is it tagged to be accessible for text to speech synthesis software? (such as screen readers like Jaws and Window Eyes for vision impaired users and Kurzweil 3000 for people with learning disabilities)  
* If you do usability testing with users who have disabilities, could you tell us about it (which adaptive technology or disabilities were included)?  
+
* If you do usability testing with users who have disabilities, could you tell us about it (which assistive technology or disabilities were included)?  
* Do the products have any other features that you think could be especially useful for people with disabilities (such as spell checking)?  
+
* Do the products have any other features that you think could be especially useful for some people with disabilities (such as spell checking)?  
  
 
In my experience, customer service representatives usually need to check with their IT staff to find out about accessibility. I understand that compliance with accessibility guidelines is not necessarily enough to make a product reasonably functional for people with disabilities, and so user testing with people who have disabilities is important.  I believe institutions need to find ways to do this (for our own websites as well as for resources from vendors). In the meantime, I've found that using the questions above has been a practical approach to start with.
 
In my experience, customer service representatives usually need to check with their IT staff to find out about accessibility. I understand that compliance with accessibility guidelines is not necessarily enough to make a product reasonably functional for people with disabilities, and so user testing with people who have disabilities is important.  I believe institutions need to find ways to do this (for our own websites as well as for resources from vendors). In the meantime, I've found that using the questions above has been a practical approach to start with.

Revision as of 12:06, 10 December 2008

This page is for sharing information among library employees about accessibility of library databases and other online resources. I hope you’ll contribute! Please include the sources or experiential basis of your contributions.

There is also a section to share practical information about strategies librarians have used to evaluate accessibility. In my experience, most libraries do not yet have an in depth expert on these issues, so we are learning as we go. If you are very new to accessibility, you might want to start with ASCLA Think Accessible Before You Buy , especially the Understanding the Language section. WebAIM offers another introduction to accessibility Also, I have found this article useful: Web accessibility at academic libraries: standards, legislation, and enforcement. Author(s): Michael Providenti, Robert Zai III Library Hi Tech; Volume: 25 Issue: 4; 2007 Research paper

Thank you to Will Reed and everyone who had the idea for this page. I am an academic reference librarian. I do not have enough experience using adaptive technology to test pages independently, so the information I have to share will be from that point of view. I hope this page can be useful for librarians from public and other types of libraries as well.

Contributions from librarians who use assistive technology are especially appreciated. Suggestions about this page are welcome as well. -Adina Mulliken amullike@syr.edu


Accessibility of specific vendors

DATABASE VENDORS

  • CSA/Proquest (8/2008)

During 2008 Midwinter ALA ACRL-ANSS meeting, representatives said their interface complies with the UKs SENDA accessibility guidelines but they did not know about Section 508. I did not find an accessibility statement on their website.

  • Ebsco (12/2008)

http://www.ebscohost.com/thisTopic.php?marketID=1&topicID=844 http://support.ebsco.com/knowledge_base/detail.php?id=1031&page=&page_function=search&keyword=%5C%22section+508%5C%22 http://support.epnet.com/support_news/detail.php?id=356&t=r&return=true Ebsco has done usability testing with users who have disabilities. They also state they are compliant with Section 508.

  • Gale (8/2008)

http://www.gale.cengage.com/servlet/PressArchiveDetailServlet?articleID=200110_ADApolicy Says “Gale is working hard to get completely compliant. Since Gale publishes content from such a wide variety of reference sources and periodicals, it is difficult to address the tagging and mark-up of every document. We are working toward a standard, accessible interface design, with a goal of making our content meet all the accessibility standards.”

  • OvidSP (8/2008)

“OvidSP will not be compliant, but we're a lot closer than we are with current Ovid Gateway. We've eliminated most graphic buttons in favor of text links (which screen readers can read) We've implemented much of the new functionality, and a bit of the old, such that it degrades gracefully when javascript is not available. Our new color scheme is much easier to read for people with poor eyesight or color blindness For Firefox users, nearly all of the text in the interface can be scaled larger (using Ctrl-+, Ctrl--, and Ctrl-0) to make it even easier to read.” - email I received on 10/26/2007 I did not find an accessibility statement on their website.

  • OCLC (12/2008)

http://www5.oclc.org/downloads/accessibility/508template-fs.html

  • Proquest (12/2008)

http://support.proquest.com/al/12/1/article.asp?aid=2789&bt=4n Says “Compliant with Section 508 of the Americans with Disabilities Act.” Section 508 is part of the Rehabilitation Act of 1973, not the Americans with Disabilities Act, so I don’t know what to think about this statement. Also says “There are…limitations on usability that are imposed by the format of the primary source materials contained in our products - whether they be a periodical, dissertation or other type of content. The format of the materials we receive may prevent some impaired users from being able to use certain of the works where the format is incompatible with the person’s disability and/or the ability of third party applications such as screen readers to render a useable version of the work. For example, while a PDF rendered from a work submitted in text format may allow the Adobe Reader screen reader functionality, a PDF rendered from a work submitted in hard copy form is rendered as an image of the hard copy work (also known as a Scanned Image PDF) and therefore is not compatible with the screen reader functionality. Again, this is a consequence of the format of the works provided to UMI for inclusion within our products.” http://www.proquest.com/en-US/site/accessibility.shtml

  • WilsonWeb (12/2008)

http://www.hwwilson.com/documentation/WilsonWeb/rehabilitation_act_compliance.htm During the 2008 Midwinter ALA ACRL-ANSS meeting, representatives said they communicated with at least one adaptive technology vendor. They did not say if they had done user testing with people who use any adaptive technologies.

FEDERATED SEARCH ENGINES

  • Metalib (12/2008)

http://www.exlibrisgroup.com/default.asp?catid={475327AD-F744-44BC-8901-CFA3765488ED}&details_type=1&itemid={C41A7BEC-B647-41E5-BA68-6320032AA482} “This new version of MetaLib features a fully accessible user interface that complies with the W3C Web Content Accessibility Guidelines 1.0, level A, and Section 508 of the United States Rehabilitation Act (29 U.S.C. 794d).” http://metalib.sibul.ul.pt/V/MEVK15M6X5HH5RI9J61CH7NXHLXDFP2GB3M3DA5UP9G53Y3H7U-01892?func=file&file_name=accessibility “Accessibility Statement Ex Libris™ is committed to making its Web-based applications accessible to as many users as possible regardless of the challenges that they face. As new technologies emerge, Ex Libris makes every effort to improve the accessibility of its products.

The MetaLib® user interface was developed to comply with leading international accessibility and industry standards: The W3C Web Content Accessibility Guidelines 1.0, level A Section 508 of the Rehabilitation Act (29 U.S.C. 794d) Disclaimer Institutions can customize the interface of MetaLib. Ex Libris cannot guarantee that the resulting user interface will be compliant with accessibility standards after a third party has altered the interface.

MetaLib connects to other Web sites maintained by third parties over which Ex Libris has no control. Ex Libris makes no representations as to Web accessibility compliance standards maintained by other Web sites.”

  • Central Search (8/2008)

During a Summer 2007 presentation to Syracuse University Library staff, a customer representative said Central Search was not yet compliant. I did not find an accessibility statement on their website.

MULTIPLE ONLINE RESOURCES

  • Suzanne L. Byerley, Mary Beth Chambers and Mariyam Thohira. (2007). “Accessibility of web-based library databases: the vendors’ perspectives in 2007,” (25)4, Library Hi tech, 2007, 509-527. Contains very useful, in depth information about accessibility from numerous vendors. Information about Ebsco (and probably other vendors) is no longer up to date; however, for vendors that do not post much or any accessibility information on their website, this may be the most current information available.

http://www.emeraldinsight.com/Insight/ViewContentServlet;jsessionid=C55C43123047035ED59F58B072176F3F?Filename=Published/EmeraldFullTextArticle/Articles/2380250406.html

  • Axel Schmetzky’s Web Accessibility Survey Site

http://library.uwsp.edu/aschmetz/Accessible/websurveys.htm especially this section http://library.uwsp.edu/aschmetz/Accessible/websurveys.htm#onlineresources and the accessible policy statements for collection development here http://library.uwsp.edu/aschmetz/Accessible/pub_resources_p.htm#Policy

OTHER

  • Libguides (12/2008)

Libguides has filled out a "Voluntary Product Evaluation Template (VPAT)" which details accessibility of the product. You can request it from Libguides. It is not Section 508 Compliant.

Strategies/experiences evaluating resources

(12/2008 Adina Mulliken) I attempted to use the ASCLA Think Accessible guidelines once by emailing them to a vendor when my library was considering buying a product. When I spoke with the customer service person later, they made it clear they did not understand the guidelines, but would talk with their IT staff. The representative then emailed to say the product was not “compliant” yet. I did not get answers to the specific questions in the guidelines.

I sent the following questions to the organizers of the 2008 Midwinter ALA-ACRL-ANSS meeting. The organizers sent the questions to the vendors before the vendors' presentation at the meeting.

  • Is the product compliant with accessibility guidelines for people with disabilities such as Section 508 or Web Content Accessibility Guidelines (WCAG) from WC3? If not, which guidelines does it follow or not follow? For WCAG, what level?
  • If the database includes full text, are the documents in pdf, html, or other formats? Especially if some of the full text is only in pdf, is it tagged to be accessible for text to speech synthesis software? (such as screen readers like Jaws and Window Eyes for vision impaired users and Kurzweil 3000 for people with learning disabilities)
  • If you do usability testing with users who have disabilities, could you tell us about it (which assistive technology or disabilities were included)?
  • Do the products have any other features that you think could be especially useful for some people with disabilities (such as spell checking)?

In my experience, customer service representatives usually need to check with their IT staff to find out about accessibility. I understand that compliance with accessibility guidelines is not necessarily enough to make a product reasonably functional for people with disabilities, and so user testing with people who have disabilities is important. I believe institutions need to find ways to do this (for our own websites as well as for resources from vendors). In the meantime, I've found that using the questions above has been a practical approach to start with.