This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In the section discussing dropzone (http://www.w3.org/TR/2011/WD-html5-20110525/dnd.html#dnd) there needs to be more instruction for user agents as to what roles/states need to be assigned to dropzone areas. User agents shouldn't be left guessing about how to communicate with accessibility APIs related to drag and drop areas. It is necessary to indicate to users that an area is available to drop content being dragged, and the way to accomplish this is not defined in the spec.
Assigning to Cynthia to work out details for this bug in the AAPI mapping sub-group of the HTML A11Y TF.
mass-moved component to LC1
Adding the "needsinfo" keyword since resolution of this bug is waiting on action from the AAPI mapping subteam of the HTML a11y TF (not waiting on the editor)
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: Given that we've been waiting almost a year for the relevant info, I think we should plan to address this in HTML.next.
HTML A11Y TF has said we don't need to track drag and drop bugs because they were filed before an overhaul of that part of the spec, but will review that part of the spec again.