25135 2014-03-24 13:05:38 +0000 allow summary to have role=button 2014-05-12 12:59:53 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC Windows NT RESOLVED FIXED CR P2 normal --- 1 faulkner.steve dave.null mike public-html-admin public-html-wg-issue-tracking zcorpan public-html-bugzilla oldest_to_newest 102820 0 faulkner.steve 2014-03-24 13:05:38 +0000 "summary element No role" 102821 1 faulkner.steve 2014-03-24 13:17:14 +0000 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. 102917 2 zcorpan 2014-03-26 11:35:56 +0000 I think this change doesn't make sense given how summary is defined. It's like allowing role=button on <video>. 102919 3 faulkner.steve 2014-03-26 11:56:50 +0000 (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 102922 4 faulkner.steve 2014-03-26 13:20:44 +0000 (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 102926 5 zcorpan 2014-03-26 16:38:41 +0000 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 102930 6 faulkner.steve 2014-03-26 16:54:32 +0000 (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? 102995 7 zcorpan 2014-03-27 11:52:46 +0000 https://code.google.com/p/chromium/issues/detail?id=94384 103073 8 faulkner.steve 2014-03-28 09:19:10 +0000 (In reply to Simon Pieters from comment #7) > https://code.google.com/p/chromium/issues/detail?id=94384 thanks for that. 103448 9 faulkner.steve 2014-04-05 14:48:49 +0000 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. 105718 10 faulkner.steve 2014-05-12 12:59:53 +0000 *** Bug 24869 has been marked as a duplicate of this bug. ***