just read the blog post and wondered if this can be used with keyboard (alone) and it seems that it can't be.
In the demo I've also seen that everything is made with div and p elements.
I suggest adding at least some basic keyboard support and better semantics.
Don't have the time to make a pull request at the moment, but I will provide some tips here:
Basically we need to add better semantics for keyboard and screen-reader users
(using ordered list with buttons that have proper ARIA attributes would go a long way).
Hi there,
just read the blog post and wondered if this can be used with keyboard (alone) and it seems that it can't be.
In the demo I've also seen that everything is made with
divandpelements.I suggest adding at least some basic keyboard support and better semantics.
Don't have the time to make a pull request at the moment, but I will provide some tips here:
Basically we need to add better semantics for keyboard and screen-reader users (using ordered list with buttons that have proper ARIA attributes would go a long way).
Please check https://pressbooks.library.torontomu.ca/wafd/chapter/sortable-lists/ for simple implementation or https://www.tpgi.com/the-road-to-accessible-drag-and-drop-part-1/ for some more advanced things.