[aapi] Minutes: UAI TF Meeting Tue 20 October 2015

Link: http://www.w3.org/2015/10/20-aapi-minutes.html

Plain text follows:
   [1]W3C

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

           Protocols and Formats Working Group Teleconference

20 Oct 2015

   See also: [2]IRC log

      [2] http://www.w3.org/2015/10/20-aapi-irc

Attendees

   Present
          Joseph_Scheuhammer, Rich_Schwerdtfeger, Joanmarie_Diggs,
          Bryan_Garaventa, Cynthia_Shelly

   Regrets
   Chair
          Joseph_Scheuhammer

   Scribe
          joanie

Contents

     * [3]Topics
         1. [4]Check that all new ARIA 1.1 spec have actions.
         2. [5]Add interfaces where appropriate, e.g.
            IAccessibleText
         3. [6]Check that all new ARIA 1.1 spec have actions.
     * [7]Summary of Action Items
     __________________________________________________________

   <trackbot> Date: 20 October 2015

   <clown> agenda: this

   <scribe> scribe: joanie

Check that all new ARIA 1.1 spec have actions.

   JS: The main purpose of this meeting is to start getting ready
   for ARIA 1.1.
   ... In particular getting the mapping spec and name computation
   spec ready for CR.
   ... My concern is that there might be some items that fell
   through the cracks and are in the ARIA spec, but not the
   mapping spec.
   ... So I want to put that on people's radar.

   RS: Michael is supposed to identify testing criteria and write
   the testable statements.

   JS: That will work.

Add interfaces where appropriate, e.g. IAccessibleText

   JS: This came up in an email last week about role="text".
   ... The mapping spec just says to give it a role.
   ... Rich asked if it should also implement the accessible text
   interface.
   ... I looked at the HTML spec and noticed it indicates
   interfaces that should be implemented.
   ... Our mapping spec doesn't make this indiciation. Should it?

   <clown>
   [8]http://rawgit.com/w3c/aria/master/html-aam/html-aam.html#el-
   figure

      [8] http://rawgit.com/w3c/aria/master/html-aam/html-aam.html#el-figure

   JS: For example, in the HTML mapping spec (link above), if you
   look at their entries, they have a role, object attributes,
   name:, and relations.
   ... We don't generally go into that detail; we identify the
   role for mapping.

   <clown>
   [9]http://w3c.github.io/aria/core-aam/core-aam.html#role-map-gr
   id

      [9] http://w3c.github.io/aria/core-aam/core-aam.html#role-map-grid

   RS: We indicate the table interface for table/grid.

   JS: Confirmed.

   RS: I don't think we need to get into fine granularity.
   ... I think we have to implement the accessible text interface.

   JS: For grid??

   RS: For IA2, for instance, you can get a given header for a
   specified cell.

   <clown>
   [10]http://w3c.github.io/aria/core-aam/core-aam.html#role-map-g
   rid

     [10] http://w3c.github.io/aria/core-aam/core-aam.html#role-map-grid

   JS: Does ATK have a table interface, and should it be
   implemented for grid?

   JD: Yes.
   ... For what it's worth, in practice implementors already do
   that for my platform.
   ... But it should be added to our mapping spec.

   RS + JS: (notes that the new table role is not listed in our
   spec)

   JS: Volunteers?

   RS: I could do it after TPAC.
   ... It should pretty much be what we have for grid.

   JS: Did we also add new roles for row?

   <clown> ACTION: Rich to determine mappings for ARIA 1.1 table
   and cell role for all AAPI platforms. [recorded in
   [11]http://www.w3.org/2015/10/20-aapi-irc]

     [11] http://www.w3.org/2015/10/20-aapi-irc]

   <trackbot> Created ACTION-1737 - Determine mappings for aria
   1.1 table and cell role for all aapi platforms. [on Richard
   Schwerdtfeger - due 2015-10-27].

   JD: No. But we did for cell.

   <clown> action-1737

   <trackbot> action-1737 -- Richard Schwerdtfeger to Determine
   mappings for aria 1.1 table and cell role for all aapi
   platforms. -- due 2015-10-27 -- OPEN

   <trackbot>
   [12]https://www.w3.org/WAI/PF/Group/track/actions/1737

     [12] https://www.w3.org/WAI/PF/Group/track/actions/1737

   JD: There was some discussion about possibly deprecating
   gridcell, but nothing has been done in that regard yet.

   <clown> action-1737

   <trackbot> action-1737 -- Richard Schwerdtfeger to Determine
   mappings for ARUA 1.1 table and cell role for all AAPI
   platforms. -- due 2015-11-13 -- OPEN

   <trackbot>
   [13]https://www.w3.org/WAI/PF/Group/track/actions/1737

     [13] https://www.w3.org/WAI/PF/Group/track/actions/1737

   Group: (Does mapping for table and cell roles during the
   meeting)

   <cyns>
   [14]https://msdn.microsoft.com/en-us/library/windows/desktop/ee
   671624(v=vs.85).aspx

     [14]
https://msdn.microsoft.com/en-us/library/windows/desktop/ee671624(v=vs.85).aspx

   <richardschwerdtfeger>
   [15]https://www.w3.org/WAI/PF/Group/track/actions/1737

     [15] https://www.w3.org/WAI/PF/Group/track/actions/1737

Check that all new ARIA 1.1 spec have actions.

   JS: The process today is to say if we can do items in the 1.1
   timeframe or need to punt it to 2.0.

   <clown> action-842?

   <trackbot> action-842 -- Cynthia Shelly to Create a diagram to
   support section 1.2 A11Y vs DOM tree -- due 2015-09-30 -- OPEN

   <trackbot>
   [16]https://www.w3.org/WAI/PF/Group/track/actions/842

     [16] https://www.w3.org/WAI/PF/Group/track/actions/842

   JS: The first one is Cynthia's (action-842).

   CS: This will not happen in the 1.1 timeframe.

   JS: Do we want to kill this entirely?

   Group: Let's close this action.

   RESOLUTION: Close action-842.

   <clown> action-1104

   <trackbot> action-1104 -- Cynthia Shelly to Define what the
   accessibility API mapping is for UIA on aria-describedby in
   section 5.5.1 table when the element does not exist in the
   accessibility tree such as when css: display:none applies --
   due 2015-09-15 -- OPEN

   <trackbot>
   [17]https://www.w3.org/WAI/PF/Group/track/actions/1104

     [17] https://www.w3.org/WAI/PF/Group/track/actions/1104

   JS: Action-1104 is also Cynthia's.

   CS: Give me three months, until January 1st.

   JS: Does that fit in the ARIA 1.1 time frame?

   RS: We want to go into CR during the first quarter as I
   understand it.
   ... It doesn't have to be done by January 1st; it needs to be
   in the spec by January 1st. However, before then would be
   better. We need to lock things down.

   CS: I will try to do it earlier.

   <clown> action-1309

   <trackbot> action-1309 -- Cynthia Shelly to Determine the best
   place to map aria-colindex and aria-rowindex for UIA. -- due
   2015-08-01 -- OPEN

   <trackbot>
   [18]https://www.w3.org/WAI/PF/Group/track/actions/1309

     [18] https://www.w3.org/WAI/PF/Group/track/actions/1309

   JS: This one is also Cynthia's.

   CS: I haven't done it yet. But it can be done in the ARIA 1.1.
   timeframe.
   ... December 1st.

   <clown> action-1373

   <trackbot> action-1373 -- Cynthia Shelly to Create a test case
   for when aria-posinset and aria-setsize are provided explicitly
   on some but not all elements. -- due 2015-09-15 -- OPEN

   <trackbot>
   [19]https://www.w3.org/WAI/PF/Group/track/actions/1373

     [19] https://www.w3.org/WAI/PF/Group/track/actions/1373

   JS: Cynthia?

   CS: Also December 1st.

   JS: It's a test case so you might want to sync up with Michael
   Cooper.

   <clown> action-1409

   <trackbot> action-1409 -- Joanmarie Diggs to Monitor progress
   of bug against atk in gnome's bugzilla requesting new position,
   level, and other api be added
   ([20]https://bugzilla.gnome.org/show_bug.cgi?id=727453) -- due
   2015-10-27 -- OPEN

     [20] https://bugzilla.gnome.org/show_bug.cgi?id=727453)

   <trackbot>
   [21]https://www.w3.org/WAI/PF/Group/track/actions/1409

     [21] https://www.w3.org/WAI/PF/Group/track/actions/1409

   JD: I haven't had time to add new API to ATK yet.
   ... I still plan to.

   <clown> scribenick: clonw

   <clown> scribenick: clown

   JD: Let's move it to aria 2.0
   ... But it's not blocking, it simply doesn't change anything
   ... There is a mapping through the object attributes.

   <joanie> scribe: joanie

   <clown> action-1527

   <trackbot> action-1527 -- Cynthia Shelly to Investigate the
   proper uia mappings for aria-current -- due 2015-10-01 -- OPEN

   <trackbot>
   [22]https://www.w3.org/WAI/PF/Group/track/actions/1527

     [22] https://www.w3.org/WAI/PF/Group/track/actions/1527

   JS: Cynthia, this one is yours.

   CS: Is aria-current still current?

   JS: It's still there.

   <clown>
   [23]http://w3c.github.io/aria/core-aam/core-aam.html#ariaCurren
   t

     [23] http://w3c.github.io/aria/core-aam/core-aam.html#ariaCurrent

   JD: If memory serves me, James Craig raised some concerns. Have
   those been resolved?

   (Group is not sure. It was raised on list but not at a meeting.
   Therefore, we need to go back and look.)

   JS: We have a mapping for ATK. I don't know if a test will
   pass, but it is mapped.

   <clown> action-1527

   <trackbot> action-1527 -- Cynthia Shelly to Investigate the
   proper uia mappings for aria-current -- due 2015-10-01 -- OPEN

   <trackbot>
   [24]https://www.w3.org/WAI/PF/Group/track/actions/1527

     [24] https://www.w3.org/WAI/PF/Group/track/actions/1527

   JS: Cynthia, could you update the action since you have an idea
   about the mapping for your platform?

   CS: Is core-aam normative? Can I change it?

   JS: As long as it's a working draft, you can change it.

   CS: For now the mapping will be in aria-properties. But we may
   wish to improve the situation down the road.

   JS: To me, that change would be for 2.0.

   CS: It wouldn't make the existing mapping wrong, but there'd be
   another (better) place for implementors.

   RS: We could probably update the spec for something like that.

   JD: Based on my experience (1.0 hit CR before Igalia was a W3C
   member), I pointed out a number of things that were incorrect
   in the 1.0 mapping spec. I was told that the changes which
   would make things correct were substantial and would have to be
   postponed to 1.1. Thus I think we would have to roll a 1.2
   release of the mapping spec to make any changes.
   ... I think rolling such a release would be easy and worth
   doing.

   JS: So do we want to put it in aria-properties for now?

   <clown> action-1527

   <trackbot> action-1527 -- Cynthia Shelly to Investigate the
   proper uia mappings for aria-current -- due 2015-10-01 -- OPEN

   <trackbot>
   [25]https://www.w3.org/WAI/PF/Group/track/actions/1527

     [25] https://www.w3.org/WAI/PF/Group/track/actions/1527

   <clown> scribenick: clown

   CS: I've put a note in the action to use AriaProperties for
   now.

   JS: Assign the action to me now.
   ... You have given me the information, and I can now do the
   edits.
   ... And, that will be it for this meeting.
   ... Have a good meeting at TPAC next week, everyone (who is
   going).

   <joanie> scribe: joanie

Summary of Action Items

   [NEW] ACTION: Rich to determine mappings for ARIA 1.1 table and
   cell role for all AAPI platforms. [recorded in
   [26]http://www.w3.org/2015/10/20-aapi-irc]

     [26] http://www.w3.org/2015/10/20-aapi-irc

   [End of minutes]

Received on Tuesday, 20 October 2015 20:10:19 UTC