Make WordPress Core

Opened 3 years ago

Last modified 10 days ago

#39074 new defect (bug)

No method to move meta boxes using keyboard

Reported by: joedolson Owned by:
Milestone: 5.3 Priority: normal
Severity: normal Version:
Component: Administration Keywords: wpcampus-report needs-design
Focuses: accessibility Cc:

Description (last modified by antpb)

Using a mouse, meta boxes can be moved to a new order in the DOM or to a different column. There's no method to do this using the keyboard.

Especially with several plugins installed, being able to customize which meta boxes are closest in tab sequence can be quite helpful for editing efficiency.

I assume this has been in since whatever version added sortable metaboxes.

This issue was brought to light again through the WPCampus-report when it was discovered that the weight of the edit image attributes was not able to be ordered. This is true for all forms of meta boxes so I’m adding in the details from the specific Edit Image context to highlight the accessibility importance of this issue:

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

Affected Populations:
Motor Impaired
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

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.

Attachments (1)

4A1B714B-6886-470C-BD7C-313BA317BDE7.png (76.9 KB) - added by antpb 2 weeks ago.
An example where this has accessibility difficulties

Download all attachments as: .zip

Change History (14)

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.

3 years ago

#2 @afercia
3 years ago

  • Milestone changed from Awaiting Review to Future Release

Makes sense and probably needs some research.

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.

19 months ago

#4 @afercia
3 months ago

Related: #47135.

This ticket was mentioned in Slack in #core-media by mike. View the logs.

2 weeks ago

#6 @anevins
2 weeks ago

  • Keywords wpcampus-report added; needs-patch removed

Added keyword

#7 @antpb
2 weeks ago

#47135 was marked as a duplicate.

#8 @antpb
2 weeks ago

  • Description modified (diff)

#9 @antpb
2 weeks ago

  • Milestone changed from Future Release to 5.3

2 weeks ago

An example where this has accessibility difficulties

#10 @afercia
2 weeks ago

Full detailed report available at #47135.

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.

2 weeks ago

This ticket was mentioned in Slack in #accessibility by audrasjb. View the logs.

10 days ago

#13 @audrasjb
10 days ago

  • Keywords needs-design added
Note: See TracTickets for help on using tickets.