2010511 - [meta] Add DevTools support for ariaNotify

Status: NEW

(DevTools :: General, task)

Description

[Sebastian Zartner [:sebo]]

The imperative ARIA Notify API (as a replacement for ARIA live regions will be implemented, see https://groups.google.com/a/mozilla.org/g/dev-platform/c/7UOkFqbeH7o/m/IozzYfuGAAAJ.

And I think it should be somehow surfaced in the DevTools to help authors with a11y debugging.

From the explainer I get that API mainly consists of an asynchronous ariaNotify() function that can be called on elements and the document. And that function takes a string to tell screen readers what to read as first argument and an optional options object as second argument.
In addition to that there will be a new aria-notify directive for the Permissions-Policy header and a corresponding aria-notify value for the allow attribute on iframes.

I imagine multiple places where the DevTools could expose this info:

• The Accessibility panel could show the strings and possibly the options in their node view. (Though the messages are very transient, so not sure about the best way to do that.)
• The Inspector panel could show a badge indicating the notification and link to the Accessiblity panel for more info. (Though the messages are very transient, so not sure about the best way to do that.)
• The area-notify directive (and also the other directives) for the Permissions-Policy header could be linked to its related MDN page. (According to Searchfox, the Permissions-Policy header itself already links to the related MDN page. So that should be fine.)
• The aria-notify directive (and also the other directives) in the allow attribute of <iframe> elements could be linked to its related MDN page.

Sebastian