Comments on: Accessibility & Native Drag and Drop http://html5doctor.com/accessibility-native-drag-and-drop/ helping you implement HTML5 today Thu, 11 Mar 2010 20:04:25 -0800 http://wordpress.org/?v=2.9.2 hourly 1 By: Collection of HTML5 Resources to Move You Forward http://html5doctor.com/accessibility-native-drag-and-drop/comment-page-1/#comment-1556 Collection of HTML5 Resources to Move You Forward Wed, 04 Nov 2009 14:45:40 +0000 http://html5doctor.com/?p=603#comment-1556 [...] Accessibility & Native Drag and Drop [...] [...] Accessibility & Native Drag and Drop [...]

]]> By: Rich Schwerdtfeger http://html5doctor.com/accessibility-native-drag-and-drop/comment-page-1/#comment-951 Rich Schwerdtfeger Sun, 13 Sep 2009 21:11:23 +0000 http://html5doctor.com/?p=603#comment-951 Gez, Nice article, but there are problems with this approach: * It does not include drop by link (an HTML 5 feature). * What if the application does not want to support a cut (which I would assume you would do in the case of a move)? * It prevents the mobility impaired user from being able to see all the grabbed items (visible only with the mouse pointer). The question I have is why the same script functions called in response to mouse activity could not be used for the keyboard implementer. If you were to take out the mouse pointer position information you virtually use the same HTML 5 utilities in the keyboard implementation. Gez,

Nice article, but there are problems with this approach:

* It does not include drop by link (an HTML 5 feature).
* What if the application does not want to support a cut (which I would assume you would do in the case of a move)?
* It prevents the mobility impaired user from being able to see all the grabbed items (visible only with the mouse pointer).

The question I have is why the same script functions called in response to mouse activity could not be used for the keyboard implementer. If you were to take out the mouse pointer position information you virtually use the same HTML 5 utilities in the keyboard implementation.

]]> By: alex http://html5doctor.com/accessibility-native-drag-and-drop/comment-page-1/#comment-776 alex Mon, 17 Aug 2009 20:58:04 +0000 http://html5doctor.com/?p=603#comment-776 Hi remy, very nice article, wich will improve the correct, accessible implementation of HTML 5. Firefox 3.6 will also add ARIA-Semantics automaticly, if you use HTML5 draggable (https://bugzilla.mozilla.org/show_bug.cgi?id=477599). i think, Firefox will make it right. if you only use a native browser-feature, you shouldn´t even have to add aria-semantics. aria should be used for features, wich are implemented by an author. if the browser vendor introduces a new feature (an HTML 5 element, DOM-Interface etc.), he is the first responsible to make it accessible. regards alex Hi remy,

very nice article, wich will improve the correct, accessible implementation of HTML 5.

Firefox 3.6 will also add ARIA-Semantics automaticly, if you use HTML5 draggable (https://bugzilla.mozilla.org/show_bug.cgi?id=477599).

i think, Firefox will make it right. if you only use a native browser-feature, you shouldn´t even have to add aria-semantics. aria should be used for features, wich are implemented by an author. if the browser vendor introduces a new feature (an HTML 5 element, DOM-Interface etc.), he is the first responsible to make it accessible.

regards
alex

]]> By: Jonny Axelsson http://html5doctor.com/accessibility-native-drag-and-drop/comment-page-1/#comment-351 Jonny Axelsson Mon, 27 Jul 2009 10:54:47 +0000 http://html5doctor.com/?p=603#comment-351 A nice article, but one concern I have is how the native support and scripted support should interact. When these are in conflict which one will win? Will the user lose? I put my thoughts down here: http://my.opera.com/jax/blog/can-html5-make-accessibility-usable A nice article, but one concern I have is how the native support and scripted support should interact. When these are in conflict which one will win? Will the user lose? I put my thoughts down here: http://my.opera.com/jax/blog/can-html5-make-accessibility-usable

]]> By: danjam http://html5doctor.com/accessibility-native-drag-and-drop/comment-page-1/#comment-329 danjam Sat, 25 Jul 2009 08:26:14 +0000 http://html5doctor.com/?p=603#comment-329 I've been reporting IE bugs here - https://connect.microsoft.com/IE/Feedback Although I suspect Shaun's method may be faster. I’ve been reporting IE bugs here – https://connect.microsoft.com/IE/Feedback

Although I suspect Shaun’s method may be faster.

]]> By: Brian Campbell http://html5doctor.com/accessibility-native-drag-and-drop/comment-page-1/#comment-322 Brian Campbell Fri, 24 Jul 2009 14:03:49 +0000 http://html5doctor.com/?p=603#comment-322 @Remy – I can't tell you that; it could mean either. You'd have to ask someone from Apple, who has access to Radar, to clarify that. @Remy – I can’t tell you that; it could mean either. You’d have to ask someone from Apple, who has access to Radar, to clarify that.

]]> By: Remy Sharp http://html5doctor.com/accessibility-native-drag-and-drop/comment-page-1/#comment-319 Remy Sharp Fri, 24 Jul 2009 08:39:10 +0000 http://html5doctor.com/?p=603#comment-319 @Thomas - the demo is using <em>native</em> drag and drop, whereas Gez's example is pure/old school JavaScript. The obvious downside to the native version is it's not supported in Opera 10. The article was more to show how to implement accessibility to the native version of drag and drop. This however, does beget an article showing you how you should fail down (though perhaps it's just a case of testing to see if you can create a drag event, and if not, rely on the JavaScript driven DnD). @Brian - Thanks for clarifying on the radar bug - does that mean that they had it already, or they've added it to their system? @Thomas – the demo is using native drag and drop, whereas Gez’s example is pure/old school JavaScript. The obvious downside to the native version is it’s not supported in Opera 10. The article was more to show how to implement accessibility to the native version of drag and drop. This however, does beget an article showing you how you should fail down (though perhaps it’s just a case of testing to see if you can create a drag event, and if not, rely on the JavaScript driven DnD).

@Brian – Thanks for clarifying on the radar bug – does that mean that they had it already, or they’ve added it to their system?

]]> By: Brian Campbell http://html5doctor.com/accessibility-native-drag-and-drop/comment-page-1/#comment-315 Brian Campbell Thu, 23 Jul 2009 21:30:21 +0000 http://html5doctor.com/?p=603#comment-315 @Remy – The comment on the WebKit bug is just an indication that they have the same bug filed in Apple's internal bugtracker, radar (that's what the ‘rdar:’ URL means). I hope the browser vendors implement copy and paste for drag events soon; drag and drop on its own is a serious accessibility nightmare. I know people in their 20s who have no disabilities, went to Ivy league universities, and have used computers for years, who still cannot drag and drop (or at the very least don't think of it when using an interface), but who can copy and paste. I implement interactive multimedia that had drag and drop activities for sorting items, and we discovered that our users (doctors and nurses) had serious problems with those activities, so most of them we changed to having our virtual mentor pick one item at a time, and the user clicks where it goes. I hope that when copy and paste support is added to drag and drop in the browsers, users will also be able to select dragabble elements with their mouse, with a single click, just like you select items in a list or icons on the desktop. I have encountered users who do not know how to focus elements with a keyboard or copy and paste using keyboard, but instead do everything with the mouse. @Remy – The comment on the WebKit bug is just an indication that they have the same bug filed in Apple’s internal bugtracker, radar (that’s what the ‘rdar:’ URL means).

I hope the browser vendors implement copy and paste for drag events soon; drag and drop on its own is a serious accessibility nightmare. I know people in their 20s who have no disabilities, went to Ivy league universities, and have used computers for years, who still cannot drag and drop (or at the very least don’t think of it when using an interface), but who can copy and paste. I implement interactive multimedia that had drag and drop activities for sorting items, and we discovered that our users (doctors and nurses) had serious problems with those activities, so most of them we changed to having our virtual mentor pick one item at a time, and the user clicks where it goes.

I hope that when copy and paste support is added to drag and drop in the browsers, users will also be able to select dragabble elements with their mouse, with a single click, just like you select items in a list or icons on the desktop. I have encountered users who do not know how to focus elements with a keyboard or copy and paste using keyboard, but instead do everything with the mouse.

]]> By: Thomas Scholz http://html5doctor.com/accessibility-native-drag-and-drop/comment-page-1/#comment-314 Thomas Scholz Thu, 23 Jul 2009 20:32:37 +0000 http://html5doctor.com/?p=603#comment-314 How does it work? In contrast to Gez Lemon’s example I can’t find anything to drag in Opera 9 and 10 in yours. Did I miss something? How does it work? In contrast to Gez Lemon’s example I can’t find anything to drag in Opera 9 and 10 in yours. Did I miss something?

]]> By: Remy Sharp http://html5doctor.com/accessibility-native-drag-and-drop/comment-page-1/#comment-312 Remy Sharp Thu, 23 Jul 2009 16:00:10 +0000 http://html5doctor.com/?p=603#comment-312 @Emil - cheers, looks like there's a few hoops I'll have to jump through to get the bug listed. @Shaun - I think you just listed the hoops :-D @Emil – cheers, looks like there’s a few hoops I’ll have to jump through to get the bug listed.

@Shaun – I think you just listed the hoops :-D

]]>