Wednesday, April 27, 2011

Tech Article Discussion: Web Accessibility, Libraries, and the Law

Fulton, C. (2011). Web accessibility, libraries, and the law. Information Technology & Libraries, 30(1), 34-43. Retrieved from EBSCOhost.

Last semester I took a course, Information Architecture for the Web, in which we spent a significant amount of time working to identify accessibility barriers on various websites and improve the accessibility of those websites we designed. We used a variety of resources to identify potential areas of weakness in our websites, and were able to meet with employees from the IU Adaptive Technology and Accessibility Centers (ATAC). They offer extensive services to those with disabilities as well as to those working with individuals with challenges. For our class, we discussed the obstacles various elements of web design might present as well as how the ATAC can help test and evaluate client websites to improve accessibility.

Fulton's article takes this one step further, examining federal laws and state statutes for web accessibility. She examines three assumptions:
  • Although the federal government has no web accessibility laws in place for the general public, most states legalized web accessibility for their respective agencies.
  • Most state statutes do not mention Section 508 of the Americans with Disabilities Act (ADA) or acknowledge World Wide Web Consortium (W3C) standards.
  • Most libraries are not included as entities that must comply with state web accessibility statutes.
While the Individuals with Disabilities Education Act (IDEA) does require schools and colleges to provide access to education resources, it does not require libraries to support this with their web presence. Issues of accessibility will continue to rise as library web services continue to grow and replace "traditional" print resources. It has fallen to individual states to define when and how accessibility standards should be implemented and enforced. Section 504 prevents the exclusion of those with disabilities "from programs or activities that are funded by federal dollars" and notes specific examples; because web accessibility is not addressed, state employees must analyze and interpret the law.

After examining each state's government websites for web accessibility standards (as opposed to building accessibility), Fulton compiled a list and addressed the three assumptions listed above. The first discussed state web accessibility standards; Fulton found 17 states have laws about web accessibility with only four with coverage including institutions receiving state funds. Others have established guidelines another way (except for Alaska and Wyoming, which had no accessibility standards available online). The second assumption was found to be true; Fulton found only seven states which directly address Section 508 or the W3C Web Content Accessibility Guidelines 1.0 (with only Minnesota referencing the more recent W3C WCAG 2.0). The last assumption, regarding libraries not being required to comply to state web accessibility standards, was also found to be true. Only Arkansas, California, Kentucky, and Montana require accessibility compliance in order to receive state funds; university libraries in Illinois, Oklahoma, Texas, and Virginia are required to have their websites at the same level as their state agency websites.

There are many barriers related to the time and finances it takes to make websites accessible; however, by not following accessibility standards approximately 24.5 million people around the United States have difficulties accessing the information they need. Reaching and serving patrons with disabilities should be approached as embracing a new way of thinking, not as a hassle. Accommodating those with special needs is more than just providing accessible physical spaces. The author notes, "Lack of statutes or federal laws should not exempt libraries from providing equivalent access to all; it should drive libraries toward it."

Additional resources:

No comments:

Post a Comment