13734 2011-08-10 03:32:03 +0000 new input element types and accessibility 2016-04-14 14:09:24 +0000 1 1 1 Unclassified HTML WG HTML a11y Task Force unspecified PC All RESOLVED INVALID http://www.w3.org/mid/B6CB855C5769484F862F4FB2CCFA50F402D545A7@VHAISHMSGJ2.vha.med.va.gov a11y P2 normal --- 13590 1 mike contributor chaals ian jackalmage laura.lee.carlson lwatson mike public-html-a11y public-html-admin public-html-wg-issue-tracking dave.null oldest_to_newest 54571 0 mike 2011-08-10 03:32:03 +0000 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] 54600 1 jackalmage 2011-08-10 15:10:01 +0000 Yes, browsers will have to do things correctly. Is there a problem with the HTML spec here? 60238 2 mike 2011-11-20 18:16:59 +0000 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? 60447 3 ian 2011-11-24 21:39:04 +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: Did Not Understand Request Change Description: no spec change Rationale: see comment 2 108376 4 lwatson 2014-06-26 11:31:07 +0000 Moved to HTML A11y TF component. 125843 5 chaals 2016-04-14 14:09:24 +0000 For known bugs, please file specific issues on the github issues list http://github.com/w3c/html/issues