[wp-trac] [WordPress Trac] #47131: Cursor suggests functionality even when functionality is not present

[WordPress Trac]

#47131: Cursor suggests functionality even when functionality is not present
-------------------------------------+-------------------------------------
 Reporter:  anevins                  |      Owner:  (none)
     Type:  defect (bug)             |     Status:  new
 Priority:  normal                   |  Milestone:  Awaiting Review
Component:  General                  |    Version:
 Severity:  normal                   |   Keywords:  has-screenshots needs-
  Focuses:  ui, accessibility,       |  patch wpcampus-report
  javascript                         |
-------------------------------------+-------------------------------------
 Users who mouse over the "Save" heading on the Edit Media page see a
 "move" cursor, which suggests to users that the "Save" section can
 be dragged and dropped to somewhere else. However, this is only the case
 if additional boxes are shown, re-ordering is not possible if "Save"
 is the only visible box (although the element can be dragged, there is
 nowhere else to drop it).

 The use of consistent and relevant cursors may be important for users
 who have a cognitive disability, since cursors give a visual clue as to
 an element's functionality. Using the move cursor for elements which
 cannot be moved may be confusing or counter-intuitive for users.

 * **Severity**:
   * Medium
 * **Affected Populations**:
  * Low-Vision
  * Cognitively Impaired
 * **Platform(s)**:
  * All / Universal
 * **Components affected**:
  * Edit Media

 **Issue code**

 {{{
     .js .postbox .hndle, .js .widget .widget-top {


         cursor: move;


     }
 }}}

 **Remediation Guidance**
 Only allow the move cursor to appear to users when re-ordering is
 functionally possible.

 Ideally, the drag and drop functionality should not be available at all
 when only one box is present (i.e. it should not even be possible to
 drag that one box), however this may be unrealistic to fix, and
 therefore the solution of removing the cursor style will go a long way
 towards matching user expectations.

 **Relevant standards**
 N/A

 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-78 in Tenon's report

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47131>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform