This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Per previous discussion[1], I believe that it is the policy of the editor to remove features that any browser that has notable market share do not intend to support, and then work to come up with solutions that everybody would agree to. table@summary does something in JAWS and some other UAs, but has issues, the PF Working Group hopes to someday completely obsolete it, isn't described in the spec, and any uses produces a warning. keygen does something in Gecko and some other UAs, has issues, likely will never be implemented in IE, the HTML WG hopes to someday completely obsolete it, is described in the spec, and uses currently produce no warning. Per the discussion on issue 53, I believe that table@summary should be described even if is recommended against, but at the very least it seems to me that keygen should get no more favorable treatment than table@summary. Therefore, if table@summary remains as it is, the description for keygen should be removed, and uses of keygen should produce a warning. [1] http://lists.w3.org/Archives/Public/www-archive/2009Jul/0075.html
You forget that <keygen> has no alternative, whereas the summary attribute, as per the specification, does.
HTML5 intentionally provides no alternative "for user agents rendering to non-visual media such as speech and Braille."[2] [2] http://www.w3.org/TR/html401/struct/tables.html#adef-summary
That's not what I meant with alternative.
The summary="" attribute is now described and conforming, as is <keygen>. The summary="" attribute still emits a warning, though, since its use can be detrimental to accessibility, unlike use of the <keygen> element, which is mostly harmless.
This bug predates the HTML Working Group Decision Policy. If you are satisfied with the resolution of this bug, 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 This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.