1 / 45

Web Accessibility

Web Accessibility. An Evaluation and Discussion of the Web Accessibility of Academic Library Web Sites. Dave Comeaux Web Services Librarian Tulane University. What is Web Accessibility Why it’s Important How Academic Libraries are doing. What is web accessibility?.

latham
Télécharger la présentation

Web Accessibility

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Web Accessibility An Evaluation and Discussion of the Web Accessibility of Academic Library Web Sites Dave Comeaux Web Services Librarian Tulane University

  2. What is Web Accessibility • Why it’s Important • How Academic Libraries are doing

  3. What is web accessibility? • Web accessibility means that people with disabilities can use the Web. More specifically, Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with the Web, and that they can contribute to the Web. (World Wide Web Consortium - http://www.w3.org/WAI/intro/accessibility.php) • Web accessibility refers to the inclusive practice of making websites usable by people of all abilities and disabilities. When sites are correctly designed, developed and edited, all users can have equal access to information and functionality. (Wikipedia - http://en.wikipedia.org/wiki/Web_accessibility)

  4. Why is it important • Helps everyone • Required by law • Helps fulfill the long-standing goal of libraries to provide barrier-free access to everyone

  5. Helps Everyone • Accessible design is universal design • Each of the major categories of disabilities requires certain types of adaptations in the design of the web content. Most of the time, these adaptations benefit nearly everyone, not just people with disabilities. • For example: • Almost everyone benefits from helpful illustrations, properly-organized content and clear navigation. • Similarly, while captions are a necessity for Deaf users, they can be helpful to others, including anyone who views a video without audio. (WebAIM - http://webaim.org/intro/)

  6. Legal Mandate for Accessible Web Content • Sect. 508 (Rehabilitation Act Amendment of 1998)Under Section 508 (29 U.S.C. ‘794 d), agencies must give disabled employees and members of the public access to information that is comparable to access available to others.  • Section 504 (Rehabilitation Act of 1973) • ADA (1990/2008) • Title II (public entities) • Title III (private entities; places of public accommodations)

  7. Research Overview • This research is based on automated testing • Enables analysis of thousands of web pages for machine-detectable errors • Does not involve user testing • Builds on research performed by Schmetze (2001, 2002) and Comeaux and Schmetzke (2007)

  8. Research Overview • Axel Schmetzke, “Web accessibility at university libraries and library schools,” Library Hi Tech, 19(1), 35-499. (2001) • Axel Schmetzke, “Web Accessibility at University Libraries and Library Schools: 2002 Follow-Up Study,” In Mary Hricko, ed.,Design and Implementation of Web-Enabled Teaching Tools.  Hershey, PA: Idea Group Publishing, 2003: 145-189. • David Comeaux and Axel Schmetzke, “Web Accessibility of North American Library School and Library Web Sites,” Library Hi Tech, 25(4), 457-477. (2007)

  9. Research Methodology • Study size: • 56 academic libraries (2002, 2006, 2010, 2012) • The main libraries at institutions with ALA-accredited SLISs • Geographic coverage: US and Canada

  10. Research Methodology • As in previous studies, Bobby 3.1.1 was used. • Bobby tests for alt tags on images, image maps, objects, frame titles (Priority 1 errors that can be checked automatically) • Homepages plus one link-layer down (within the domain or folder) • Extracted two key figures: • Percentage of Bobby-approved pages (no P1 errors) • Average errors per page (total errors / pages)

  11. Research Methodology

  12. Research Methodology

  13. Research Questions 1.How accessible are the library Web sites? (in terms of the percentage of barrier-free pages and errors per page) 2. How many library sites use "Skip Navigation" links and does their use correlate with accessibility?

  14. Research Questions 3. How does the method of page layout (table-based or CSS-based) correlate with accessibility? 4. Does the use of a Content Management System (CMS) correlate with accessibility? 5.Does the home page search interface correlate with accessibility?

  15. How accessible are they? • How accessible are the library Web sites in 2010? • Overall, 60.70% Bobby-approved. • 8 were 100% approved. • 13 sites were above 90% approved. • 11 were between 80% & 90% approved. • 6 had no approved pages • 7 had less than 10% approved. • Average errors per page: 2.28

  16. How accessible are they? • How accessible are the library Web sites on the in 2012? • Overall, 61.47% Bobby-approved. • 7 were 100% approved. • 23 sites were above 90% approved. • 7 were between 80% & 90% approved. • 5had no approved pages • 14had less than 10% approved. • Average errors per page: 1.66

  17. Trends 56 library web sites

  18. Skip Navigation • Why have Skip Navigation links? • In this example, it takes the screen reader 2 minutes to get to the page content!

  19. Skip Navigation • Research Method – looked at source code – searched for “Skip, Jump “ • Looked at home page and at least one internal page (typically the “About” page)

  20. How many library sites use "Skip Navigation" links? • 25 (44.6%) used skip navigation links. 2006 • 10 (17.9%) used skip navigation links. 2010 2012 • 27 (48.2%) used skip navigation links.

  21. Connection between use of “skip links” and broader accessibility 2006 2010 2012

  22. Conclusion • The use of “skip navigation” links are associated with higher accessibility • Probably the high accessibility ratings can be ascribed to a greater awareness

  23. Page Layout • Table or div – in earlier studies, I observed that a high incidence of errors were caused by missing alt text on “spacer” images • Since spacer images are usually only used with table-based layouts, it seemed that there may be a correlation

  24. Page Layout • Table or div – used Web Developer toolbar – Outline Table cells tool

  25. Page Layout • A site whose layout is table-based will look like

  26. Page Layout 2010 2012

  27. Conclusion • Websites whose layouts are primarily driven by CSS have considerably fewer errors per page than table-based layouts

  28. Does the use of a (CMS) correlate with accessibility? Does the use of a Content Management System (CMS) correlate with accessibility?

  29. What is a Content Management System? • A Content Management System (CMS) is a web-based software application that uses a programming language to assemble web pages from content stored in a database. • Pages are built according to a template, which in theory can make accessibility easier • However, a CMS is often used to decentralize web publishing, so employees with little web experience (and likely no experience with accessibility issues) are able to publish

  30. Methodology • Not an exact science! Most commercial and open-source systems can be detected, but “home-made” CMSs are not

  31. Methodology • ChromeSniffer (Browser Extension)

  32. Methodology • Manual Code Examination

  33. How many sites use a CMS? 2010 • 16 (28.57%) used a CMS. 2012 • 19 (33.93%) use a CMS.

  34. Are they more accessible? 2010 2012

  35. Conclusion • Websites that use a CMS have considerably fewer errors per page and a higher percentage of error-free pages that websites that do not use a CMS

  36. Search Interface • Most library websites include a search interface on the home page. • Many include a “tabbed search” interface, where users can select which search tool to use • Usually this includes the catalog, federated search, a search for ejournals or databases by title, etc.

  37. Search Interface

  38. Search Interface

  39. How many sites use a tabbed search on the home page? • 42 (75%) use a tabbed search interface. • 10 (17.86%) use a single search interface. • 2 have multiple single search boxes • 2 have no search boxes on the home page

  40. Is there a a correlation? 2012 * 1 site had almost 20 errors per page; removing this site drops the average down to 1.5

  41. Conclusion • Tabbed searches are not associated with a higher incidence of machine-detectable accessibility errors • Other possible barriers, such as reliance on JavaScript or difficulty navigating between tabs using a screen reader, cannot be detected with this testing method • Further research, involving user testing, should be done

  42. Testing your sites • Web Developer Toolbar

  43. Testing your sites • Functional Accessibility Evaluator 1.1 http://fae.cita.uiuc.edu/about/

  44. Testing your sites • WAVE Toolbar (Firefox only) http://wave.webaim.org/toolbar

  45. Questions?

More Related