ISSUE-1035: Are additional roles or properties needed to help authors build interactive list and tree structures with complex items?

Complex lists and tree widgets

Are additional roles or properties needed to help authors build interactive list and tree structures with complex items?

State:
CLOSED
Product:
ARIA 2.0
Raised by:
Matthew King
Opened on:
2016-06-09
Description:
Authors need to be able to create list and tree structures that present complex children. For example, a list of search results where each result includes multiple focusable children in addition to other rich semantic information. It is also desirable that such structures function as a composite widget, i.e., the entire structure is a single tab stop and it is possible to navigate the list with the arrow keys.

Assistive technologies and most browsers treat option and treeitem elements as static; their children are treated as if they are presentational and their content is stringified when they are read by screen readers. The option role is used to represent an HTML option, which is not allowed to have interactive children.

ARIA 1.1 includes changes to grid so it can be used to create interactive lists and trees that contain composite items. The gridcell is a container that reveals the semantics of its children.

However, concerns remain that grid does not adequately support the needs of authors. See discussion in June 9, 2016 ARIA caucus:
http://www.w3.org/2016/06/09-aria-minutes.html
Related Actions Items:
No related actions
Related emails:
No related emails

Related notes:

[mck]: Are additional roles or properties needed to help authors build interactive list and tree structures with complex items? - Accessible Rich

9 Jun 2016, 18:02:59

Changelog:

Created issue 'Are additional roles or properties needed to help authors build interactive list and tree structures with complex items?' nickname Complex lists and tree widgets owned by Matthew King on product ARIA 2.0, description 'Authors need to be able to create list and tree structures that present complex children. For example, a list of search results where each result includes multiple focusable children in addition to other rich semantic information. It is also desirable that such structures function as a composite widget, i.e., the entire structure is a single tab stop and it is possible to navigate the list with the arrow keys.

Assistive technologies and most browsers treat option and treeitem elements as static; their children are treated as if they are presentational and their content is stringified when they are read by screen readers. The option role is used to represent an HTML option, which is not allowed to have interactive children.

ARIA 1.1 includes changes to grid so it can be used to create interactive lists and trees that contain composite items. The gridcell is a container that reveals the semantics of its children.

However, concerns remain that grid does not adequately support the needs of authors. See discussion in June 9, 2016 ARIA caucus:
http://www.w3.org/2016/06/09-aria-minutes.html
' non-public

Matthew King, 9 Jun 2016, 17:56:54

Status changed to 'closed'

James Nurthen, 3 May 2018, 19:42:22


Joanmarie Diggs <jdiggs@igalia.com>, James Nurthen <nurthen@adobe.com>, Chairs, Michael Cooper <cooper@w3.org>, Ruoxi Ran <ran@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $