- From: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>
- Date: Tue, 9 Sep 2014 17:59:00 +0000
- To: 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. So would aria-expanded='true' be applied to the container with role=tabpanel as well? That part is somewhat confusing to me, because setting the aria-expanded attribute doesn't affect the visibility of the element, and if it is already rendered and readable, wouldn't it already be implicitly expanded? -----Original Message----- From: Joseph Scheuhammer [mailto:clown@alum.mit.edu] Sent: Tuesday, September 09, 2014 10:52 AM To: Karl Groves; James Craig Cc: Léonie Watson; W3C WAI Protocols & Formats Subject: Re: Query about intent of aria-expanded > So would the best practice be to place it on both the control and the > section being expanded/ collapsed (IOW not either-or)? That depends on the context or role. For a tree view [1], aria-expanded on the controller is important, but it can't be applied to the exposed children. Consider that the children themselves are potentially expandable -- that is, they might have children as well. Thus, their aria-expanded is set to true when they themselves are expanded, not because their controller (parent) is expanded. On the other hand, in the case of tablist [2], it's possible to place it on both the controlling tab [3] and the controlled tabpanel [4] without the above limitation. [1] http://www.w3.org/TR/wai-aria/roles#tree [2] http://www.w3.org/TR/wai-aria/roles#tablist [3] http://www.w3.org/TR/wai-aria/roles#tab [4] http://www.w3.org/TR/wai-aria/roles#tabpanel -- ;;;;joseph. 'Array(16).join("wat" - 1) + " Batman!"' - G. Bernhardt -
Received on Tuesday, 9 September 2014 17:59:38 UTC