This Wiki page is edited by participants of the HTML Accessibility Task Force. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Task Force participants, WAI, or W3C. It may also have some very useful information.
Spec Review/Drag and Drop
Under review:
Note reference to Drag and Drop in Focus#HTML5.
Contents
Comments from NV Access (Mick Curran)
"I have read through both, and nothing bad jumps out at me accessibility-wise. Of course though we are really only qualified to look from a screen reader perspective.
<SNIPPED>Neither of these sections, and therefore I assume the entire document, mentions ARIA or accessibility specifically, so I guess these points should be left up to the Browser and other accessibility-specific documents."
The drag and drop section is probably closer to home for us. But having read it, I feel that everything is covered. At least from a DOM point of view anyway. I'm not sure if it is the job of that document to mention things like the fact that the draggable attribute should be mapped to an accessibility API rather identical to how the ARIA drag and drop properties are?
Andrew Kirkpatrick
Drag and drop on systems that have pointing devices
The Drag and Drop description around pointing devices is too restrictive and suggests that browsers only need to support non-mouse operations on devices without a mouse. This functionality needs to be available for obligatory keyboard users even on systems that support a mouse.
Current: 7.7 Drag and Drop: On media without a pointing device, the user would probably have to explicitly indicate his intention to perform a drag-and-drop operation, stating what he wishes to drag and where he wishes to drop it, respectively.
Recommend change to: “Drag and drop operations must be able to be accomplished without a pointing device. The user would probably have to explicitly indicate his intention to perform a drag-and-drop operation, stating what he wishes to drag and where he wishes to drop it, respectively.”
AAPI support for dropzone state
Is there an ability within IA2 or other APIs to support the "dropzone" state, so as to indicate to users that an area is available to drop content being dragged?