[wp-trac] [WordPress Trac] #31450: Add landmark roles to WordPress admin areas

[WordPress Trac]

#31450: Add landmark roles to WordPress admin areas
----------------------------+--------------------------------------------
 Reporter:  joedolson       |       Owner:  joedolson
     Type:  defect (bug)    |      Status:  assigned
 Priority:  normal          |   Milestone:  4.2
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  accessibility, administration
----------------------------+--------------------------------------------

Comment (by afercia):

 Looking a bit into this, I wouldn't touch this z-index madness :) Ideally,
 there should be just one stacking context based on a general wrapper
 element. By the way there would probably be unpredictable consequences,
 for example about plugins that add items in the admin bar.
 One way to solve the issue (tested) is to add a wrapper `div` e.g.:
 {{{
 <div id="nav-main" role="navigation" aria-label="<?php esc_attr_e( 'Main
 menu' ); ?>">
 <a tabindex="1" href="#wpbody-content" class="screen-reader-
 shortcut"><?php _e( 'Skip to main content' ); ?></a>
 <div id="adminmenuback"></div>
 <div id="adminmenuwrap">
 <ul id="adminmenu">
 ...
 </ul>
 </div>
 </div>
 }}}

 This way the new wrapper div will still use the original stacking context,
 no CSS changes required. Yes it's one more div... I know.

 Would like to hear your thoughts about one thing that always bothered me
 :) the placement of the "Skip to toolbar" link:
 {{{
 <a class="screen-reader-shortcut" href="#wp-toolbar" tabindex="1"><?php
 _e('Skip to toolbar'); ?></a>
 }}}
 Would it make sense to change its placement conditionally based on
 `is_admin()`?
 If is admin: output it right after the "Skip to main content" link
 If is front end: output it in the admin bar.

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