See also: IRC log
<clown> agenda: this
<scribe> scribe: joanie
<clown> https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-heading
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.
... And the answer is yes, because you (Rich) sent out emails
to Bogdan and James Craig.
RS: Correct.
JS: Any other comments or questions?
<clown> issue-676?
<trackbot> issue-676 -- Is it useful to identify MSAA+IA2 and ATK/AT-SPI actions, interfaces, and relations in the mappings? -- open
<trackbot> http://www.w3.org/WAI/ARIA/track/issues/676
JS: There's an issue raised by
Jason Kiss to add actions, interfaces, and relations to the
mappings.
... We did it for ATK; Cynthia seems to have done the same for
UIA.
<clown> https://lists.w3.org/Archives/Public/public-aria/2016Oct/0059.html
JS: MSAA and IA2 seems to be the
only things missing.
... I sent an email to Alex Surkov (see link above).
... I asked him to look through it and tell me where the
differences are.
... I also CCed Jason Kiss.
... Now we are waiting for him to reply.
<clown> action-2121?
<trackbot> 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
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/2121
JS: This is a new one, which we
came up with last week.
... We were looking at single and multiple selection.
... Joanie noticed some stuff she was not particularly happy
with.
<clown> https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#mapping_events_selection
JS: And she wanted to make some
corrections.
... The above link is for the section we're talking
about.
... Joanie added a note to the action item.
From my comment:
I'm not sure how we want to word the text for the table cell, however....
Any time the selection changes, in addition to object:selection-changed on the container/parent, there should also be the following:
1. object:state-changed:selected with detail1 = 0 on any element which just became unselected
2. object:state-changed:selected with detail1 = 1 on the element which just became selected
Any time the focused element changes, there should also be the following:
<clown> https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#mapping_events_selection
1. object:state-changed:focused with detail1 = 0 on the element which just became unfocused
2. object:state-changed:focused with detail1 = 1 on the element which just became focused
(Aside, this seems to be what is alluded to in the MSAA column.)
(End of paste)
JD: By the way, where is IA2 in that table?
JS: In this case IA2 is the same
as MSAA because they are MSAA events.
... 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.
<clown> https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#focus_state_event_table
JD: If focus follows selection, the object:state-changed:focused events AND associated states (focusable, focused) need to also be present.
JS: I think that's covered by the focus state event table (see link above)
JD: Maybe, but it's not clear to me that user agents will make that leap.
JS: As a compromise, how about I link to the focus state event table?
JD: Perfect, thanks!
JS: First question: In your notes you say "element"; should that instead be "accessible object"?
JD: Use whatever language is consistent with your spec. Apologies for not checking; wrote "element" out of habit (ARIA spec).
<clown> https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#mapping_events_state-change
(Group discusses ATK/AT-SPI2 event detail1 and how best to reflect the requirements in the Core AAM.)
JS: Do we need to test all of these?
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.
JS: I will assign this action to myself now.
<clown> issue-618?
<trackbot> issue-618 -- MSAA selection event mapping for single selection case when item becomes unselected -- open
<trackbot> http://www.w3.org/WAI/ARIA/track/issues/618
<clown> action-1553?
<trackbot> Sorry, but action-1553 does not exist.
action-1533
<trackbot> action-1533 -- Joanmarie Diggs to Implement Webdriver automated accessibilty testing framework for testing ARIA in ATK/AT-SPI -- due 2016-07-12 -- OPEN
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/1533
<clown> issue-1031
<trackbot> issue-1031 -- Implement Webdriver automated accessibility testing framework for testing ARIA in various AAPIs -- open
<trackbot> http://www.w3.org/WAI/ARIA/track/issues/1031
<clown> action-2077
<trackbot> action-2077 -- Cynthia Shelly to Recruit people to implement Webdriver automated accessibility testing for MSAA+IA2 and AXAPI -- due 2016-06-29 -- OPEN
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/2077
<clown> action-2056?
<trackbot> action-2056 -- Joanmarie Diggs to Coordinate the mappings for the various AAPIs of the enumerated aria-haspopup values -- due 2016-06-07 -- OPEN
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/2056
action-2056
<trackbot> action-2056 -- Joanmarie Diggs to Coordinate the mappings for the various AAPIs of the enumerated aria-haspopup values -- due 2016-06-07 -- OPEN
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/2056
JS: James commented on this
action in June.
... James is claiming this is not backwards compatible.
... And it sounds like he is saying AXAPI isn't going to do
this.
... Am I misreading this?
<clown> https://rawgit.com/w3c/aria/master/aria/aria.html#aria-haspopup
(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)
https://www.w3.org/TR/2014/REC-wai-aria-20140320/complete#aria-haspopup
RS: I commented on the action.
<clown> https://developer.gnome.org/atk/unstable/AtkValue.html#atk-value-get-value-and-text
<clown> https://developer.gnome.org/atk/unstable/AtkValue.html
<clown> https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#ariaValueNow
<clown> ACTION: Joseph to change all ATK/AT-SPI uses of "AccessibleValue" interface to "Value" interface. [recorded in http://www.w3.org/2016/10/18-aapi-irc]
<trackbot> Created ACTION-2122 - Change all atk/at-spi uses of "accessiblevalue" interface to "value" interface. [on Joseph Scheuhammer - due 2016-10-25].
RS: The Core AAM uses "AccessibleValue" for ATK when it should say "Value" interface.
JS: I will change it.
This is scribe.perl Revision: 1.148 of Date: 2016/10/11 12:55:14 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found embedded ScribeOptions: -final *** RESTARTING DUE TO EMBEDDED OPTIONS *** Found Scribe: joanie Inferring ScribeNick: joanie Default Present: Joanmarie_Diggs, Joseph_Scheuhammer, Rich_Schwerdtfeger, Bryan_Garaventa Present: Joanmarie_Diggs Joseph_Scheuhammer Rich_Schwerdtfeger Bryan_Garaventa Found Date: 18 Oct 2016 People with action items: joseph WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]