Showing papers on "Web accessibility published in 1999"

Checklist of Checkpoints for Web Content Accessibility Guidelines 1.0

Abstract: This document is an appendix to the W3C "Web Content Accessibility Guidelines 1.0". It provides a list of all checkpoints from the Web Content Accessibility Guidelines 1.0, organized by concept, as a checklist for Web content developers. Please refer to the Guidelines document for introductory information, information about related documents, a glossary of terms, and more. This list may be used to review a page or site for accessibility. For each checkpoint, indicate whether the checkpoint has been satisfied, has not been satisfied, or is not applicable. A tabular version of the list of checkpoints is also available (e.g., for printing). This document has been produced as part of the Web Accessibility Initiative. The goal of the WAI Web Content Guidelines Working Group is discussed in the Working Group charter.

Accessibility of Special Education Program Home Pages

Abstract: The World Wide Web (WWW) is a universal medium that has revolutionized the dissemination and gathering of information; however, on-line barriers limit the accessibility of the WWW for individuals w...

Accessibility in the Virtual Library: Creating Equal Opportunity Web Sites.

Abstract: In compliance with the Americans with Disabilities Act (ADA), libraries not only have to provide equal access for patrons to physical collections and equipment but to electronic resources as well. The Web Accessibility Initiative is developing guidelines for building Web sites that are accessible to people with disabilities. By following these guidelines and using common sense, a library Web site can be ADA compliant and ensure that every patron has access to all the resources a library has to offer. To use a common metaphor, there are some who need more than an on-ramp to get onto the information superhighway. Building accessibility into a library Web site ensures that all patrons have a chance to access the resources a library has to offer. Unfortunately, computer design "assumes use of several physical capabilities or combinations of capabilities--sight for viewing the monitor, manual dexterity for typing on the keyboard, and hand-eye coordination for using the mouse, etc."(1) Although a well-designed Web site allows for assistive technology to relieve some of these difficulties, accessibility has to be built into the Web site itself. As Marcia Norris of De Anza College in California puts it: "If we can get universal design built in at the front end, it will be easier than having to retrofit or to have separate but equal sites."(2) Although providing access to information resources is a prime purpose of a library, the 1990 Americans with Disabilities Act impresses upon us the need to increase our efforts to ensure that all patrons have equal access to these resources. Coincidental to the passing of this bill has been the rise of the Internet from ivory tower obscurity through the development of gopher, text-based browsers, and Graphical User Interfaces (GUIs). The increased availability of personal computers, public Internet access, and adaptive computer technology have produced an explosion in information provision and exchange. People with disabilities have relatively easy access to more information sources than ever before, especially when using assistive technologies such as screen readers, information sources such as gopher, and text-based browsers such as Lynx. For some people, such as print-impaired users, "much of this information was inaccessible prior to the advent of the computer."(3) Ironically, the Graphical User Interface that transformed the Internet into the World Wide Web has all but slammed the door shut on this flood of information resources for people with disabilities. Fortunately, the GUI is flexible enough to address the issue of accessibility. It's a matter of "educating site designers about information-access barriers on the WWW and how to overcome those barriers."(4) In February of 1998, the Web Accessibility Initiative (WAI), a part of the World Wide Web Consortium (W3C), "issued the first public working draft of a document to guide page builders in constructing Web Sites accessible to people with disabilities."(5) Although this document and its revisions must be treated as a work in progress, library Web sites can be made accessible by combining common sense and incorporating WAI recommendations. The first step in making a Web site accessible is to determine what makes it inaccessible. People facing visual, hearing, motor, learning, and cognitive barriers each encounter different problems with a Web site. Sometimes, a remedy for one can create a barrier for another. Keeping the design as simple as possible is a good starting point for building a barrier-free Web site. This does not mean there has to be a bland, boring presentation of content. It means that all elements must be chosen deliberately to enhance the content rather than be window dressing or distract from the presentation. Some of these barriers can be removed by adjusting browser preferences and using adaptive technology, but only if the Web site supports these options. In other words, the designer has to know what parts of the Web site to leave to the control of the patron. …

Scalable web server design for distributed data management

Abstract: With the explosive popularity of the internet and the world wide web (WWW), there is a rapidly growing need to provide unprecedented access to globally distributed data sources through the internet. Web accessibility will be an essential component of the services that future digital libraries should provide for clients. This need has created a strong demand for database access capability through the internet, and high performance scalable web servers. As most popular web sites are experiencing overload from an increasing number of users accessing the sites at the same time, it is desired that scalable web servers should adapt to the changing access characteristics and should be capable of handling a large number of concurrent requests simultaneously, with reasonable response times and minimal request drop rates.

Evaluating accessibility and usability of Web pages

Abstract: BobbySM is a computer-based tool that supports Universal Design of a specific computer-human interface, the World Wide Web. The notion of a universally designed Web challenges society to think about plurality—to consider all individuals, regardless of age, ability, race, or economic or cultural background—when developing new technologies. Yet at this time, though the Web has much potential for broad inclusion, it often excludes some people from participating in much the same way that a staircase prevents a person in a wheelchair from going in a building’s door. In response to this, CAST launched Bobby in August 1996. Bobby teaches Web designers about Web accessibility by displaying accessibility problems directly within the context of the designer’s site. Bobby is a teaching tool, helping Web designers (including the rapidly growing number of non-professional designers who are putting up sites) learn skills they can apply later. The more people use Bobby, the more likely they will be to integrate accessibility principles into their way of thinking and the irstyle of Web site design.

Web Page Accessibility on the University of Wisconsin's Campuses

Abstract: Comparative study of the web page accessibility on the various University of Wisconsin campuses. Three questions are addressed: 1. How accessible are campus web pages? 2. To which extent are policies in place that mandate accessible web page design? 3. To which extent is concern for accessibility reflected in on-campus web authoring training and instructional resources? A "Accessible Web Page Design Resources" Page is included.

Considering accessibility for visually impaired users [Web site design]

Abstract: The highly visual nature of the World Wide Web makes addressing visual disabilities one of the most pressing concerns faced by Web designers. Such concerns should be addressed early in the design phase, with special attention paid to specific design elements, such as colors and fonts, as well as the infrastructure of the Web site. This paper covers design conventions that will increase the accessibility of a Web site for visually impaired audiences. Why is this important? According to Bergman and Johnson (1995), accessibility is "a category of usability". Therefore, before a Web site can be tested for usability, its coding and design must first be accessible to the targeted users, i.e. accessibility must be in place before a conventional usability test can be conducted on representatives from the target audience-in this case, the visually impaired.

Web Page Accessibility at U.S. Universities

Abstract: Study of the web page accessibility at the various U.S. Universities. Three questions are addressed: Research tools is Bobby. A "Accessible Web Page Design Resources" Page is included.