[wp-trac] [WordPress Trac] #29699: add_theme_support( 'screen-reader-text' );

[WordPress Trac]

#29699: add_theme_support( 'screen-reader-text' );
-------------------------+------------------------------
 Reporter:  GaryJ        |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Themes       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  accessibility
-------------------------+------------------------------

Comment (by GaryJ):

 Here's a real example from outside of core. The Genesis Framework search
 form, by default doesn't have a `<label>`. Amending the code so that it
 does would change the visual appearance, potentially breaking the layout
 of 130,000+ sites. Adding a `screen-reader-text` class to Genesis
 `style.css` to visually hide the new label won't help, as the child themes
 don't reference that file - it needs to be in the child theme `style.css`.

 So, it's exactly the same situation as in core, but the point is, it's not
 core. It's a theme, and plugins could be in a similar situation. Adding
 explicit labels to fix the tickets in core doesn't address the issues in
 the wider context, whereas having a solution that all parties in the
 community can use (`add_theme_support( 'screen-reader-text' )` with
 something close the patch I've added here) means everyone can use it.

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