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

[Bug 10450] Allow lists to be used as menus or tab sets

From: <bugzilla@jessica.w3.org>
Date: Thu, 30 Sep 2010 09:12:07 +0000
To: public-html-a11y@w3.org
Message-Id: <E1P1FBP-0007wx-Mf@jessica.w3.org>

--- Comment #11 from steve faulkner <faulkner.steve@gmail.com> 2010-09-30 09:12:07 UTC ---
(In reply to comment #10)
> (In reply to comment #9)
> > Works in the way that allows role=tabset to see children of a child that is
> > role=presentation.
> "For any element with a role of presentation and which is not focusable, the
> user agent MUST NOT expose the implicit native semantics of the element (the
> role and its states and properties) to accessibility APIs. However, the user
> agent MUST expose content and descendant elements that do not have an explicit
> or inherited role of presentation. Thus, the presentation role causes a given
> element to be treated as having no role or to be removed from the accessibility
> tree, but does not cause the content contained within the element to be removed
> from the accessible tree."
> From <http://www.w3.org/TR/wai-aria/roles#presentation>
> And this is how WebKit, at least, actually implements it - elements with
> role=presentation are skipped when generating the accessibility tree, so they
> are "transparent" in terms of role parent/child relationships.

This is how it works in firefox and IE as well, the examples I provided
(actually by my colleague hans hillen, who has been working on implementing
ARIA in Jquery UI and Extjs libraries) were not thought experiments, they are
working examples.

Configure bugmail: http://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 Thursday, 30 September 2010 09:12:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:55:44 UTC