- From: Joseph Scheuhammer <clown@utoronto.ca>
- Date: Fri, 31 Oct 2008 13:18:03 -0400
- To: Richard Schwerdtfeger <schwer@us.ibm.com>
- CC: Jon Gunderson <jongund@illinois.edu>, Aaron M Leventhal <aleventh@us.ibm.com>, David Bolter <david.bolter@utoronto.ca>, w3c-wai-pf@w3.org, wai-xtech@w3.org, wai-xtech-request@w3.org
Rich,
Just picking nits and seeing if I understand you.
For something that is visually rendered as a set of tabs, set its role
to "tablist" and its multiselectable property to "false".
For something that is rendered like Sun's accordion example, set its
role to "tablist" and its multiselectable property to "true".
In these two cases, a screen reader has sufficient information to speak
"tabpanel" in the first case, and "accordion" in the second.
> The GWT example should behave like the Dojo tabpanel (single select).
As it happens, dojo's *accordion*, whose role is marked as "tablist", is
single select. Presumably, its multiselectable property should be
"false". A screen reader would speak "tabpanel" for a dojo accordion.
In a work environment with blind and sighted users, it might be jarring
to the sighted user to hear "tabpanel", when it obviously looks like an
accordion.
Describing a single-select accordion as a "tablist" is not decidely
wrong, though. Perhaps the sighted user will just have to get used to it.
--
;;;;joseph
'This is not war -- this is pest control!'
- "Doomsday", Dalek Leader -
Received on Friday, 31 October 2008 17:19:03 UTC