This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16538 - aria mapping for details and summary are problematic
Summary: aria mapping for details and summary are problematic
Status: RESOLVED INVALID
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, aria
Depends on:
Blocks:
 
Reported: 2012-03-27 15:59 UTC by steve faulkner
Modified: 2012-04-03 18:13 UTC (History)
4 users (show)

See Also:


Attachments

Description steve faulkner 2012-03-27 15:59:36 UTC
The details element has a default implied role of group and a restriction that "Role must be a role that supports aria-expanded"
http://dev.w3.org/html5/spec/wai-aria.html#wai-aria

The 'group' role cannot have aria-expanded attribute applied. Roles that can are button, document, link, separator and window. None of which appear appropriate for the details element.

What is specified for details would be more appropriate for the summary element. As in implementations (webkit/chrome) this is the interactive element and is most likely to be implemented as a button in some API's that don't have a disclousre triangle role.

Recommend  removing summary form the first table and changing the row in the second table that lists details under "Language feature" to the summary element, leaving all the rest of the text that pertianed to details the same.

Recommend adding 'details' to the first table with a default implied role of "group"
Comment 1 steve faulkner 2012-04-03 18:13:48 UTC
my bad, misreading of the ARIA spec, so closing bug. still think the details/summary element mappings need tweaking, will file a new bug.