This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
"The button element represents a button. If the element is not disabled, then the user agent should allow the user to activate the button. change the should in this sentence to MUST. Users must be able to activate any non-disabled button.
You cannot activate them in all media. Or e.g. when it is not displayed on the screen.
mass-move component to LC1
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: Rejected Change Description: no spec change Rationale: see comment 1.
Can you list the other cases (besides being disabled) where the button can't be activated, so this can be a must? Being activated is the point of buttons, and non-activatable buttons will be a problem for AT and for users with cognitive issues.
(In reply to comment #4) > Can you list the other cases (besides being disabled) where the button can't be > activated, so this can be a must? Being activated is the point of buttons, and > non-activatable buttons will be a problem for AT and for users with cognitive > issues. If I understand Anne's comment 1 correctly, what he meant is, you can't activate a button in, e.g., @media print.
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: Rejected Change Description: no spec change Rationale: Indeed. Or if the user agent is any other kind of non-interactive medium (e.g. an electronic billboard).
I meant, can you list other cases, such as print media, IN THE SPEC?
HTML A11Y TF Bug Triage sub-team notes that there seems to be agreement that there are use cases for not taking the original suggestion up, but what hasn't been closed is putting these use cases into the spec so there won't be further misunderstandings. Re-opening to request editor to put explanations in the spec.
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: works for me Change Description: no spec change Rationale: the cited text is no longer in HTML 5.1 and I could not find anything similar.