bp-screen-reader-text class and Themes overridding buddypress.css

[imath]

Great improvements about accessibility has been committed into 2.4.0 and with them the use of the .bp-screen-reader-text class also increased.

Testing some themes (using BP Legacy and overriding the buddypress.css file) to check the cover images feature, i've noticed none of them were including this class inside their css file.

And i'm also a bad user, because my custom buddypress.css on the projects i'm working on wasn't including it :)

In 2.2 it was used 9 times, it's now used 44 times. So there is good chances some labels appear when they shouldn't... Just in case we'll have this patch ready..

[DJPaul]

Is this needed?

[hnla]

I'm inclined to close this for following reasons:

First and foremost we are now past the danger point, if there had have been an issue we would have needed to deploy this by now!

As imath says he's a bad user :) and hasn't covered the class in his overloaded styles, this is a common class used to hide label text, we(BP) have added a number of these class tokens on labels that previously didn't exist & the ruleset however it has always to be the responsibility of the custom theme to deal with ensuring any new styles, script, or markup additions are accounted for.

Yes true those labels may appear, but enqueueing embedded head styles just to cover the possibility of a few custom themes having an issue? We're loading styles on every page, that won't cache just to prevent labels showing for a few themes do we want to do that? If we did perhaps we should load only if we detect overloaded theme?

[DJPaul]

I agree. Hasn't proven to be a problem (yet?) in the Real World.

[hnla]

Ticket started 8 months ago, my comment 3 months ago, we haven't seen a problem brought to our attention so although a fair point to raise, we're well past any true problem point.