[AAPI] Minutes UIA TF Meeting Tuesday, 21 March 2017

Link: https://www.w3.org/2017/03/21-aapi-minutes.html

Plain text follows:

   [1]W3C

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

   Accessible Rich Internet Applications Working Group Teleconference

21 Mar 2017

   See also: [2]IRC log

      [2] http://www.w3.org/2017/03/21-aapi-irc

Attendees

   Present
          Joanmarie_Diggs, Joseph_Scheuhammer, Rich_Schwerdfeger

   Regrets
          Bryan_Garaventa

   Chair
          Joseph_Scheuhammer

   Scribe
          joanie

Contents

     * [3]Topics
         1. [4]ISSUE-738 (Bogdan) Verify or provide correct UIA
            mapping for role="heading".
         2. [5](All) Level of detail in UIA mappings.
         3. [6](Joseph, Joanie) Remove RELATION_POPUP_FOR from
            ATK/AT-SPI mappings of aria-haspopup
         4. [7]GH-ISSUE-536 (Joseph, Joanie) Latest
            AXRoleDescription strings for roles alertdialog and
            dialog
         5. [8]Joseph post-ARIA 1.1
     * [9]Summary of Action Items
     * [10]Summary of Resolutions
     __________________________________________________________

   <clown> agenda: this

   <scribe> scribe: joanie

ISSUE-738 (Bogdan) Verify or provide correct UIA mapping for
role="heading".

   <clown> issue-738?

   <trackbot> issue-738 -- UIA mapping for heading incorrect --
   closed

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

     [11] http://www.w3.org/WAI/ARIA/track/issues/738

   JS: Cynthia asked a question about the heading role.
   ... Bogdan provided a patch. I pulled it in.

   RS: Is it implemented?

   JS: I added a comment that it might not be implemented.
   ... I closed the issue, but I realized this might be a 1.1
   change.

   RS: Why if it's under the covers?

   JS: Before it just stated to map it to text.
   ... But arguably, everything is 1.1. So I don't have to call it
   out then?
   ... But if for UIA everything is 1.1, then we need tests for
   everything.

   RS: We don't have to do them all.
   ... We just have to do what changed in 1.1.

(All) Level of detail in UIA mappings.

   JS: We have a general request from Microsoft to put greater
   detail in the Core AAM.
   ... This request was made off-list.
   ... The last thing I heard from Bogdan was that he was willing
   to do the work.
   ... I suggested to Bogdan that he write a paragraph explaining
   the default interface should be assumed.
   ... Rather than repeating it everywhere throughout the spec.
   ... He is also going to provide some text explaining current
   versus cached.

   RS: But what are we going to do for the ATTA?

   JS: I think we agreed that we'd use cached, but Joanie is
   concerned about potential ATTA/harness timeouts should the
   calculation not come back sufficiently fast.

   RS: So the ATTA developers will need to handle that.

   JS: Also, Bogdan indicated that he'd do the work, but not when
   he'd have it done by.
   ... But this area is progressing and is no longer stalled.
   ... I guess I should ask Bogdan when he thinks he'll have it
   done by.

   RS: Joanie, will we have an ATTA for UIA done in the near
   future?

   JD: I'm not sure.

   RS: I would like to have an ETA for ATTAs next week.

   JD: <mutters something about regressions Apple introduced to
   accessibility of WebKitGtk which she has to focus on now>

(Joseph, Joanie) Remove RELATION_POPUP_FOR from ATK/AT-SPI mappings
of aria-haspopup

   JS: This is a pull request that Joanie put out about a week
   ago.

   <clown> [12]https://github.com/w3c/aria/pull/537

     [12] https://github.com/w3c/aria/pull/537

   JS: There's a RELATION_POPUP_FOR in ATK/AT-SPI, but there's
   nothing in the spec that allows the user agent to implement it.
   ... I had a couple of very small comments.

   <clown>
   [13]https://github.com/w3c/aria/pull/537#pullrequestreview-2792
   6175

     [13] https://github.com/w3c/aria/pull/537#pullrequestreview-27926175

   JS: One was wording in the ChangeLog

   JD: <explains her rationale for using "undid" rather than
   "removed">

   JS: Ok, that's fine. I will pull this in later in the week.

GH-ISSUE-536 (Joseph, Joanie) Latest AXRoleDescription strings for
roles alertdialog and dialog

   JS: [14]https://github.com/w3c/aria/pull/536
   ... This is something Joanie discovered.
   ... AXRoleDescription for alertdialog is now "web alert dialog"
   ... AXRoleDescription for dialog is now "web dialog"
   ... I pulled it in and told Joanie that she could close it if
   she thinks it's complete.

     [14] https://github.com/w3c/aria/pull/536

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

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

   JD: I can close it, but I'm not signed in and two-step
   authentication means I need to get a code on my phone, and I'm
   scribing....

   JS: I can sign in and close it.
   ... Done

Joseph post-ARIA 1.1

   RS: Joseph's employer wants to phase Joseph out his work in
   ARIA.
   ... Because they want him to work on other things.
   ... Being out before 1.1 CR is going to be problematic.

   JS: What they want is a transition plan.

   RS: We don't have the resources right now, especially during
   the CR process.
   ... I don't know who is going to own it after 1.1.

   JD: I'm willing to take on the Core AAM editorship, but NOT
   until 1.1 is done.

   <clown> [16]https://www.w3.org/WAI/ARIA/track/products/23

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

   <clown>
   [17]https://www.w3.org/Bugs/Public/buglist.cgi?component=Core%2
   0AAM&product=ARIA

     [17] https://www.w3.org/Bugs/Public/buglist.cgi?component=Core
AAM&product=ARIA

   JD: I'm behind on ATTA work, I have implementations to do in
   WebKitGtk, I have regressions introduced by others I have to
   debug and fix....
   ... However, I think I actually know more about the mappings
   and implementation than I do the authoring (hence my lousy
   examples in the ARIA spec.) ;)
   ... So given that the ARIA spec practice has been for people to
   make branches which I merge after consensus has been reached, I
   think I can take on the Core AAM (after 1.1).

   Group: (Discussion about Tracker versus Github)

   RS: Let's say we finish these issues in github that are for
   1.1.
   ... Joseph, you can tell your employer that we will try to
   phase you out and phase Joanie in.
   ... The exact timeline remains to be determined.

   action-2117

   <trackbot> action-2117 -- Joseph Scheuhammer to Update core-aam
   to not expose aria-details relationships that reference
   elements that are hidden. -- due 2016-09-22 -- PENDINGREVIEW

   <trackbot> [18]http://www.w3.org/WAI/ARIA/track/actions/2117

     [18] http://www.w3.org/WAI/ARIA/track/actions/2117

   RS: You showed that one to us.

   JS: Yes I did.

   RS: Close it.
   ... Now you only have nine.

   <clown> [19]https://www.w3.org/WAI/PF/Group/track/products/26

     [19] https://www.w3.org/WAI/PF/Group/track/products/26

   JS: There's also the AccName spec.

   JD: (only half-joking) Wait, a minute....

   <clown> [20]https://www.w3.org/WAI/ARIA/track/products/26

     [20] https://www.w3.org/WAI/ARIA/track/products/26

   RS + JS: That used to be part of the Core AAM, but was pulled
   out to be referenced by other specs.

   JS: Somebody and some point moved a bunch of items from the
   ARIA tracker to AccName without any explanation.
   ... Also Cynthia raised a number of issues because Microsoft
   was having trouble implementing it and needed more information.
   ... Cynthia wanted a list, specific to SVG. But that doesn't
   belong in the AccName because that is host-language
   independent.

Summary of Action Items

Summary of Resolutions

   [End of minutes]

Received on Tuesday, 21 March 2017 20:18:23 UTC