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

additional sentence for 204

From: Cynthia Shelly <cyns@microsoft.com>
Date: Thu, 13 Sep 2012 20:36:29 +0000
To: HTML Accessibility Task Force <public-html-a11y@w3.org>, "James Craig (jcraig@apple.com)" <jcraig@apple.com>
Message-ID: <0be96675b1cf4895a8a43d844d5dad25@CH1PR03MB600.namprd03.prod.outlook.com>
At the html-a11y tf meeting this morning, I was asked to propose some text to make it clear that authors have control over whether @hidden elements will be exposed to users via accessibility APIs.  It's pretty clear in the existing text, in the 2nd paragraph, that this exposure only applies to elements that are referenced by another element.

<blockquote>
User Agents may thus expose the full semantics of hidden elements to Assistive Technology when appropriate, if such content is referenced indirectly by a unique identifier (ID) reference or valid hash-name reference.
</blockquote>

I propose that we add a note after the 2nd paragraph to clarify the author's control over this.  This text needs some word-smithing, but I think it conveys the idea.

<proposal>
Note:
Authors have control over whether elements with the @hidden attribute will be exposed in this manner.  Only elements that are is referenced indirectly by a unique identifier (ID) reference or valid hash-name reference will be exposed.  If an author does not wish to have a @hidden element exposed, he may achieve this by not referencing the element.
</proposal>

Or something like that...
Received on Thursday, 13 September 2012 20:37:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 September 2012 20:37:20 GMT