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

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

From: <bugzilla@jessica.w3.org>
Date: Sat, 08 Sep 2012 07:11:39 +0000
Message-Id: <E1TAFCd-0005wW-Vu@jessica.w3.org>
To: public-html-a11y@w3.org

--- Comment #10 from Joshue O Connor <joshue.oconnor@cfit.ie> 2012-09-08 07:11:39 UTC ---
Thanks for that Edward. One of the issues that I am interested in is with the
use of HTML content being hidden via the CSS declaration <display:none> etc.
While this may be an issue for the CSS WG, there are many times where text
strings hidden using this method can be of use to screen reader users and a way
of showing/hiding this using ARIA 'as an override' to the CSS declaration -
would be great. If it already exists if someone would point out a best practice
example to me, I'd appreciate it. It may be a UA issue, and just a matter of
joining the dots with an appropriate method.

(In reply to comment #9)
> Here's some new text that addresses both the jurisdiction issue captured in
> this bug and the technical precision issue of bug 18745.[....]

> 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.

While I don't agree with Johns stance on this issue, he does bring some
interesting points (as usual ;-)

I'm not sure I know what 'normal' document flow means - the paragraph may
benefit from removing the reference and rewriting it to:

"Such content should not be perceivable to users 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

I'm not sure I understand the use case of the latter example. If table headers
exist - why would they be hidden? If there is a valid use case then please let
us know.

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 07:11:41 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:30 UTC