[AAPI] Minutes UAI TF Meeting, Tuesday 18 October 2016

URL: https://www.w3.org/2016/10/18-aapi-minutes.html

Plain text follows:

   [1]W3C

      [1] http://www.w3.org/

   Accessible Rich Internet Applications Working Group Teleconference

18 Oct 2016

   See also: [2]IRC log

      [2] http://www.w3.org/2016/10/18-aapi-irc

Attendees

   Present
          Joanmarie_Diggs, Joseph_Scheuhammer, Rich_Schwerdtfeger,
          Bryan_Garaventa

   Regrets
   Chair
          Joseph_Scheuhammer

   Scribe
          joanie

Contents

     * [3]Topics
         1. [4]ISSUE-1038/ISSUE-1026: (Bogdan, James) Mappings for
            feed, figure, and term.
         2. [5]ISSUE-676/: (Joseph) Adding MSAA+IA2 action,
            interface, and relations to role mappings.
         3. [6]ACTION-2121: (Joanie) Correct the ATK/AT-SPI text
            for single and multiple selection removal.
         4. [7]Triage issues/actions:
            https://www.w3.org/WAI/ARIA/track/products/23
     * [8]Summary of Action Items
     * [9]Summary of Resolutions
     __________________________________________________________

   <clown> agenda: this

   <scribe> scribe: joanie

   <clown>
   [10]https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#r
   ole-map-heading

     [10]
https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-heading

ISSUE-1038/ISSUE-1026: (Bogdan, James) Mappings for feed, figure, and
term.

   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?

ISSUE-676/: (Joseph) Adding MSAA+IA2 action, interface, and relations
to role mappings.

   <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> [11]http://www.w3.org/WAI/ARIA/track/issues/676

     [11] 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>
   [12]https://lists.w3.org/Archives/Public/public-aria/2016Oct/00
   59.html

     [12] 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.

ACTION-2121: (Joanie) Correct the ATK/AT-SPI text for single and
multiple selection removal.

   <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> [13]http://www.w3.org/WAI/ARIA/track/actions/2121

     [13] 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>
   [14]https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#m
   apping_events_selection

     [14]
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>
   [15]https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#m
   apping_events_selection

     [15]
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>
   [16]https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#f
   ocus_state_event_table

     [16]
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>
   [17]https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#m
   apping_events_state-change

     [17]
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.

Triage issues/actions:
[18]https://www.w3.org/WAI/ARIA/track/products/23

     [18] https://www.w3.org/WAI/ARIA/track/products/23

   <clown> issue-618?

   <trackbot> issue-618 -- MSAA selection event mapping for single
   selection case when item becomes unselected -- open

   <trackbot> [19]http://www.w3.org/WAI/ARIA/track/issues/618

     [19] 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> [20]http://www.w3.org/WAI/ARIA/track/actions/1533

     [20] 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> [21]http://www.w3.org/WAI/ARIA/track/issues/1031

     [21] 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> [22]http://www.w3.org/WAI/ARIA/track/actions/2077

     [22] 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> [23]http://www.w3.org/WAI/ARIA/track/actions/2056

     [23] 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> [24]http://www.w3.org/WAI/ARIA/track/actions/2056

     [24] 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>
   [25]https://rawgit.com/w3c/aria/master/aria/aria.html#aria-hasp
   opup

     [25] 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)

   [26]https://www.w3.org/TR/2014/REC-wai-aria-20140320/complete#a
   ria-haspopup

     [26]
https://www.w3.org/TR/2014/REC-wai-aria-20140320/complete#aria-haspopup

   RS: I commented on the action.

   <clown>
   [27]https://developer.gnome.org/atk/unstable/AtkValue.html#atk-
   value-get-value-and-text

     [27]
https://developer.gnome.org/atk/unstable/AtkValue.html#atk-value-get-value-and-text

   <clown>
   [28]https://developer.gnome.org/atk/unstable/AtkValue.html

     [28] https://developer.gnome.org/atk/unstable/AtkValue.html

   <clown>
   [29]https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#a
   riaValueNow

     [29]
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
   [30]http://www.w3.org/2016/10/18-aapi-irc]

     [30] 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.

Summary of Action Items

   [NEW] ACTION: Joseph to change all ATK/AT-SPI uses of
   "AccessibleValue" interface to "Value" interface. [recorded in
   [31]http://www.w3.org/2016/10/18-aapi-irc]

     [31] http://www.w3.org/2016/10/18-aapi-irc

Summary of Resolutions

   [End of minutes]

Received on Tuesday, 18 October 2016 20:18:23 UTC