RE: accessible name calculation for hidden labels

If aria-hidden=”true” is set on the node, or CSS display:none or visibility:hidden is set on that node, then that and any subtree elements should not be used as part of the naming calculation.

This is critical, otherwise it will make it impossible to reliably render complex structures like Tree, Treegrid, and so on, which always have nested structures that are hidden at times.




From: Steve Faulkner [mailto:faulkner.steve@gmail.com]
Sent: Tuesday, September 22, 2015 8:33 AM
To: W3C WAI Protocols & Formats <public-pfwg@w3.org>; Joseph Scheuhammer <clown@alum.mit.edu>
Subject: Re: accessible name calculation for hidden labels

note: limted testing of some current browser implementations  = do not produce accessible names from  labels with display:none or aria-hidden=true.

actually, this is not correct: (latest browsers on windows 10)
Chrome: neither results in acc name
Firefox: only aria-hidden true results in an accessible name
IE 11:both result in an accessible name
test file: http://codepen.io/stevef/pen/PPzLdV


--

Regards

SteveF
Current Standards Work @W3C<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>

On 22 September 2015 at 16:19, Steve Faulkner <faulkner.steve@gmail.com<mailto:faulkner.steve@gmail.com>> wrote:
It is unclear to me, from reading the accname spec [1] whether the following markup  examples should result in an accessible name for a control
label with aria-hidden=true

<label for="test" aria-hidden="true"> name </label>
<input type="text" id="test">

label CSS set to display:none

<label for="test1" style="display:none"> name </label>
<input type="text" id="test1">
note: limted testing of some current browser implementations  = do not produce accessible names from  labels with display:none or aria-hidden=true.

[1] rawgit.com/w3c/aria/master/accname-aam/accname-aam.html<http://rawgit.com/w3c/aria/master/accname-aam/accname-aam.html>
--

Regards

SteveF
Current Standards Work @W3C<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>