This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
http://www.w3.org/mid/B6CB855C5769484F862F4FB2CCFA50F402D545A7@VHAISHMSGJ2.vha.med.va.gov Input Elements Extensive work will need to be done that the new elements have appropriate accessibility for users with disabilities, including keyboard/non-pointer-device accessibility, as well as appropriate indicators of states and attributes that impact how or whether a user can interact with that input element. Although there could be great promise in having a consistent means of providing input elements, accessibility concerns will need to be taken into account when determining how user agents display that information to the user, and expose information to AT. [split out from bug 13590]
Yes, browsers will have to do things correctly. Is there a problem with the HTML spec here?
This bug is waiting on a response from Mia Lipner or somebody else to comment #1: > Yes, browsers will have to do things correctly. Is there a problem with the > HTML spec here?
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: Did Not Understand Request Change Description: no spec change Rationale: see comment 2
Moved to HTML A11y TF component.
For known bugs, please file specific issues on the github issues list http://github.com/w3c/html/issues