W3C home > Mailing lists > Public > wai-xtech@w3.org > August 2010

RE: ISSUE 30 @longdesc use cases

From: John Foliot <jfoliot@stanford.edu>
Date: Mon, 23 Aug 2010 17:00:23 -0700 (PDT)
To: "'Jonas Sicking'" <jonas@sicking.cc>, "'Ian Hickson'" <ian@hixie.ch>
Cc: "'Joshue O Connor'" <joshue.oconnor@cfit.ie>, "'HTML Accessibility Task Force'" <public-html-a11y@w3.org>, "'HTML WG'" <public-html@w3.org>, "'W3C WAI-XTECH'" <wai-xtech@w3.org>, "'Barry McMullin'" <barry.mcmullin@dcu.ie>, "'Laura Carlson'" <laura.lee.carlson@gmail.com>
Message-ID: <033f01cb431f$5375fe40$fa61fac0$@edu>
Jonas Sicking wrote:
> 
> Note that my example has nothing media-specific in it. AT tool users
> also do not see the content when it's read by a screen reader when the
> reader is reading the normal flow of the page.

One of the things that seems to be missing here is that the user of the
screen reader must have a mechanism to read or ignore that alternative
text: it's a user choice thing. So how does the screen reader go from
"reading the normal flow of the page" to "taking a side trip to go read
what this otherwise hidden stuff is about"?  And given that this is now
(again) apparently being targeted to screen readers only, what of those
users who aren't blind that need the expanded text as well? How do they
access content that is otherwise not in the normal flow? Is there a
toggling mechanism for them? Discovery of the alternative text is a big
part of the required functionality. 

JF
Received on Tuesday, 24 August 2010 00:01:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 13:16:09 GMT