You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't currently happening for understandable reasons, but I wanted to open an issue to get browser implenetors' feedback on the feasibility of auto-translating strings given the current format of:
content:'string-not-to-be-translated'/'string that should be translated';
There's a bit of history of screen-reader-only content getting left out of localization efforts both in browsers and by authors (e.g. aria-label taking quite a while to be included in translation), and this seems like it has a high potential to follow that trend so I wanted to make sure this is raised early.
Essentially, for browser folks, I'm curious if:
This format with content + / can feasibly be included in strings to be translated
Would this interfere with efforts to include CSS content in general in translations
Could this be implemented before CSS overflow becomes a stable/released feature
The text was updated successfully, but these errors were encountered:
smhigley
changed the title
[css-overflow-5]: making specific scroll markers disabled
[css-overflow-5]: browser translation of accessible name strings for scroll-markers and scroll-buttons
Jun 3, 2025
This isn't currently happening for understandable reasons, but I wanted to open an issue to get browser implenetors' feedback on the feasibility of auto-translating strings given the current format of:
There's a bit of history of screen-reader-only content getting left out of localization efforts both in browsers and by authors (e.g.
aria-label
taking quite a while to be included in translation), and this seems like it has a high potential to follow that trend so I wanted to make sure this is raised early.Essentially, for browser folks, I'm curious if:
content
+/
can feasibly be included in strings to be translatedcontent
in general in translationsThe text was updated successfully, but these errors were encountered: