ISSUE-481: aria-live removal events should or must happen before object removal
aria-live removal events
aria-live removal events should or must happen before object removal
- State:
- CLOSED
- Product:
- ARIA 2.0 Core AAM
- Raised by:
- Matthew King
- Opened on:
- 2012-02-20
- Description:
- Section 5.8.2 of the UAIG includes the following paragraph with a SHOULD. Consider changing to MUST.
User agents SHOULD ensure that an assistive technology, running in process can receive notification of a node being removed prior to removal. This allows an assistive technology, such as a screen reader, to refer back to the corresponding DOM node being deleted. This is important for live regions where removals are important. For example, a screen reader would want to notify a user that another user has left a chat room. The event in MSAA would be EVENT_OBJECT_HIDE. For ATK/AT-SPI this would be children_changed::remove. And in Mac OS X, the event is AXLiveRegionChanged. This also requires the user agent to provide a unique ID in the accessibility API notification identifying the unique node being removed. - Related Actions Items:
ACTION-1368 on Cynthia Shelly to Investigate implementation of aria-live region events in ie apropos issue-481. - due 2014-04-29, closedACTION-1369 on David Bolter to Investigate implementation of aria-live region events in FF - due 2014-05-06, closedACTION-1434 on David Bolter to Contact matt king regarding issue-481, especially regarding multi-process - due 2014-05-27, closed- Related emails:
- No related emails
Related notes:
Matt prefers keeping this on the radar. Let's move to 2.0.
Moving to ARIA 2.0 product since there is no UAIG 2.0 product yet. Will discuss creating new product with Michael.
https://github.com/w3c/core-aam/issues/8
James Nurthen, 9 May 2018, 23:48:39Display change log