This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Determine whether UIA Pattern Methods should be included in the table of default actions in 5.7 Actions. (From Cynthia's walkthrough of the UAIG.) See also related ACTION 848: Define "default action" as used in this section http://www.w3.org/WAI/PF/Group/track/actions/848
I had a long talk with Larry about this, and we don't think we should include this table at this time. We would need to be able to change the DOM in order to hook this up correctly, and that's not allowed with ARIA 1.0. We actually think we should remove most of the section, including the table, and tell browsers to simulate a click if MSAA doDefaultAction is called, or if *ANY* pattern method is called via UIA. JavaScript event handlers can then react to the click event and set the aria properties. The browser will update the API based on the aria property changes, and it should all work. Getting a real 2 way API is something we need to do for ARIA 2.0.
Remove the table and make edits from Cynthia's post to MSAA and UIA bullets. She thinks IA2 relies on MSAA DoDefaultAction. Check with David for ATK and James for OS X.
Have removed the table but need more guidance from Cynthia on modifying the remaining text.
From Cynthia: Replace all of that with this. We need the names of the equivalent to DefaultAction in ATK/AT-SPI and OSX. As part of mapping roles to accessible objects as defined in (section), users agents will have implemented an MSAA DefaultAction, one or more UIA Pattern methods, or (whatever this is called in other APIs). · If an AT calls MSAA DoDefaultAction on an accessible object, the browser SHOULD simulate a click on the DOM element which is mapped to that accessible object. · If an AT calls the IA2 IAccessibleAction on an accessible object, the browser SHOULD simulate a click on the DOM element which is mapped to the that accessible object. · If an AT calls any UIA pattern method on an accessible object, the browser SHOULD simulate a click on the DOM element which is mapped to that accessible object. · ATK/AT-SPI · OSX Note: Authors will need to create handlers for those click events that update ARIA states and properties in the DOM accordingly, so that those updated states can be populated by the browser in the Accessibility API.
Changes made per Cynthia's comment. Need AT/SPI info from David and OS X info from James.
David, please review the new text for the Actions section and provide the equivalent bullet for ATK/AT-SPI: http://www.w3.org/WAI/PF/aria-implementation/#mapping_actions
For ATK: "If an AT calls an action on an accessible object, the user agent SHOULD simulate a click on the DOM element which is mapped to the that accessible object."
Need OS X bullet from James. See ACTION-848.