[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 rianrietveld):

 Jumping new into the conversation:

 I agree with @GaryJ that adding add_theme_support( 'screen-reader-text' )
 will be the best way to check for screen reader text CSS and maintain
 backwards compatibility in themes, frameworks and plugins.

 Adding the CSS to core has the disadvantage that core decides how the CSS
 will look like.
 Using the screen-reader-text with hover for skip links needs custom
 styling to fit the theme's look, and some customers still need IE7 support
 (yes, I know), so the CSS can differ per theme.

 Like @joedolson I can't come up with another a11y functionality for
 add_theme_support than the screen-reader-text. ARIA labels, roles etc. is
 all hidden from screen anyway. So if that is added in
 core/framework/plugin, the front end will suffer from it.

 So, +1 for add_theme_support( 'screen-reader-text' );

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