W3C home > Mailing lists > Public > public-html-a11y@w3.org > September 2012

[Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204

From: <bugzilla@jessica.w3.org>
Date: Mon, 10 Sep 2012 23:59:11 +0000
Message-Id: <E1TBDsl-0004GO-AL@jessica.w3.org>
To: public-html-a11y@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18744

--- Comment #26 from James Craig <jcraig@apple.com> 2012-09-10 23:59:11 UTC ---
(In reply to comment #19)
> (In reply to comment #15)
> You might have the same control referencing multiple descriptions and hide all
> but the currently relevant one, and in fact authors try to do this:
> 
> http://www.nvda-project.org/ticket/2597
> 
> Previously brought to the WG's attention:
> http://lists.w3.org/Archives/Public/public-html/2012Aug/0212.html

I don't necessarily agree with that design pattern, but there is a potential
here to have a more explicit way for users to switch this explicitly for the
example you describe.

  aria-hidden="false"

Hides from accessibility APIs no matter if the content is shown or hidden. I
think aria-hidden should override hidden="" in all cases, regardless of
modality. The flipside applies, too: 

  <div hidden aria-hidden="false">…</div>

That is, specifically hidden from mainstream interfaces, but overridden so that
that the structure is available in Accessibility APIs. (Disclaimer: to my
knowledge, no Users Agents currently expose hidden content this way.)

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 10 September 2012 23:59:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 10 September 2012 23:59:13 GMT