Repository navigation
Core-AAM: new UA req that ariaNotify strings should be translated when browser view is auto-translated #265
Description
I took an action to make a new issue for Core-AAM based on a question from @pkra... The implementation should translate
ariaNotifystrings if the browser/engine is running in a translated rendering via built-in "Translate this page" features. For example, using a variant of @smhigley's example:<html lang="en"> <body> …[chinese content]… </body> </html>el.ariaNotify('希望你能听懂中文'); // this announcement becomes a translated string when browser view is translated from the ChineseI think this can be a single RFC-2119 req for UAs, and leave the specifics as implementation details. Note: Sarah is doing some additional tests to determine if this is an existing problem with Live Regions.
Originally posted by @cookiecrook in #2828
Activity
cookiecrook commentedon Jul 16, 2026
smhigley commentedon Jul 16, 2026
I verified
ariaNotifystrings are not currently being auto-translated by browsers (unsurprising based on how new the feature is). Here's a codepen with a test case to verify: https://codepen.io/editor/smhigley/pen/019f6bf9-12b0-7c95-a290-1642d204c808And here's a link to the UI alone, without the codepen UI: https://inspiring-term-elephant.codepen.app/
cookiecrook commentedon Jul 16, 2026
Yes, so it seems the new Core-AAM rule for ariaNotify could require the same translation step for live region updates, before triggering the subsequent accessibility API notification. (Unless the implementation proves too problematic for some reason.)
cookiecrook commentedon Jul 21, 2026
In some brief tests, Live Region announcements in Safari+VO are auto-translated, but sometimes but the original and translated strings can be spoken in sequence, so I think it's worth specifying that UA should not trigger the system notification until after the translation step has completed.
cookiecrook commentedon Aug 6, 2026
@twilco has WebKit PR 71083 up already. 🔥