18:49:04 RRSAgent has joined #aapi 18:49:04 logging to http://www.w3.org/2016/10/18-aapi-irc 18:49:06 RRSAgent, make logs world 18:49:06 Zakim has joined #aapi 18:49:08 Zakim, this will be 18:49:08 I don't understand 'this will be', trackbot 18:49:09 Meeting: Accessible Rich Internet Applications Working Group Teleconference 18:49:09 Date: 18 October 2016 18:49:20 chair: Joseph_Scheuhammer 18:49:59 agenda: this 18:50:10 agenda+ ISSUE-1038/ISSUE-1026: (Bogdan, James) Mappings for feed, figure, and term. 18:50:21 agenda+ ISSUE-676/: (Joseph) Adding MSAA+IA2 action, interface, and relations to role mappings. 18:51:23 agenda+ ACTION-2121: (Joanie) Correct the ATK/AT-SPI text for single and multiple selection removal. 18:51:39 agenda+ Triage issues/actions: https://www.w3.org/WAI/ARIA/track/products/23 18:51:50 agenda+ Triage core-aam bugzillas: https://www.w3.org/Bugs/Public/buglist.cgi?component=Core%20AAM&product=ARIA 18:52:01 agenda+ Triage accname-aam bugzillas: https://www.w3.org/Bugs/Public/buglist.cgi?component=AccName%20AAM&product=ARIA 18:52:10 agenda+ Triage accname actions: https://www.w3.org/WAI/PF/Group/track/products/26 18:52:15 agenda+ be done. 18:52:44 clown has changed the topic to: WebEx Access Code 641 707 405 (Next meeting 18-Oct-2016, 20:00 UTC) 18:59:40 present+ Joanmarie_Diggs 19:01:45 present+ Joseph_Scheuhammer 19:02:42 Rich has joined #aapi 19:03:01 present+ Rich_Schwerdtfeger 19:06:20 scribe: joanie 19:07:42 bgaraventa1979 has joined #aapi 19:08:06 present+ Bryan_Garaventa 19:08:23 https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-heading 19:10:29 bgaraventa1979 has joined #aapi 19:11:05 present+ Bryan_Garaventa 19:12:11 Zakim, take up item 1 19:12:11 agendum 1. "ISSUE-1038/ISSUE-1026: (Bogdan, James) Mappings for feed, figure, and term." taken up [from clown] 19:12:33 JS: There are a couple of issues about the Core AAM mappings for UIA and AXAPI and I wanted to know if there was any news. 19:12:52 JS: And the answer is yes, because you (Rich) sent out emails to Bogdan and James Craig. 19:12:58 RS: Correct. 19:13:31 JS: Any other comments or questions? 19:13:46 Zakim, next item 19:13:46 agendum 2. "ISSUE-676/: (Joseph) Adding MSAA+IA2 action, interface, and relations to role mappings." taken up [from clown] 19:13:51 issue-676? 19:13:51 issue-676 -- Is it useful to identify MSAA+IA2 and ATK/AT-SPI actions, interfaces, and relations in the mappings? -- open 19:13:51 http://www.w3.org/WAI/ARIA/track/issues/676 19:14:13 JS: There's an issue raised by Jason Kiss to add actions, interfaces, and relations to the mappings. 19:14:27 JS: We did it for ATK; Cynthia seems to have done the same for UIA. 19:14:29 https://lists.w3.org/Archives/Public/public-aria/2016Oct/0059.html 19:14:38 JS: MSAA and IA2 seems to be the only things missing. 19:15:02 JS: I sent an email to Alex Surkov (see link above). 19:15:29 JS: I asked him to look through it and tell me where the differences are. 19:15:38 JS: I also CCed Jason Kiss. 19:15:50 JS: Now we are waiting for him to reply. 19:16:46 Zakim, next item 19:16:46 agendum 3. "ACTION-2121: (Joanie) Correct the ATK/AT-SPI text for single and multiple selection removal." taken up [from clown] 19:16:52 action-2121? 19:16:52 action-2121 -- Joanmarie Diggs to Correct the atk/at-spi entries in seciton 5.8.3 for single selection and multiple selection when the selection is removed. -- due 2016-10-18 -- OPEN 19:16:52 http://www.w3.org/WAI/ARIA/track/actions/2121 19:17:00 JS: This is a new one, which we came up with last week. 19:17:10 JS: We were looking at single and multiple selection. 19:17:23 JS: Joanie noticed some stuff she was not particularly happy with. 19:17:33 https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#mapping_events_selection 19:17:35 JS: And she wanted to make some corrections. 19:17:44 JS: The above link is for the section we're talking about. 19:17:53 JS: Joanie added a note to the action item. 19:19:53 From my comment: 19:19:57 I'm not sure how we want to word the text for the table cell, however.... 19:19:57 Any time the selection changes, in addition to object:selection-changed on the container/parent, there should also be the following: 19:20:00 1. object:state-changed:selected with detail1 = 0 on any element which just became unselected 19:20:03 2. object:state-changed:selected with detail1 = 1 on the element which just became selected 19:20:06 Any time the focused element changes, there should also be the following: 19:20:07 https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#mapping_events_selection 19:20:08 1. object:state-changed:focused with detail1 = 0 on the element which just became unfocused 19:20:11 2. object:state-changed:focused with detail1 = 1 on the element which just became focused 19:20:14 (Aside, this seems to be what is alluded to in the MSAA column.) 19:20:17 (End of paste) 19:20:45 JD: By the way, where is IA2 in that table? 19:21:02 JS: In this case IA2 is the same as MSAA because they are MSAA events. 19:22:02 JS: We might want to modify the column title, but.... Some people suggested that because IA2 builds upon MSAA, we didn't want to do that. 19:22:08 https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#focus_state_event_table 19:26:26 JD: If focus follows selection, the object:state-changed:focused events AND associated states (focusable, focused) need to also be present. 19:26:42 JS: I think that's covered by the focus state event table (see link above) 19:26:58 JD: Maybe, but it's not clear to me that user agents will make that leap. 19:27:12 JS: As a compromise, how about I link to the focus state event table? 19:27:16 JD: Perfect, thanks! 19:28:38 JS: First question: In your notes you say "element"; should that instead be "accessible object"? 19:29:06 JD: Use whatever language is consistent with your spec. Apologies for not checking; wrote "element" out of habit (ARIA spec). 19:32:47 https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#mapping_events_state-change 19:37:42 (Group discusses ATK/AT-SPI2 event detail1 and how best to reflect the requirements in the Core AAM.) 19:39:21 JS: Do we need to test all of these? 19:39:48 JD: My ATTA is capable of it, and hopefully Gecko would pass the tests because I believe (for the most part) they are already doing this correctly. 19:40:11 JS: I will assign this action to myself now. 19:41:53 Zakim, next item 19:41:53 agendum 4. "Triage issues/actions: https://www.w3.org/WAI/ARIA/track/products/23" taken up [from clown] 19:42:25 issue-618? 19:42:25 issue-618 -- MSAA selection event mapping for single selection case when item becomes unselected -- open 19:42:25 http://www.w3.org/WAI/ARIA/track/issues/618 19:43:11 action-1553? 19:43:11 Sorry, but action-1553 does not exist. 19:43:15 action-1533 19:43:15 action-1533 -- Joanmarie Diggs to Implement Webdriver automated accessibilty testing framework for testing ARIA in ATK/AT-SPI -- due 2016-07-12 -- OPEN 19:43:15 http://www.w3.org/WAI/ARIA/track/actions/1533 19:44:21 issue-1031 19:44:21 issue-1031 -- Implement Webdriver automated accessibility testing framework for testing ARIA in various AAPIs -- open 19:44:21 http://www.w3.org/WAI/ARIA/track/issues/1031 19:44:33 action-2077 19:44:33 action-2077 -- Cynthia Shelly to Recruit people to implement Webdriver automated accessibility testing for MSAA+IA2 and AXAPI -- due 2016-06-29 -- OPEN 19:44:33 http://www.w3.org/WAI/ARIA/track/actions/2077 19:46:32 action-2056? 19:46:32 action-2056 -- Joanmarie Diggs to Coordinate the mappings for the various AAPIs of the enumerated aria-haspopup values -- due 2016-06-07 -- OPEN 19:46:32 http://www.w3.org/WAI/ARIA/track/actions/2056 19:46:36 action-2056 19:46:36 action-2056 -- Joanmarie Diggs to Coordinate the mappings for the various AAPIs of the enumerated aria-haspopup values -- due 2016-06-07 -- OPEN 19:46:36 http://www.w3.org/WAI/ARIA/track/actions/2056 19:47:08 JS: James commented on this action in June. 19:47:37 JS: James is claiming this is not backwards compatible. 19:48:00 JS: And it sounds like he is saying AXAPI isn't going to do this. 19:48:04 JS: Am I misreading this? 19:58:00 https://rawgit.com/w3c/aria/master/aria/aria.html#aria-haspopup 20:00:16 (Group discusses the backwards compatibility issue raised by James, namely that the new enumerated types will be treated as "false" in ARIA 1.0 browsers) 20:01:22 https://www.w3.org/TR/2014/REC-wai-aria-20140320/complete#aria-haspopup 20:05:45 RS: I commented on the action. 20:06:59 https://developer.gnome.org/atk/unstable/AtkValue.html#atk-value-get-value-and-text 20:07:33 https://developer.gnome.org/atk/unstable/AtkValue.html 20:07:59 https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#ariaValueNow 20:08:50 action: Joseph to change all ATK/AT-SPI uses of "AccessibleValue" interface to "Value" interface. 20:08:50 Created ACTION-2122 - Change all atk/at-spi uses of "accessiblevalue" interface to "value" interface. [on Joseph Scheuhammer - due 2016-10-25]. 20:09:17 RS: The Core AAM uses "AccessibleValue" for ATK when it should say "Value" interface. 20:09:21 JS: I will change it. 20:10:02 Zakim, part 20:10:02 leaving. As of this point the attendees have been Joanmarie_Diggs, Joseph_Scheuhammer, Rich_Schwerdtfeger, Bryan_Garaventa 20:10:02 Zakim has left #aapi 20:10:54 scribeOptions: -final 20:11:01 RRSAgent, stop