[wp-trac] [WordPress Trac] #39074: No method to move meta boxes using keyboard

[WordPress Trac]

#39074: No method to move meta boxes using keyboard
-------------------------------------+-------------------------------------
 Reporter:  joedolson                |       Owner:  xkon
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  5.4
Component:  Editor                   |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  wpcampus-report has-     |     Focuses:  ui, accessibility,
  patch needs-design-feedback has-   |  administration
  screenshots                        |
-------------------------------------+-------------------------------------

Comment (by xkon):

 [attachment:"39074.7.diff"] also adds `a11y.speak()` for some of the
 actions.

 To recap what this patch is introducing for an easier review:

 - Introduces 3 new buttons on postboxes. Two of them will move the
 postboxes within the same group and the third will cycle the postbox
 through all other groups always on position 1.
 - Changes the HTML output of the buttons to match the DOM.
 - Creates new `handle_order`, `handle_move`,
 `enable_disable_order_buttons` callbacks in `postbox.js` with the
 necessary code for each case.
 - Modifies the `wp_ajax_meta_box_order()` to return with a
 `wp_send_json_success()` and adds `a11y.speak()` on the `save_order` ajax
 as `The postboxes order has been saved.`.
 - Adds `a11y.speak()` on the `handle_order` to identify if the current
 postbox is already first/last on the list as `The postbox is already on
 the first position.` & `The postbox is already on the last position.`.

 --

 Visual preview is the same as [attachment:"39074.6_preview.gif"].

 We can always extend & adjust the `a11y.speak()` messages on future
 iterations to be more precise regarding the position within the groups as
 well as add a message for the `save_state` (this keeps the open/closed as
 well as the Screen Options list).

 Do tell me if I missed anything or if any further adjustments are needed!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/39074#comment:39>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform