- From: Janina Sajka <janina@rednote.net>
- Date: Thu, 16 Feb 2012 21:50:43 -0500
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Cc: Laura Carlson <laura.lee.carlson@gmail.com>, Joseph Scheuhammer <clown@alum.mit.edu>, "wai-xtech@w3.org" <wai-xtech@w3.org>
Leif Halvard Silli writes: > Laura Carlson, Thu, 16 Feb 2012 10:55:09 -0600: > > What about the user level? What is impacted? > > At the user level, the impact is meant to lead to a richer experience. > E.g. instead of flattening the following link to a text string, the > user instead receives it as a link: > > <img src=image aria-describedby=description alt=text > > <a id=description hidden=hidden aria-hidden=true > href=link >Link to long description.</a> > > And according to Jonas, last week in public-html@, then whether the AT > would perceive the above link as link, would not depend on the AT - but > on the UA. If that is so, then it diminishes the possible downsides a > lot: The only requirement would then be that the AT supports > @aria-describedby. > And what about people who might want to consume the content but who do not use AT? I seem to recall this was an important requirement of the HTML-WG some months back, and rightfully so. It seems to me a lot of complication is being concocted to serve a function far more simply served by longdesc. I still suggest a shave with Occam's Razor. Janina -- Janina Sajka, Phone: +1.443.300.2200 sip:janina@asterisk.rednote.net Chair, Open Accessibility janina@a11y.org Linux Foundation http://a11y.org Chair, Protocols & Formats Web Accessibility Initiative http://www.w3.org/wai/pf World Wide Web Consortium (W3C)
Received on Friday, 17 February 2012 02:51:12 UTC