Web Accessibility Initiative

Making the web accessible to all people, regardless of disability, age, etc., is the goal of this initiative, with emphasis not only on websites but web software. The groups making up the WAI want to create a web where not only can people with disabilities access the web, but also contribute. They argue that the technological advantages of the web allow for new "unprecidented" possibilities for access to and interaction with information in a way never previously possible using standard tools like print or video media. The introduction has very little applicable information, so....

I dug a little deeper and began looking at actual evaluations and guidelines.

Essential Components of Web Accessibility employs a relatively simple-enough concept of interdependency between users and authors as the heart of web access. If the authoring tools and evaluative tools developers use produce content which are directly accessed by users employing assistive technology, browsers, and media players, and everything works the same way on each side of the coin, the system runs smoothly and users are not denied access because of some disability. Furthermore, if implemented and maintained correctly, the system is self-perpetuating in a sort of economic concept of proportionate supply-and-demand. If users can access the web universally using certain tools, those tools come into demand, as does the demand for developers to continue to create web media which universally interacts with these tools and users, and like a cycle, the system flourishes. This is essentially the goal of the initiative. The W3C and WAI have a trifecta of guidelines for creating and maintaining user accessibility aimed at the three levels of the web: developer, content, user. The ATA (Authoring Tool Accessibility Guidelines) looks at developing tools, the WCAG (Web Content Accessibility Guidelines) at the content in static terms, separate from user and developer, and the UAAG (User Agent Accessibility Guidelines) looks at how end-users receive and interact with web content.

There are mountains of information contained here and I couldn't begin to sort through it all in a few hours' time. The fact that these guidelines go so far as to evaluate content evemts triggered by mouse interaction is testimony to the extensive nature of considerations. I'm unable to comment with much authority without taking the time to look further into the policies and concerns, which would ultimately be an entire semesters' worth of work. I find it a daunting task to place all disabilities under one umbrella and try to shotgun web content in one fail swoop. It certainly seems to be a valiant goal and a worthwhile endeavour.