[wp-trac] [WordPress Trac] #46651: Site Health: no room for the admin notices

WordPress Trac noreply at wordpress.org
Sat Mar 30 11:50:41 UTC 2019


#46651: Site Health: no room for the admin notices
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  5.2
Component:  Administration                       |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots site-health has-     |     Focuses:
  patch needs-design-feedback needs-refresh      |
-------------------------------------------------+-------------------------
Changes (by afercia):

 * keywords:  has-screenshots site-health has-patch needs-design-feedback =>
     has-screenshots site-health has-patch needs-design-feedback needs-
     refresh


Comment:

 For better accessibility and semantics, the first thing within the main
 content area should be a `h1` heading. The `h1` gives context to the main
 content area and it's also used for content navigation. Having a series of
 notices before the `h1` wouldn't be ideal, for example:
 - When using the "skip to main content" link or the ARIA landmarks, users
 would perceive as first thing one or multiple notices. Instead, they
 should get the main H1 so they're immediately informed about the main
 topic of the page.
 - When using a screen reader and navigating through headings, all the
 notices would be "skipped".

 This is a long standing issue across the admin pages where other elements
 are placed before the main `h1`. For example, the placement of the Screen
 Options and Help tabs isn't ideal, see ticket:21583#comment:56. It applies
 also to the "update nag": I do understand it needs to be visually
 prominent but its placement in the source order isn't ideal.

 For these reasons, I wouldn't recommend to keep the notices above the
 header.

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


More information about the wp-trac mailing list