- From: Léonie Watson <tink@tink.uk>
- Date: Thu, 7 Apr 2016 09:15:39 +0100
- To: "'Cynthia Shelly'" <cyns@microsoft.com>, "'Accessible Rich Internet Applications Working Group'" <public-aria@w3.org>
Received on Thursday, 7 April 2016 08:16:21 UTC
From: Cynthia Shelly [mailto:cyns@microsoft.com] Sent: 07 April 2016 01:20 “”HTML5accessibility.com test asserts that the paragraph (id=1) and the button (id=2) should be visually hidden, but available in the AAPI. Does the ARIA WG agree? <p hidden aria-hidden="false" id=”1”>one</p> <input id="2" type="button" hidden aria-hidden="false" />” This seems right technically. At the risk of resurrecting an old discussion, I’m not sure API access to hidden content is something we should be encouraging though? “What about aria-hidden=false objects that are children of hidden or display:none? Should the paragraph (id=4) be in the accessibility tree? <div hidden id=3>two<p aria-hidden=false id=4>three</p>four</div>” AFAIK hidden is inherited, so this would have the same effect as the previous examples. Léonie. -- @LeonieWatson tink.uk Carpe diem.
Received on Thursday, 7 April 2016 08:16:21 UTC