Make a11y string properly localizable#15161
Conversation
There was a problem hiding this comment.
Thank you @swissspidy for helping us with this improvement!
I wanted to ask if it's possible to use _x() instead of __() to be able to send a more accurate context to the translators, letting them know that this string is intended to be used be the Screen Reader engine.
Something like:
_x( 'Heading block. Level %s. Empty.', 'Spoken out loud by the screen reader' )
|
In WordPress itself we usually use a |
That sounds great! Thank you 🙏 |
pinarol
left a comment
There was a problem hiding this comment.
I tested this on iOS and it works OK.
|
hey @Tug 👋 I updated the position of translator comments |
* Make a11y string properly localizable * Remove extra . after the content * Add `accessibility text` to the translators comment * Fix the wrong parameter * Change the position of translator comments
Description
Fixes the non-localizable code introduced by #15144.
This is a friendly reminder to think about internationalization best practices :-)
Types of changes
Bug fix (non-breaking change which fixes an issue)
Checklist: