#713: Review request for Confirmation of Action API
Discussions
2022-02-14
Dan: this starts off with user need which is great.
Dan: Regarding the privacy & security questions - do we think it should be restricted to secure contexts?
Sangwhan: given how easy it is to get https certs not sure it will mitigate against misuse. The other part that concerns me -
Dan: shouldn't this be the same bar as push notification API?
Sangwhan: gate it behind a permission?
Dan: I don't see the argument ...
Sangwhan: not convinced that it makes it less dangerous .. i won't lose sleep.
[...side discussion on secure contexts...]
Sangwhan: I'm more concerned about will applications be too chatty? other potential issue - aria so far has been declarartive - this is an API that changes that paradigm...
Dan: it's in the AOM work - so associated with other technologies that do the same...
Hi @sartang - thanks for this really well-written explainer! We especially appreciate how it starts with the user needs. Do you have any further info on multi-stakeholder interest? Have they had feedback from the ARIA community on this?
Dan & Sangwhan to have side discussions
OpenedFeb 2, 2022
Braw mornin' TAG!
I'm requesting a TAG review of a Confirmation of Action API.
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. We propose a notification API purpose-built to communicate to the accessibility layer for scenarios in which ARIA live regions are a poor choice. One of these scenarios is a "confirmation of action" where the action in question is not necessarily tied to UI (elements) in the app.
Further details:
We'd prefer the TAG provide feedback as (please delete all but the desired option):
💬 leave review feedback as a comment in this issue and @-notify [sartang, dlibby]