diff --git a/core-aam/index.html b/core-aam/index.html index b9b052b35..82dbf8074 100644 --- a/core-aam/index.html +++ b/core-aam/index.html @@ -11199,6 +11199,132 @@
+ Some APIs provide + methods which require specific algorithms to be followed. The following + sections provide the algorithm mapping tables for these methods. +
+
+ The ARIANotifyMixin provides a method for announcing content
+ to assistive technologies. The following algorithm mappings specify how
+ these announcements will be implemented across different accessibility
+ APIs to ensure consistent behavior for users of assistive technologies.
+
To aria notify given node, announcement, and priority:
| ARIA Specification | +
+ aria notify
+ |
+
|---|---|
| Preconditions | +
+ If node is excluded from the accessibility tree, then abort these steps. + |
+
| Language | +
+ + User agents and assistive technologies MUST determine the language of the announcement by taking the first valid BCP 47 language tag from the following sources: + +
+ Assistive technologies MUST present the announcement using that language (for example, voice, pronunciation rules, braille table). + + |
+
| MSAA + IAccessible2 | +
+ No implementation specified (see fallback note). + |
+
| UIA | +
+
+ If the platform accessibility implementation determines that node is not represented in the UIA + Control view or + Content view, user agents SHOULD instead raise the notification event + on the nearest ancestor that is represented as a UIA Control. If no such ancestor exists, user agents SHOULD raise it on the document root (which is expected to be + in one of these views) to ensure assistive technologies that ignore events on elements not in the Control or Content view receive the notification. + + |
+
| ATK | +
+
On older Linux accessibility stacks prior to ATK 2.50.0, user agents MAY use the fallback; see fallback note. + |
+
| AT-SPI | +
+
|
+
| AX API | +
+
|
+
When no suitable platform notification API is available (for example, older Linux accessibility stacks prior to ATK 2.50.0 that lack the newer notification signal, or on Windows when the user agent is not able to use UIA), a user agent MAY synthesize a temporary, assistive-technology-only live region in its accessibility tree to convey an aria notify announcement. Such fallback nodes are not exposed to or detectable by web content and this behavior is not required.
diff --git a/index.html b/index.html index 95d131c27..f516fbea4 100644 --- a/index.html +++ b/index.html @@ -179,7 +179,7 @@ preProcess: [linkCrossReferences, getParticipants], postProcess: [ariaAttributeReferences], - xref: ["dom", "accname-1.2", "core-aam-1.2", "infra", "HTML"], + xref: ["dom", "accname-1.2", "core-aam-1.2", "infra", "HTML", "permissions-policy"], definitionMap: [], }; function respecChangelogFilter(commit) { @@ -16733,8 +16733,8 @@
Conforming user agents MUST implement the following IDL interface.
+Conforming user agents MUST implement the following IDL interfaces.
@@ -16797,6 +16797,54 @@Interface Mixin ARIAMixin
>
+ enum AriaNotifyPriority { "normal", "high" };
+
+ dictionary AriaNotificationOptions {
+ AriaNotifyPriority priority = "normal";
+ };
+ interface mixin ARIANotifyMixin {
+ undefined ariaNotify(DOMString announcement, optional AriaNotificationOptions options = {});
+ };
+ Element includes ARIANotifyMixin;
+ Document includes ARIANotifyMixin;
+
+
+
+ The User Agent processing steps for the
+ ariaNotify(announcement, options)
+ method are:
+
If the document is not [=allowed to use=] the feature identified by "aria-notify" abort these steps.
+Let node be this.
Let priority be options["priority"].
If node is excluded from the accessibility tree, then abort these steps.
+Run the aria notify steps given node, announcement, and priority.
+This specification defines a [=policy-controlled feature=] identified by the string "aria-notify".
+ It has a [=policy-controlled feature/default allowlist=] of "*".
+
+ When disabled in a document, any notifications applied using ariaNotify within that document will not be sent.
+