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

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10450

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #19 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-10-14 10:18:21 UTC ---
Maciej did some digging in the ARIA specs and found the following:

1. It seems like the relationship between tab and tablist is mediated by the
"owned element" concept, which applies to any DOM descendant:
   http://www.w3.org/TR/2010/WD-wai-aria-20100916/terms#def_owned_element
Thus, role=presentational isn't needed according to the ARIA spec to achieve
the effect described above.

However:
2. It is required to prevent the role of the list item itself being present.
This is a different use case than described above, but a relevant one
nonetheless. That is, the role=presentation is not in theory required to get
the ownership relation right, but it is required to avoid redundant content in
the accessibility tree.

However:
3. This means that any list will contain _all_ of its descendant list items,
even those owned by nested lists, which is clearly a bug in ARIA.

Futhermore:
4. The implementation guide:
   http://www.w3.org/WAI/PF/aria-implementation/>
...says that the role mappings are such that random DOM descendants (with
non-presentation-role intermediate elements) will not get hooked up correctly
(as according to the ARIA spec). Therefore, the use case described previously
here _does_ apply according to the implementation guide (but not the ARIA
spec).

The remaining issue in this bug therefore seems to be handled by bug 10919.
I'll fix it there and am returning this bug to the FIXED state as per comment
1.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 14 October 2010 10:18:24 UTC