[wp-trac] [WordPress Trac] #47012: Proposal: Simplify WordPress Admin Navigation

WordPress Trac noreply at wordpress.org
Tue May 7 15:11:23 UTC 2019


#47012: Proposal: Simplify WordPress Admin Navigation
-------------------------------------------------+-------------------------
 Reporter:  lessbloat                            |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Administration                       |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-design needs-design-feedback   |     Focuses:  ui,
  dev-feedback                                   |  accessibility
-------------------------------------------------+-------------------------

Comment (by afercia):

 > The hover/flyout menus are difficult to make accessible

 Seems to me this statement without any additional context comes a bit out
 of the blue.  I'd like to hear more details about the specific
 accessibility concerns. Is there any data? Any user testing? While the
 current "flyouts" can be problematic for some accessibility needs, they're
 perfectly OK for other users. For example, screen reader users don't even
 perceive the "flyouts", as the menu sub-items can be normally navigated
 with Tabs or arrowing and they're all correctly announced.

 Instead, accordions would make the interaction less intuitive and less
 natural, for the simple fact they require an additional click. Not to
 mention [https://core.trac.wordpress.org/ticket/18382 accordions would
 bring WordPress back to 3.2] 🙂

 On a general note, I'd tend to think any design proposal should be based
 on an in-depth analysis of the current functionalities/features and have
 solid basement in data and user testing. Ideally, this should happen
 before any visual mockup.

 Which of the current admin menu functionalities and features should be
 kept? Which ones can be removed? For example, I don't see any analysis
 about the four different states the menu can have:
 1. fully expanded (on large screens)
 2. auto-folded (automatically kicks in at intermediate viewports)
 3. collapsed (triggered by the user)
 4. responsive

 Worth also reminding plugins can add menu sections and items and this is
 based on a system of "priorities": basically plugins can add menu sections
 almost everywhere. I don't see this taken into considerations in the
 visual mockups nor in the proposed menu grouping.

 A few more things I'd like to see before any visual mockups:
 - a complete analysis of all the pending Trac tickets related to the admin
 menu: I see this as an essential step, in order to have a better idea of
 what the pending issues are, enhancements, feature requests, etc.
 - in-depth user testing of the current admin menu
 - the user testing group include users with accessibility needs
 - analysis of the features/functionalities for multisite
 - analysis of the features/functionalities with regards to capabilities
 - mobile first

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


More information about the wp-trac mailing list