- From: Jim Allan <jimallan@tsbvi.edu>
- Date: Mon, 1 Nov 2010 15:13:34 -0500
- To: wed@csulb.edu
- Cc: deborah.kaplan@suberic.net, W3C WAI ig <w3c-wai-ig@w3.org>
The User Agent Accessibility Working Group would encourage review of the document. (www.w3.org/tr/uaag20) Full keyboard access (including to the @title and @alt) has been a requirement since UAAG1. Unfortunately, no user agent has implemented keyboard access to these attributes. Also, talking to your browser developers/manufactures and explaining your accessibility needs may help. Guidelines only work when someone implements them. Please review the document. Feedback is welcomed and appreciated. Jim Allan, Co-Chair, W3C/WAI User Agent Working Group On Mon, Aug 16, 2010 at 2:04 PM, Wayne Dick <wed@csulb.edu> wrote: > Dear Deborah, > > Now, I think we actually agree. The User Agent Accessibility > Guidelines are up for review right now. We need to review this > carefully. Browsers, media players like Acrobat Reader, screen > readers, talking browsers and other reading assistants are all user > agents. Also, this matter needs to brought up in the 508 revise. > > User agents must recognize accessibility messages and use them. That > applies to assistive technologies as well as mainstream browsers and > media players. It makes no sense to give well meaning developer a > well crafted set of rules and then tell them they cannot use them. > We've gone to all this work to set realistic standards for content, > and the UA's let us down. > > Our frustrations are the same. The criteria and sufficient conditions > are sound, the UA implementations fail. > > Cheers, > Wayne > > -- Jim Allan, Accessibility Coordinator & Webmaster Texas School for the Blind and Visually Impaired 1100 W. 45th St., Austin, Texas 78756 voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/ "We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Monday, 1 November 2010 20:14:05 UTC