Review request for Confirmation of Action API

[sartang]

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.

• Explainer¹ (minimally containing user needs and example code): here
• User research: here
• Primary contacts (and their relationship to the specification):
  • Sara Tang, Microsoft
  • Daniel Libby, Microsoft
  • Travis Leithead, Microsoft
• Organization(s)/project(s) driving the specification: Microsoft, Google, Chrome
• External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): here

Further details:

• I have reviewed the TAG's Web Platform Design Principles
• Relevant time constraints or deadlines: [please provide]
• The group where the work on this specification is currently being done: ARIA working group
• The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue):
• Major unresolved issues with or opposition to this specification:
• This work is being funded by: Microsoft, Google

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]

[torgo]

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?

[sartang]

@torgo Not at the moment, but we are hoping to get more feedback once we start prototyping.

[dlibby-]

As @sartang mentioned, we're planning on getting more feedback from other stakeholders as we refine the proposal during implementation and modification to the proposal.

We have received some preliminary feedback from various folks (see initial discussion in the AOM CG and WICG/aom#187), and once we believe we've addressed that feedback, we plan on opening this up for discussion in ARIA WG.

cc @travisleithead in case he wanted to add any details.

[LeaVerou]

Hi there,

We looked at this today during our F2F. Overall this looks like useful functionality that has been missing from the web platform. We'd love to see this moving forward. Thanks for working with us!

[sartang]

Leaving a note here that I've updated the explainer. The proposal is largely the same, but more code examples have been added and the parameter names in the spec have changed slightly.