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

https://www.w3.org/Bugs/Public/show_bug.cgi?id=18744

--- Comment #9 from Edward O'Connor <eoconnor@apple.com> 2012-09-08 03:01:10 UTC ---
Here's some new text that addresses both the jurisdiction issue captured in
this bug and the technical precision issue of bug 18745. I'm pretty happy with
how this addresses the various technical issues that have been raised. Looking
forward to finding out what people think!



Accessibility APIs are encouraged to allow a way to expose structured
content while marking it as hidden in the default view. Such content
should not be perceivable to users in the normal document flow in any
modality, whether using Assistive Technology or mainstream User Agents.

When such features are available, User Agents may thus expose the full
semantics of hidden="" elements to Assistive Technology when
appropriate, if such content is referenced indirectly by an ID reference
or hash-name reference. This allows Assistive Technologies to access the
content structure upon user request, while keeping the content hidden in
all presentations of the normal document flow. Some examples of where it
would be appropriate for the structure of hidden="" elements to be
exposed to users of AT with such an API include:

 * a <map> referenced from <img usemap>
 * table headers referenced with the headers="" attribute

Cases where it would be inappropriate include

 * <a href> containing a hash name reference to a hidden="" element in
   the same document
 * <label for> referencing a hidden="" form element

Other specifications which define elements and attributes which may be
included in valid HTML documents (such as SVG, MathML, and WAI-ARIA) may
define how or whether this applies to their elements and attributes.

-- 
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 Saturday, 8 September 2012 03:01:11 UTC