[AAPI] Minutes UAI TF Meeting, Tuesday 19 April 2016

URL: https://www.w3.org/2016/04/19-aapi-minutes.html

Plain text follows:

   [1]W3C

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

   Accessible Rich Internet Applications Working Group Teleconference

19 Apr 2016

   See also: [2]IRC log

      [2] http://www.w3.org/2016/04/19-aapi-irc

Attendees

   Present
          Joanmarie_Diggs, Joseph_Scheuhammer, Cynthia_Shelly,
          Bryan_Garaventa

   Regrets
          Richard_Schwerdtfeger

   Chair
          Joseph_Scheuhammer

   Scribe
          joanie

Contents

     * [3]Topics
         1. [4]ACTION-1737 (Joseph/Cynthia/Joanie) Confirm the UIA
            mappings for table/cell were pulled in correctly, and
            the AXAPI mappings.
         2. [5]ACTION-1718 (Cynthia) Review UIA mappings for
            aria-checked on radio buttons and menuitem radio
            buttons.
         3. [6]ACTION-2032 (Cynthia) Review new UIA example for
            the AAPI explanatory text.
         4. [7]ACTION-2022/ACTION-1668 (All) Add IA2_ROLE_LANDMARK
            for IA2. Latest developments, including mapping of
            role="form".
         5. [8]ACTION-2032 (Cynthia) Review new UIA example for
            the AAPI explanatory text.
         6. [9]ACTION-2043 (Joseph/Cynthia) Review UIA mapping of
            role="status".
         7. [10]ACTION-2022/ACTION-1668 (All) Add
            IA2_ROLE_LANDMARK for IA2. Latest developments,
            including mapping of role="form".
     * [11]Summary of Action Items
     * [12]Summary of Resolutions
     __________________________________________________________

   <scribe> agenda: this

   <joanie> scribe: joanie

ACTION-1737 (Joseph/Cynthia/Joanie) Confirm the UIA mappings for
table/cell were pulled in correctly, and the AXAPI mappings.

   <clown> action-1737?

   <trackbot> action-1737 -- Joseph Scheuhammer to Determine
   mappings for ARIA 1.1 table and cell role for all AAPI
   platforms. -- due 2015-11-13 -- PENDINGREVIEW

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

     [13] http://www.w3.org/WAI/ARIA/track/actions/1737

   JS: I found a whole bunch of actions in tracker that were edits
   which had been made.
   ... These just need one final review/look-at.
   ... This one is table and cell roles.

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

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

   JS: So for cell, the above URL has the content.
   ... (Reads UIA)

   CS: That sounds right.

   JS: Joanie?

   JD: I think that's fine. Though I'm not 100% sure if we should
   also mention access via the Table interface.

   JS: And AXAPI?

   JD: If you remind me when I'm not scribing, I can look at the
   WebKit code and confirm if what you have jives with that
   implementation.

   JS: Please do so.
   ... In the meantime, I'm closing this action.

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

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

   JS: If you (Joanie) have any changes/corrections, I can reopen
   it.
   ... The other one is table (above URL)
   ... (Reads UIA text from above URL)

   CS: That looks correct.

   JS: I'll ask Joanie to look at ATK/AT-SPI2.

   JD: The table mapping for my platform looks fine.

   JS: This covers the table interface here, and we assume cells
   are in tables, right?
   ... Also, when you look at AXAPI for cell, please do so for
   table.

   JD: Ok.

   JS: I've already closed the action.

ACTION-1718 (Cynthia) Review UIA mappings for aria-checked on radio
buttons and menuitem radio buttons.

   <clown> action-1718?

   <trackbot> action-1718 -- Joseph Scheuhammer to Check that the
   UIA mappings for aria-checked are correct for radio buttons and
   menuitem radio buttons. -- due 2016-02-02 -- PENDINGREVIEW

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

     [16] http://www.w3.org/WAI/ARIA/track/actions/1718

   JS: This action was done a while ago.
   ... It's UIA mappings for aria-checked for radio buttons and
   menuitem radio buttons.
   ... Cynthia provided me with text.
   ... I brought it up to date around CSUN.

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

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

   JS: The URL for the mappings is above.
   ... The UIA content is a lot.
   ... (Reads text from spec)

   CS: (Confirms text being read is correct)

   JS: This action is just dealing with UIA.
   ... Can we close this?

   CS: Yes.
   ... Bryan, this is a bug you reported a while ago.

   BG: Yay! :)

   JS: And it's a slightly different mapping from before and
   should be tested.

   BG: Progress is wonderful!

ACTION-2032 (Cynthia) Review new UIA example for the AAPI explanatory
text.

   <clown> action-2032?

   <trackbot> action-2032 -- Joseph Scheuhammer to Provide a new
   example for the accessibility api explanatory text. -- due
   2016-03-01 -- PENDINGREVIEW

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

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

   JS: Another action related to Cynthia.

   CS: I'll be back in my office shortly.

ACTION-2022/ACTION-1668 (All) Add IA2_ROLE_LANDMARK for IA2. Latest
developments, including mapping of role="form".

   <clown> action-2022?

   <trackbot> action-2022 -- Richard Schwerdtfeger to Followup
   with alex about ia2 discussion re: adding a landmark role,
   similar to atk -- due 2016-02-23 -- OPEN

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

     [19] http://www.w3.org/WAI/ARIA/track/actions/2022

   JS: There was discussion last week and on the various mailing
   lists.
   ... We decided to go the same route that ATK/AT-SPI2 does.
   ... Namely, the role is LANDMARK, and an object attribute
   provides the actual landmark type/role.
   ... I went through the entire mapping spec and made that
   switch.

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

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

   JS: For example, the URL above has complementary.
   ... (Reads from spec)
   ... We decided to do that last week.
   ... In the meantime, there was some discussion between Rich,
   Freedom Scientific, and Alex.
   ... Alex asked about role="form", which is a landmark.

   <clown> IA2_ROLE_FORM

   JS: But in IA2 (and ATK), it has its own form.
   ... And Alex's question is do we change that?
   ... Rich's discussion with Freedom Scientific is that we change
   it.

   BG: That's fine with me.

   <clown>
   [21]https://lists.w3.org/Archives/Public/public-aria/2016Apr/01
   38.html

     [21] https://lists.w3.org/Archives/Public/public-aria/2016Apr/0138.html

   BG: With a regular form, you cannot jump to it now like you can
   with other landmarks.

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

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

   JS: The URL above is where Rich said we should change it.
   ... The URL above has the mapping.
   ... Do you want to change this in ATK to be interoperable?

   <clown> scribenick: clown

   <joanie> CS: Are you sure you want to change this because it
   seems like a breaking change.

   JD: short answer is that I don't care.
   ... but, what does the community at large want?
   ... If a form is a landmark, it should have ROLE_LANDMARK, and
   if form is not a landmark, it shouldn't.
   ... Similarly for the HTML5 <form> element.
   ... Long way of saying, do what everyone else does.

   <joanie> scribe: joanie

   JS: In terms of role="form", it's a subclass of landmark.
   ... As far as ARIA is concerned.
   ... I can check the HTML AAM to see what it says about the form
   element.
   ... That AAM defers to us.
   ... So I think the ATK mappings change in the same way the IA2
   mappings change.

   JD: Fine with me.
   ... I do have a comment about the HTML AAM.

   <clown> scribenick: clown

   JD: Thinking out loud…
   ... the aria role form is a landmark.
   ... the html form element is going to be a landmark
   ... but should the HTML-AAM defer to us?
   ... I would have to look at orca's code to see what it does.

   JS: FF always exposes the xml-roles property, and copies what's
   in the role="<value>"

   JD: I don't know if an HTML form element is exposing an
   xml-roles attribute.
   ... that is going to change when gecko implements the new way
   of exposing landmarks.
   ... The question is: is an HTML form element a landmark or not?
   ... If it isn't, then it shouldn't be mapped that way.

   BG: If there are multiple form elements on a page, it would be
   helpful to find them if they are landmarks.

   <joanie> scribe: joanie

   JS: What do you want me to do if anything?
   ... Should I reply to Rich's email asking about HTML forms?

   JD: I think that what happens with respect to HTML forms is
   independent of how we map ARIA landmark forms.
   ... However, I do think an email discussion on this matter
   would be good.

   BG: I could ask around.

   JS: Does the HTML A11y task force still meet?

   CS + JD: No.

   CS: But they work in github.

   JS: I'll open an issue there then.

   <clown>
   [23]https://w3c.github.io/aria/core-aam/core-aam.html#role-map-
   form

     [23] https://w3c.github.io/aria/core-aam/core-aam.html#role-map-form

   JS: Cynthia, above is the URL for form for UIA.

   <clown>
   [24]https://w3c.github.io/aria/core-aam/core-aam.html#role-map-
   form

     [24] https://w3c.github.io/aria/core-aam/core-aam.html#role-map-form

   CS: The UIA one looks fine for me.
   ... Landmark isn't a role; it's a type.

   JS: Right, I don't think you're impacted by the decision
   related to forms.

   CS: Correct.

   JS: I will keep this action about IA2_ROLE_LANDMARK open until
   I get final confirmation from Alex.
   ... But I think it's essentially finished.
   ... And I'll raise an issue in github about HTML forms and
   whether or not they are landmarks.
   ... And Bryan will ask the greater community on WebAim, etc.

ACTION-2032 (Cynthia) Review new UIA example for the AAPI explanatory
text.

   <clown> action-2032?

   <trackbot> action-2032 -- Joseph Scheuhammer to Provide a new
   example for the accessibility api explanatory text. -- due
   2016-03-01 -- PENDINGREVIEW

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

     [25] http://www.w3.org/WAI/ARIA/track/actions/2032

   JS: This is in the section about differences between the
   accessibility APIs on the platforms.

   <clown>
   [26]https://rawgit.com/w3c/aria/ACTION-1569-%282%29/core-aam/co
   re-aam.html#uia

     [26]
https://rawgit.com/w3c/aria/ACTION-1569-%282%29/core-aam/core-aam.html#uia

   JS: Cynthia, you wanted to change an example.

   <clown>
   [27]https://rawgit.com/w3c/aria/ACTION-1569-%282%29/core-aam/co
   re-aam.html#uia

     [27]
https://rawgit.com/w3c/aria/ACTION-1569-%282%29/core-aam/core-aam.html#uia

   JS: It's currently got the treeitem example; it used to be a
   button, I think.
   ... It's in the first paragraph.

   CS: That looks like the one I gave you.
   ... There was some feedback that this was a complicated and
   confusing example.
   ... Which it is, but the concept is complicated and confusing.
   ... So I'm fine with it.
   ... We might get feedback that we should have a different
   example.

   <clown>
   [28]https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#u
   ia

     [28] https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#uia

   CS: But I couldn't come up with a better one.

   JS: Correction, the previous URL was not correct. The one I
   just put in (above) is correct.

   CS: That's easier to read. It looks correct too.

   JS: I'm closing this action then.
   ... There's still one more action on issue-540.
   ... I will check with Jason about that action later this week.

ACTION-2043 (Joseph/Cynthia) Review UIA mapping of role="status".

   <clown> action-2043?

   <trackbot> action-2043 -- Joseph Scheuhammer to Modify UIA
   mapping of role="status" -- due 2016-03-28 -- PENDINGREVIEW

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

     [29] http://www.w3.org/WAI/ARIA/track/actions/2043

   JS: This is another one for which I did a pull, or otherwise
   took your content.

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

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

   JS: This is the UIA mapping for the status role.
   ... The URL is above.

   CS: That looks fine.

   JS: It's different now from the other platforms.

   JD: If a role="status" element is nothing like a status bar,
   then it shouldn't be mapped to ROLE_STATUS_BAR.

   CS: I don't think it's like a status bar (e.g., it's not at the
   bottom of the window).

   JD: Since I'm scribing I cannot give it a ton of thought at
   this moment?

   JS: Do we want to change the mappings for IA2 and ATK?
   ... And if we do, what would the mappings be?

   CS: Probably the same as I did, with a "polite" live setting.

   JS: Part of me wants to let sleeping dogs lie; part of me wants
   to figure this out.

   JD: Does it make sense to raise this topic as an email and/or
   action?

   action Joseph to begin discussion about whether or not the
   mappings for role="status" should be changed for IA2 and
   ATK/AT-SPI2

   <trackbot> Created ACTION-2051 - Begin discussion about whether
   or not the mappings for role="status" should be changed for ia2
   and atk/at-spi2 [on Joseph Scheuhammer - due 2016-04-26].

   JS: I think there's already a discussion on github about this.

   BG: I'm working on an email to the WebAim group now. And will
   provide the feedback I receive.

   JS: Do you want advice?

   BG: No thanks.

ACTION-2022/ACTION-1668 (All) Add IA2_ROLE_LANDMARK for IA2. Latest
developments, including mapping of role="form".

   <clown> action-1375?

   <trackbot> Sorry, but action-1375 does not exist.

   <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 2016-03-29 -- OPEN

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

     [31] http://www.w3.org/WAI/ARIA/track/actions/1373

   JS: (Reads action-1373)

   CS: I haven't done any actions this week.
   ... Leave them overdue.

   JS: There's a note in here that this should coincide with the
   1.1 test case creation.

   CS: When is that date? Has the test creation begun?

   JS: The form to enter these things is up and running.
   ... I know Rich had done some work on SVG.
   ... I'll change the due date on action-1373 to May 19th.

   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
   ([32]https://bugzilla.gnome.org/show_bug.cgi?id=727453) -- due
   2016-04-07 -- OPEN

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

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

     [33] http://www.w3.org/WAI/ARIA/track/actions/1409

   <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
   ([34]https://bugzilla.gnome.org/show_bug.cgi?id=727453) -- due
   2016-04-07 -- OPEN

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

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

     [35] http://www.w3.org/WAI/ARIA/track/actions/1409

   JS: This is on Joanie.

   <clown> [36]https://bugzilla.gnome.org/show_bug.cgi?id=727453

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

   JD: It's bubbling up (honest)
   ... Don't change the due date.

   <clown> action-1533?

   <trackbot> action-1533 -- Joanmarie Diggs to Investigate and
   possibly create a minimal/skeleton javascript at-spi2 listener
   with the aim of automating the 1.1 tests. -- due 2016-03-15 --
   OPEN

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

     [37] http://www.w3.org/WAI/ARIA/track/actions/1533

   JD: This is automated testing work. Don't change the due date.

   action-1593

   <trackbot> action-1593 -- Cynthia Shelly to Compare
   implementations of AAPI managed states and look for gaps. --
   due 2016-03-29 -- OPEN

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

     [38] http://www.w3.org/WAI/ARIA/track/actions/1593

   JS: (Reads the action)

   <clown> [39]https://www.w3.org/WAI/ARIA/track/issues/706

     [39] https://www.w3.org/WAI/ARIA/track/issues/706

   CS: Leave this one overdue.
   ... I should do this soon.

   <clown> [40]https://www.w3.org/WAI/ARIA/track/actions/980

     [40] https://www.w3.org/WAI/ARIA/track/actions/980

   JS: David updated the action title.
   ... In 2015.
   ... I'll touch base with David as he may want to hand this one
   off to Alex.
   ... Unless you want to take it over from here.

   CS: I probably can.

   JS: I'll assign action-980 to you then.

   CS: Set both due dates to two weeks from now.

   JS: May 3rd. Done.

Summary of Action Items

Summary of Resolutions

   [End of minutes]

Received on Tuesday, 19 April 2016 20:05:48 UTC