From 68ecd7bec04e2a96fe8be41d0992523a3b0d2310 Mon Sep 17 00:00:00 2001 From: James Craig Date: Thu, 30 Jul 2026 18:27:18 -0700 Subject: [PATCH 1/2] CORE-AAM: Require ariaNotify announcements to be translated when the page is auto-translated Add a Translation step to the ariaNotify algorithm mapping table requiring user agents to apply the browser's machine translation to the announcement before raising the platform accessibility notification, and to defer that notification until translation completes. Closes w3c/core-aam#265 --- core-aam/index.html | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/core-aam/index.html b/core-aam/index.html index 8e91e4d86..750f56930 100644 --- a/core-aam/index.html +++ b/core-aam/index.html @@ -12557,6 +12557,21 @@

ariaNotify

Assistive technologies MUST present the announcement using that language (for example, voice, pronunciation rules, braille table).

+ + Translation + +

+ When the user agent is presenting the document in a machine-translated rendering (for example, via a built-in "Translate this page" feature), the user agent MUST apply the same + translation to announcement before performing any of the platform-specific steps below, so that the announcement is conveyed to assistive technologies in the language + presented to the user rather than in the language of the original content. +

+

+ The user agent should not trigger the platform accessibility notification until the translation step has completed; otherwise assistive technologies may present the original and + translated strings in sequence. The same translation step is expected to apply to live region announcements before their + corresponding platform notifications are triggered. +

+ + MSAA + IAccessible2 @@ -12662,6 +12677,7 @@

Change Log

Substantive changes since the last Candidate Recommendation Snapshot