This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
comment 325: http://www.w3.org/WAI/PF/Group/comments/details?comment_id=325 Survey: http://www.w3.org/2002/09/wbs/32212/20100329_comments/results#xc325 From ARIA TF March 29, 2010 meeting minutes: http://www.w3.org/2010/03/29-pf-minutes.html Comment 325: Popups - live regions RS: I would call them percievable regions JC: It is not always the result of an external event RS: When do we mark something as a live region? ... Trying to use live regions to trigger to say something, so we want to try to avoid that. JN: Problem is that developers are overusing live regions SC: Sounds like a good point RS: Do we say 'typically updated'? JC: I think 'typically updated' is probably fine RS: Second edit MC: There might be style guide somewhere which tells us which one we should use JC: We should then remove the expansion of the acronymn RS: fine with that ... Chat log change fine with me ... OK with next modification ... Next modification OK ... Final modification JN: I think it is a good idea to list them RS: Do not think that alertdialog is live region ... alert is JC: We should make a list of what are expected live regions. Do we have that list? <jamesn> also here http://www.w3.org/TR/wai-aria/roles#alertdialog RS: We should probably remove alertdialog as it will get focus JC: The user agent is expected to understand that there is an alert based on the role and not the live region RS: YEs JC: We should make the spec change too as well as the implementation guide change RS: Authoring practices is fine MC: Spec implies it is a live region <clown> http://www.w3.org/WAI/PF/aria/roles#progressbar JC: What if aria-live is off? [general discussion] JC: Agreed to edit alertdialog as it is no longer a live region ... Not sure if agreed to add text to implementation guide <jcraig> ACTION: jcraig to edit spec to remove implicit aria-live value for alertdialog [recorded in http://www.w3.org/2010/03/29-pf-minutes.html#action01] <trackbot> Created ACTION-631 - Edit spec to remove implicit aria-live value for alertdialog [on James Craig - due 2010-04-05]. JC: We talked about adding a list of live regions MC: We could refer people to the authoring practices if they are listed there RS: Yes refer to authoring practices <richardschwerdtfe> http://www.w3.org/WAI/PF/aria-practices/#chobet <jcraig> ACTION: andi to edit UAIG to add requirement that UAs trigger an API alert for alertdialog gain focus (comment 325) [recorded in http://www.w3.org/2010/03/29-pf-minutes.html#action02] <trackbot> Created ACTION-632 - Edit UAIG to add requirement that UAs trigger an API alert for alertdialog gain focus (comment 325) [on Andi Snow-Weaver - due 2010-04-05].
*** Bug 10046 has been marked as a duplicate of this bug. ***
The ARIA spec contains the following text for BOTH alert and alertdialog: The user agent MAY fire a system alert event through the accessibility API when the alert is created, provided one is specified by the intended accessibility API. But Action 667 says that the user agent MUST issue an alert for alertdialogs. For MSAA, the alert event appears to be "EVENT_SYSTEM_ALERT". Added text to role mapping table for alert (MAY) and alertdialog (MUST). For UIA, ATK, and Apple, added a generic note: "The user agent MAY/MUST fire a system alert event." But this is now out of sync with the ARIA spec which says "may" for both. I'll talk to James about this.
Per the 29 November ARIA TF meeting, it was agreed that both the WAI-ARIA spec and the UAIG will say that UA's SHOULD fire a system alert for both alert and alertdialog roles.