- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Tue, 18 Sep 2012 11:28:39 -0500
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>, 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>
Hi Janina, 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 Best Regards. Laura -- Laura L. Carlson
Received on Tuesday, 18 September 2012 16:29:09 UTC