In web accessibility, you’ll often hear emphasis being placed on the duty of web authors to create accessible content. However, this is only one part of the web accessibility equation.
One that has been particularly close to me, or rather one that has provided me with a lot of opportunity to rant, is the responsibility of developers of user agents.
Any effort on the part of web authors to add accessibility features is rendered useless if browsers and assistive technologies don’t take advantage of them. User agent developers need to ensure that their products support these features and, most crucially, make them available to users in an accessible and obvious manner.
Although far from perfect, the W3C’s User Agent Accessibility Guidelines (UAAG) 1.0 do provide a good starting point.
What follows is a quick run-down of most of UAAG’s guidelines and checkpoints, annotated with comments, suggestions, personal gripes about current levels of implementation, and wishlists for future browser versions.
Admittedly a tad rough around the edges, this is a first attempt at crystallising some of the discussions I’ve had with fellow ATF colleagues, members from the W3C, and other accessibility aficionados.
- #1 On May 20th, 2007 11:39 pm