Drag and drop functionality unavailable to keyboard or touchscreen

[anevins]

Moved from the WPCampus accessibility report issues on GitHub, see ​https://github.com/WordPress/gutenberg/issues/15316

• Severity:
  • Low
• Affected Populations:
  • Blind
  • Motor Impaired
• Platform(s):
  • All / Universal
• Components affected:
  • Edit Media

Issue description
The Edit Media interface* includes the ability to re-arrange the boxes by
drag and drop, however this can only be achieved by mouse users, since
the functionality does not support touch or keyboard users.

Users of touchscreens and keyboards cannot re-order the boxes. Speech
recognition users may be able to if they can manipulate the mouse with
speech (such as using Mouse Move), however this is onerous and
difficult.

Remediation Guidance
Allow keyboard and touchscreen users the ability to re-arrange the
boxes. This can either be done with dedicated buttons, such as are used
within Gutenberg for moving Blocks; or it could be done by extending
drag and drop support to keyboard and touch users (a good example of
which is dragondrop: ​https://schne324.github.io/dragon-drop/demo/).

Relevant standards

• 2.1.1 Keyboard (Level A) ​https://www.w3.org/TR/WCAG20/#keyboard-operation-keyboard-operable

Note: This issue may be a duplicate with other existing accessibility-related bugs in this project. This issue comes from the Gutenberg accessibility audit, performed by Tenon and funded by WP Campus. This issue is GUT-80 in Tenon's report

*Original issue description and screenshot are available at page 142 of the complete technical report PDF. However, the screenshot appears to be related to the edit post screen in the classic editor.
​https://github.com/WordPress/gutenberg/issues/15316#issuecomment-489460963

[afercia]

Previously: #39074.

[antpb]

This ticket was discussed in the recent media meeting and it was determined that the scope of this issue is wider than the edit media page. While this page certainly has the issue of no clear way to move boxes, the problem exists with every form of meta boxes.

There is an existing issue that more globally addresses this problem here: https://core.trac.wordpress.org/ticket/39074

The information in this media focused ticket is more detailed with suggestions to solving this. I’ll copy over the important bits and close this out as duplicate of #39074.