Opened 6 years ago
Last modified 21 months ago
#29748 assigned enhancement
Mark strings for screen readers
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | I18N | Keywords: | has-patch needs-refresh |
Focuses: | Cc: |
Description
Sometimes there are "hidden" strings which are for screen readers, but translators have to search for context to find the real meaning. Maybe we could mark all these strings somehow (comment for translators or context) to make it easier?
I can create patch if you think that it is a good idea (and we can also discuss best solution before: comment or context).
Attachments (5)
Change History (26)
This ticket was mentioned in Slack in #core-i18n by swissspidy. View the logs.
5 years ago
#4
follow-up:
↓ 6
@
5 years ago
- Milestone changed from Awaiting Review to Future Release
A translator comment might be helpful, yes.
@swissspidy proposed that this should be added to the handbook (https://make.wordpress.org/core/handbook/best-practices/internationalization/) and considered for future strings. I tend to agree with that. Any suggestions for a comment?
#5
@
5 years ago
A translator comment looks more adapted than context for me. May be useful to add this to https://developer.wordpress.org/plugins/internationalization/how-to-internationalize-your-plugin/ to extend the practice to plugins (the same for themes).
#6
in reply to:
↑ 4
;
follow-up:
↓ 7
@
5 years ago
Replying to ocean90:
A translator comment might be helpful, yes.
@swissspidy proposed that this should be added to the handbook (https://make.wordpress.org/core/handbook/best-practices/internationalization/) and considered for future strings. I tend to agree with that. Any suggestions for a comment?
What about simply using screen reader text
or maybe only visible to screen readers
? assistive text for screen readers
?
#7
in reply to:
↑ 6
@
5 years ago
Replying to swissspidy:
What about simply using
screen reader text
or maybeonly visible to screen readers
?assistive text for screen readers
?
We already have a few "accessibility text" comments for aria-label
placeholders.
#8
@
5 years ago
Related BuddyPress ticket: #BuddyPress6951
This ticket was mentioned in Slack in #core by chriscct7. View the logs.
5 years ago
This ticket was mentioned in Slack in #core by voldemortensen. View the logs.
5 years ago
This ticket was mentioned in Slack in #core by ocean90. View the logs.
5 years ago
#17
follow-up:
↓ 18
@
5 years ago
Just adding "accessibility text" doesn't really complete clarifying the context for the strings. Especially for "Page" which I saw as a pagination use.
#18
in reply to:
↑ 17
@
5 years ago
Replying to jipmoors:
Just adding "accessibility text" doesn't really complete clarifying the context for the strings. Especially for "Page" which I saw as a pagination use.
Yep maybe the text could be improved a bit. What translators really need to know? I'd say:
- it's hidden text, not visible in the UI so better they don't waste time trying to find the place where this text is displayed because... well, it is not displayed at all
- it is used to expand short labels and sentences to give more context or add feedback where otherwise the feedback is only visual
Anyone able to summarise all this in a very short sentence? :)
A translator comment sounds like a good idea.