- From: Jon Gunderson <jongund@illinois.edu>
- Date: Thu, 11 Sep 2008 12:34:43 -0500 (CDT)
- To: James Craig <jcraig@apple.com>, David Bolter <david.bolter@utoronto.ca>
- Cc: Aaron M Leventhal <aleventh@us.ibm.com>, Cynthia Shelly <cyns@exchange.microsoft.com>, George Young <gcyoung@microsoft.com>, W3C WAI-XTECH <wai-xtech@w3.org>
The major problem with nesting is focus management and the use of simple styling techniques ti highlight the active leaf, since from my understanding the element that receives keyboard focus must also have the role values. The nesting can be done using "aria-activedescendant", maybe aria-labelledby and probably the new "aria-label". A question that I have is when labelledby is used will it only use the content pointed to by the IDs, or will the browser also use the text node content to add to the name. In the tree view that uses nested lists it seems that it should not add any child text node content, but in some type other widgets like grids it might be convenient to have id added content concatenated to the text content of the gridcell. Jon >1. Nesting each subtree group inside its parent list item would allow this to be used with the existing structure of nested UL/LI in HTML,without the need for additional sub-level inline elements like the SPAN or A tags we have in all the examples to date. > 2. Nesting each subtree group inside its parent list item would allow aria-level to be automatically calculated by the user agent. This could lead to making aria-level optional in the same way aria-setsize and aria-posinset are currently optional unless the DOM is only showing a subset of the full tree. Jon Gunderson, Ph.D. Coordinator Information Technology Accessibility Disability Resources and Educational Services Rehabilitation Education Center Room 86 1207 S. Oak Street Champaign, Illinois 61821 Voice: (217) 244-5870 WWW: http://www.cita.uiuc.edu/ WWW: https://netfiles.uiuc.edu/jongund/www/
Received on Thursday, 11 September 2008 17:36:34 UTC