Discussion tracking for ARIA Notification proposal

[scottaohara]

During the most recent ARIA F2F meeting the ARIA Notification proposal was presented and there were a number of open questions that needed resolution to move forward.

The purpose of this issue is to create a list of those discussion points so that there can be a single unified issue where resolution of those topics are tracked and reported upon, rather than having to dive into various different issues or discussion threads.

• Does the notification API need to support Braille?
• Does the notification API need to support speech mark (i.e. SSML)
• Guidance on fallback procedures (What to do if the platform/browser doesn't support the necessary API)
• Explain / identify guidance for expected (not required) screen reader interaction
• Referencing Arrays in the current spec appears confusing
• notificationId: discussion points
• Scoping / source
• Interrupt & flushing
• Understandability
• IA2 Support

[alisonmaher]

@benbeaudry and I will be attending TPAC virtually from the Redmond area. @douggeoffray isn't registered but would be virtual from the Redmond area. @spectranaut will it be required for Doug to register in order to attend the call for this topic?

[jnurthen]

@benbeaudry and I will be attending TPAC virtually from the Redmond area. @douggeoffray isn't registered but would be virtual from the Redmond area. @spectranaut will it be required for Doug to register in order to attend the call for this topic?

It is preferred but not required