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 13291 - it doesn't make sense for <button> to be exposed as a link or radio button; it would just confuse users told to "click the button"
Summary: it doesn't make sense for <button> to be exposed as a link or radio button; i...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Cynthia Shelly
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords: a11y, a11ytf, aria
Depends on:
Blocks:
 
Reported: 2011-07-18 21:50 UTC by contributor
Modified: 2011-12-20 17:00 UTC (History)
8 users (show)

See Also:

Attachments

Description contributor 2011-07-18 21:50:59 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete.html
Multipage: http://www.whatwg.org/C#table-aria-weak
Complete: http://www.whatwg.org/c#table-aria-weak

Comment:
it doesn't make sense for <button> to be exposed as a link or radio button; it
would just confuse users told to "click the button"

Posted from: 216.239.45.4 by ian@hixie.ch
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.803.0 Safari/535.1
Comment 1 Michael[tm] Smith 2011-08-04 05:02:13 UTC 
mass-moved component to LC1
Comment 2 Ian 'Hixie' Hickson 2011-08-10 01:11:37 UTC 
It would also be confusing for it to be a checkbox menu item.
Comment 3 Ian 'Hixie' Hickson 2011-09-23 19:43:19 UTC 
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: see diff given below
Rationale: Concurred with reporter's comments.
Comment 4 contributor 2011-09-23 19:46:40 UTC 
Checked in as WHATWG revision r6574.
Check-in comment: tweak authoring conformance requirements to prevent some meaningless combinations
http://html5.org/tools/web-apps-tracker?from=6573&to=6574