こんにちは TAG-さん!

I'm requesting a TAG review of the AriaNotify API.

A new API, AriaNotify, enables content authors to directly tell a screen reader what to read. Without AriaNotify, ARIA live regions are the only mechanism available today that communicate content changes down to the accessibility layer so that users can hear about them. ARIA live regions are stretched far beyond their original use cases as authors struggle to use them in scenarios that they weren't designed for. AriaNotify is purpose-built to communicate to the accessibility layer for scenarios in which ARIA live regions are a poor choice. In the simplest scenario, the content author calls ariaNotify with a string to read.

• Explainer¹: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Accessibility/AriaNotify/explainer.md
• Specification: https://deploy-preview-2211--wai-aria.netlify.app/core-aam/#arianotifymixin-map-arianotify
• WPT Tests:
• User research: Do we need a notifications API in ARIA w3c/aria#832
• Security and Privacy self-review²: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Accessibility/AriaNotify/explainer.md#privacy--security-considerations
• GitHub repo: https://github.com/w3c/aria
• Primary contacts:
  • Evelynn Kaplan (@evelynn-kaplan), Microsoft
  • Alison Maher (@alisonmaher), Microsoft
  • Keith Cirkel (@keithamus), GitHub, Spec author
• Organization/project driving the specification: Microsoft, Google, Chrome, GitHub
• This work is being funded by: Microsoft, GitHub
• Primary standards group developing this feature: ARIA WG
• Incubation and standards groups that have discussed the design:
  • ARIA WG
  • WHATWG
• Multi-stakeholder support³:
  • Chromium comments: Supportive/driving
  • Mozilla comments: ariaNotify API mozilla/standards-positions#1049
  • WebKit comments: ariaNotify API WebKit/standards-positions#370
• Status/issue trackers for implementations⁴: https://chromestatus.com/feature/5745430754230272

Further details:

• I have reviewed the TAG's Web Platform Design Principles
• Previous early design review, if any: Review request for Confirmation of Action API #713
• Relevant time constraints or deadlines:

You should also know that...

We plan to add a permissions-policy that would allow authors to opt iframes out of AriaNotify. We are working on the implementation and draft spec but it is not yet finished. The relevant WHAT WG discussion is here: whatwg/html#11004

Please let us know if the permissions-policy should be requested as part of a separate TAG review, or accepted as part of this one.