7044 Kkk2 2009-06-22 15:47:01 +0000 [ARIA 2.0] Work with browser vendors to come up with convention for forward compatibility of ARIA states and properties 2016-01-19 18:51:06 +0000 1 1 1 Unclassified ARIA General 1.0 PC Windows XP RESOLVED WONTFIX P3 normal --- 1 andi.snowweaver cyns andi.snowweaver karlwolf1983 kaungchaint aria-ua-impl oldest_to_newest 25639 0 andi.snowweaver 2009-06-22 15:47:01 +0000 From section 3.5, bullet # 5: "For forward compatibility with new ARIA properties in future versions, user agents SHOULD expose all properties not in this table with an object attribute, removing the "ari-" prefix from the name." 37143 1 andi.snowweaver 2010-07-28 17:13:11 +0000 From Gez: Hi Gregory, Thank you so much for picking up this issue. I think it's clear that although the HTML5 specification states that the drag and drop mechanism should be device independent, it's reverse engineered from a mouse-based implementation, and the order of states required to complete a drag and drop implementation couldn't possibly completed using the keyboard alone. Like you, I would like to see the current drag and drop mechanism altered so that it can be implemented in a device independent way. If the copy and paste API is required to make this work, it will need to be amended so that it fits with the workflow defined in the WAI-ARIA authoring practices document - for example, identifying draggable objects and explaining the effect of dropping the source on a target. 37146 2 andi.snowweaver 2010-07-28 17:15:50 +0000 Please ignore comments I posted in from Gez. These were meant for 6912. 96187 3 jcraig 2013-11-12 18:40:11 +0000 *** Bug 23301 has been marked as a duplicate of this bug. *** 124637 4 cyns 2016-01-19 18:51:06 +0000 I think this is overcome by events