29600 2016-04-28 08:28:00 +0000 Focus and Keyboard Interaction with details and summary 2018-05-03 21:20:42 +0000 1 1 1 Unclassified ARIA HTML AAM 1.0 PC All RESOLVED INVALID P2 normal --- 1 je00julie.kim faulkner.steve jason surkov.alexander oldest_to_newest 126251 0 je00julie.kim 2016-04-28 08:28:00 +0000 I think aria spec and html spec are inconsistent. http://w3c.github.io/aria/html-aam/html-aam.html#summary-and-details-elements "6.1 summary and details Elements 6.1.1 Focus and Keyboard Interaction The summary element should be focusable by default. The details element should not focusable by default. Pressing the spacebar or enter key when the summary element has focus will show the details element content if the content is hidden. If the details element content is showing and the summary element has focus, pressing the spacebar or enter key will hide the details element content." https://html.spec.whatwg.org/multipage/dom.html#interactive-content "3.2.4.2.7 Interactive content Interactive content is content that is specifically intended for user interaction. a (if the href attribute is present)audio (if the controls attribute is present)buttondetailsembediframeimg (if the usemap attribute is present)input (if the type attribute is not in the Hidden state)keygenlabelobject (if the usemap attribute is present)selecttextareavideo (if the controls attribute is present) The tabindex attribute can also make any element into interactive content." ARIA spec says that summary element should be focusable but HTML spec says that details element, not summary, is an interactive content. I'm working on chromium AX as an external contributor, there is a bug report, https://bugs.chromium.org/p/chromium/issues/detail?id=389461#c6, related to event handling with details and summary elements. Please take a look. 129218 1 w3cbugzilla 2018-05-03 21:20:42 +0000 HTML AAM is no longer an ARIA Deliverable. If you wish to pursue this issue please file at https://github.com/w3c/html-aam/issues