Good question. For me, I’m almost always a mouser, and unfortunately that often means I need to make a conscious effort to even begin considering keyboard use.
TBH I’ve never thought of “drag drop” as being a keyboard thing. That is, more of an “enhancement” for those that could, while (hopefully) not being essential for those that couldn’t.
Mobiles and tablet usage is increasing daily so designers should ultimately test on portables rather than just dragging a sidebar on their ginormous screens and feel proud that the page is responsive.
This response is from a tablet. Selecting text and trying to select a username from a popup that disappears off the screen is not easy.
Also as mentioned numerous times zoom is disabled…
Ironically the article zooming works but not on this forum?
I’m pretty sure the low-ish barrier of creating Yet Another Account gets many people missing that opportunity.
However I’m also aware that it’s a sane response to butt-loads of spam.
I’m just surprised that basics of web standards aren’t even mentioned in the article (like, “These examples are purely mouse-based, but keyboard is an important input device that shouldn’t be forgotten, Sitepoint has another article focussing on that [link-to-brothercake over here]” or something.
For you and many other developers-- so it helps them do the right thing in following web standards if they at least get reminded of it when learning new stuff.
Looking at brothercake’s article, it sure looks like it’s more work at the moment. It does still use the native HTML5 API, just adds some other things on top of it. So I’d call it “Modified HTML5 Drag and Drop”.
In any case, I don’t necessarily expect the author of the more recent article to add in all the keyboard stuff, as it’s trying to stick more to the basics of the API, but I do expect a mention and maybe a link to the other SitePoint article.
In regards to drag, drop and accessibility overall my article’s primary focus was on how to use the native drag and drop functionality to handle data collection and manipulation.
Traditionally, the main focus on drag and drop has been with devices that are capable of dragging and dropping easily such as mice. The native API introduces several moderately complex concepts and outlining them along with additional factors to make it work on keyboards / other accessibility enabled devices would have made the article overly complex.
I actually looked into the process of adding support for the varying aria roles and elements but overall I felt the core concepts would get lost.
On another note the support for the native API on mobile is actually non existent so I don’t even think of mentioning that the examples and concepts won’t work on them (you could perhaps polyfill them with jQuery UI but considering most of them interact with the “data” of objects it might be a bit of a waste)
“In any case, I don’t necessarily expect the author of the more recent article to add in all the keyboard stuff, as it’s trying to stick more to the basics of the API, but I do expect a mention and maybe a link to the other SitePoint article.”
And when there are limits on an API (such as keyboard and mobiles/touch), the first paragraph could mention these facts. As a reminder to developers who are googling these things.