Hi guys.
I’m the author for the drag and drop article that you’re taking about (sorry for the lag @Stomme_poes, @Mittineague, @John_Betong , I wasn’t getting forum notifications)
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)
Thanks for the feedback / thoughts though guys!