- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Tue, 09 Sep 2014 14:45:42 -0400
- To: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>, Joseph Scheuhammer <clown@alum.mit.edu>, Karl Groves <kgroves@paciellogroup.com>, James Craig <jcraig@apple.com>
- CC: Léonie Watson <LWatson@paciellogroup.com>, W3C WAI Protocols & Formats <public-pfwg@w3.org>
> It looks like I was typing at the same time.
That's what I thought when I saw your message. :-)
> So would aria-expanded='true' be applied to the container with role=tabpanel as well?
That's a user experience question -- would it be useful to a user that a
given tabpanel is expanded if the user's point of regard is on that
tabpanel? I don't know. My point was that in the case of tab/tabpanel,
placing aria-expanded on both (and keeping them in sync), is not
incoherent as it is for a treeitem and the children it controls.
However, as you said, "Adding it to the container as well sounds a bit
confusing to me, since, if the content is visible and readable, it is
already implicitly expanded". Is there any way to get at the tabpanel
-- for the user's point of regard to be on it -- without expanding it?
If so, then it might be useful to be able to query the tabpanel and ask,
"by the way, are you expanded?".
--
;;;;joseph.
'Array(16).join("wat" - 1) + " Batman!"'
- G. Bernhardt -
Received on Tuesday, 9 September 2014 18:46:14 UTC