The W3C Web Accessibility Initiative
The World Wide Web Consortium (W3C) spearheaded the Web Accessibility Initiative (WAI) as a means to develop a set of international guidelines for web accessibility, as well as promote web usability for people with disabilities. The WAI also develops support materials and resources to promote broader understanding and implementation of Web accessibility. The WAI pursues accessibility of the Web via five primary activities:
- Ensuring that core technologies of the Web support accessibility
- Developing guidelines for Web content, user agents, and authoring tools
- Facilitating development of evaluation and repair tools for accessibility
- Conducting education and outreach
- Coordinating research and development affecting future accessibility of the Web
What is Web accessibility?
Web accessibility refers to the ability of people with disabilities to interact, perceive, navigate, and understand the Web. Web accessibility is not limited to accommodating those with visual disabilities; it includes those with physical, cognitive, speech, auditory, and neurological disabilities as well. It is important to remember that Web accessibility benefits those without disabilities, because one of the key tenets of Web accessibility is designing Web sites and software flexible enough to meet a wide range of user needs, preferences, and situations. These situations may include a slow internet connection, a temporary disability such as a broken arm, or changing abilities brought on by aging. Although progress has been made, most Web sites and Web software (Web browsers, authoring tools, and media players have accessibility barriers that make it difficult or impossible for people with disabilities to use the Web to its fullest extent.
Components of Web Accessibility
Web accessibility depends on several components of Web development and interaction working together: content (e.g., the information contained within each Web page), user agents (e.g., Web browsers and media players), assistive technology (screen readers, alternative keyboards, scanning software, etc.), user knowledge and adaptive strategies, developers, authoring tools, and evaluation tools. All of these components are interdependent. Therefore, when accessibility features are implemented effectively in one component, they are more likely to be implemented within the other components. On the other hand, if an accessibility feature is not implemented in one component, the motivation for implementation within other components is diminished. For example, developers will not take the time to implement a particular accessibility feature if it is not supported by authoring tools, browsers, or assistive technologies. While it is possible for different components to compensate via "work-arounds," it requires considerably more effort and often does not result in overall accessibility.
