[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:  reopened
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Themes       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  accessibility
-------------------------+------------------------------

Comment (by Otto42):

 > It makes for a very bad developer experience when they have to start
 removing actions and filters to take full control of the front-end of
 their site. WordPress has never done that until now, and I think we should
 be very careful about changing that.

 They already have to do that for lots and lots of things. That's par for
 the course. My concern is not with the developers. They'll adapt and there
 are fewer of them overall.

 No, my concern is with the users. If core is going to start getting into
 the business of adding screen-reader-text to places where it was not
 before, in the name of accessibility, then we need to make very, very sure
 that this new text doesn't interfere with people's existing sites. I don't
 want people taking actions to remove text from their sites or questions on
 the support forums from people asking how to make their sites less
 accessible. And that's the road you're heading down here.

 Break one person's carefully made layout in the name of accessibility, and
 they'll never again think of accessibility as a good thing. What they're
 going to think instead is that you broke their site in order to help blind
 people.

 So think real long and hard before you start ditching front-end
 compatibility.

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