- From: Maciej Stachowiak <mjs@apple.com>
- Date: Tue, 18 Sep 2012 14:37:35 -0700
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Cc: Laura Carlson <laura.lee.carlson@gmail.com>, James Craig <jcraig@apple.com>, Cynthia Shelly <cyns@microsoft.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>, Ted O'Connor <eoconnor@apple.com>
On Sep 18, 2012, at 1:42 PM, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> wrote: > Maciej Stachowiak, Tue, 18 Sep 2012 09:57:28 -0700: >> On Sep 18, 2012, at 9:28 AM, Laura Carlson wrote: > >>> On Tue, Sep 18, 2012 at 9:36 AM, Janina Sajka <janina@rednote.net> wrote: >>> >>>> The intention of the language we're looking for is to allow software to >>>> identify which hidden conten can be revealed to users at their request, >>>> and which content cannot. If the id and href approach is insufficient >>>> for that, then we would need a different approach. But, the approach >>>> must be one that software can reliably use to distinguish between the >>>> two use cases of hidden content. >>> >>> Here is an idea: add a discoverable attribute. @discoverable or >>> @nothiddenfromAT >> >> Would it mean something different than aria-hidden=false? > > Currently, aria-hidden=true is a boolean attribute value. Thus > aria-hidden=false is only informative. I saw that James proposed that > aria-hidden=false should have an effect. As far as I can tell: - aria-hidden is not a boolean attribute in the HTML sense (i.e. it's not just presence or absence that matters, the attribute value actually matters) - both aria-hidden=true and aria-hidden=false are defined to have meaning by WAI-ARIA: <http://www.w3.org/TR/wai-aria/states_and_properties#aria-hidden> Regards, Maciej
Received on Tuesday, 18 September 2012 21:38:11 UTC