This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
"summary element No role"
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: refer to https://github.com/w3c/html/commit/943d59922300d6fa2bef6815ba4950f197bbac2e Rationale: the button role is the expected role for the summary element on some platforms, and is the obvious choice for details/summary polyfil http://rawgithub.com/w3c/html-api-map/master/index.html#summary-and-details-elements no good reason to make it non conforming.
I think this change doesn't make sense given how summary is defined. It's like allowing role=button on <video>.
(In reply to Simon Pieters from comment #2) > I think this change doesn't make sense given how summary is defined. It's > like allowing role=button on <video>. I don't agree that the comparison is useful (video/summary) It makes sense for polyfilling implementations (example)[1]. also appears that current implementations (chrome/webkit) do something different to what the spec says (or doesn't say). [1]http://www.html5accessibility.com/CSUN14/details.html
(In reply to Simon Pieters from comment #2) > I think this change doesn't make sense given how summary is defined. It's > like allowing role=button on <video>. also note that previously and now in the html spec implementers can provide any accessibility information they like (no role [1]) all that has been changed is that its conforming for authors to use role=button. [1] http://www.w3.org/html/wg/drafts/html/master/dom.html#concept-role-none
For polyfill I'd recommend inserting a button as a child of summary. As for webkit/blink, that's a bug in the impl. Also see https://www.w3.org/Bugs/Public/show_bug.cgi?id=24835
(In reply to Simon Pieters from comment #5) > For polyfill I'd recommend inserting a button as a child of summary. As for > webkit/blink, that's a bug in the impl. > > Also see https://www.w3.org/Bugs/Public/show_bug.cgi?id=24835 on the related bug i asked the question https://www.w3.org/Bugs/Public/show_bug.cgi?id=25140: Are there any use cases for allowing interactive descendants? are there? As for > webkit/blink, that's a bug in the impl. bug number?
https://code.google.com/p/chromium/issues/detail?id=94384
(In reply to Simon Pieters from comment #7) > https://code.google.com/p/chromium/issues/detail?id=94384 thanks for that.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: partially accepted Change Description: added constraint to conforming usage of button on summary see commit https://github.com/w3c/html/commit/541825211eece40c2ef139fb5305e6601c436ad8 Rationale: agreed with commenter that if the summary element contains interactive content the role=button does not make sense. While by default summary is not classed as interactive content, as it states in the spec "The tabindex attribute can also make any element into interactive content." http://www.w3.org/html/wg/drafts/html/master/dom.html#interactive-content-0 In the case where tabindex is used on summary to make it interactive a role=button is allowed unless the summary contains interactive descendant elements.
*** Bug 24869 has been marked as a duplicate of this bug. ***