- From: James Craig <jcraig@apple.com>
- Date: Thu, 13 Sep 2012 15:31:02 -0700
- To: Janina Sajka <janina@rednote.net>
- Cc: Cynthia Shelly <cyns@microsoft.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>, Ted O'Connor <eoconnor@apple.com>
Does this sufficiently address the Issue 204 discussion from this morning's teleconference? http://www.w3.org/2012/09/13-html-a11y-minutes.html#item01 On Sep 13, 2012, at 3:18 PM, James Craig <jcraig@apple.com> wrote: > How about this take? > > Note: Only hidden="" elements that are referenced indirectly by a unique identifier (ID) reference or valid hash-name reference may have their structure and content exposed upon user request. Authors desiring to prevent user-initiated viewing of hidden="" elements should remove identifier (ID) or hash-name references to the element. > > > On Sep 13, 2012, at 2:51 PM, James Craig <jcraig@apple.com> wrote: > >> Janina, >> >> I don't have substantive objections with either of these, and only minor editorial objections to tense and style. >> >> James >> >> >> Cynthia's >>>> 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. >> >> Janina's: >> >>> Author control, as opposed to user control over whether elements with the @hidden attribute may be exposed to users will be delineated in this manner. Only elements that are referenced indirectly by a unique identifier (ID) reference or valid hash-name reference may be exposed at user request. An author desiring to keep a @hidden element hidden from any and all user initiated viewing scenarios may achieve this by simply not referencing the element. >> >> >
Received on Thursday, 13 September 2012 22:32:00 UTC