-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
comments_popup_link defaults for accessibility #907
Comments
I believe it is done this way because it is generally not a good thing to let translators handle the markup. But I agree that adding the .screen-reader-text class would benefit the accessibility. |
I translate Core and it's not a problem:) But yes, in general it's not the best option to leave html markup for translators. Actually Core defaults are better for two reasons:
|
Agree, but what I'm saying is, we can still go the accessibility road, without markup in translatable strings:
|
That would look weird on front end for non screen reader users. |
Silly me, didn't think of that :) |
We could probably change the first argument to |
That would be step forward. I'd even leave Core handle the first argument, but that's just me:) |
I thought about that too, but it is more encouraging than the default wording. |
Do you want me to create pull request or what are we waiting for:) |
@samikeijonen if you can do a PR that would be great. I'd suggest what @obenland did to have more encouraging wording. |
Ok, I'll send a PR. |
I used |
Looks like this was merged in #915, closing. |
I was wondering how
_s
usescomments_popup_link
function:https://github.com/Automattic/_s/blob/master/inc/template-tags.php#L64
Core take care of this a little better by default what it comes for accessibility. For example Core uses for
1 Comment
string like this:Would it be better to use defaults for this one?
The text was updated successfully, but these errors were encountered: