[AAPI] Minutes UAI TF Meeting, Tuesday 2 August 2016

URL: https://www.w3.org/2016/08/02-aapi-minutes.html

Plain text follows:

   [1]W3C

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

   Accessible Rich Internet Applications Working Group Teleconference

02 Aug 2016

   See also: [2]IRC log

      [2] http://www.w3.org/2016/08/02-aapi-irc

Attendees

   Present
          JemmaJaeunKu, Joseph_Scheuhammer, Joanmarie_Diggs,
          Bryan_Garaventa, Cynthia_Shelly

   Regrets
          Richard_Schwerdtfeger

   Chair
          Joseph_Scheuhammer.

   Scribe
          joanie

Contents

     * [3]Topics
         1. [4]ACTION-2102: (Rich) Create mappings based on
            features in html 5.1 spec.
         2. [5]Managed States
         3. [6]ISSUE-676/ACTION-2083: (Joseph) Review ATK/AT-SPI
            states for aria states and properties.
         4. [7]ISSUE-645: (All) remove 'checkable' object
            attribute requirement from aria-pressed mapping
            requirements.
         5. [8]ISSUE-663: (Rich) Presentational children of some
            widgets have doclick actions if make presentational
            who handles the click
         6. [9]ISSUE-627: (All) Conflict between aria-autocomplete
            and HTML5.2 autocomplete.
         7. [10]Triage issues/actions:
            https://www.w3.org/WAI/ARIA/track/products/23
         8. [11]ISSUE-627: (All) Conflict between
            aria-autocomplete and HTML5.2 autocomplete.
         9. [12]Triage issues/actions:
            https://www.w3.org/WAI/ARIA/track/products/23
     * [13]Summary of Action Items
     * [14]Summary of Resolutions
     __________________________________________________________

   <clown> agenda: this

   <scribe> scribe: joanie

ACTION-2102: (Rich) Create mappings based on features in html 5.1
spec.

   <clown> action-2102

   <trackbot> action-2102 -- Richard Schwerdtfeger to Create
   mappings based on features in html 5.1 spec. -- due 2016-08-04
   -- OPEN

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

     [15] http://www.w3.org/WAI/ARIA/track/actions/2102

   JS: Rich took on an action last week.

   <clown> issue-1038

   <trackbot> issue-1038 -- Need mappings for role="feed" for all
   AAPIs -- open

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

     [16] http://www.w3.org/WAI/ARIA/track/issues/1038

   JS: Last Thursday, I did a gap analysis between the ARIA spec
   and the mapping spec.

   <clown> issue-1039

   <trackbot> issue-1039 -- Need mapping for role="figure" for all
   AAPIs -- open

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

     [17] http://www.w3.org/WAI/ARIA/track/issues/1039

   <clown> issue-1040

   <trackbot> issue-1040 -- Need mappings for role="term" for all
   AAPIs -- open

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

     [18] http://www.w3.org/WAI/ARIA/track/issues/1040

   JS: I found three roles (feed, figure, and term) which need
   mappings on all platforms.

   <clown> issue-1041

   <trackbot> issue-1041 -- Need mappings of aria-colcount,
   aria-colindex, aria-colspan, aria-rowcount, aria-rowindex, and
   aria-rowspan for all AAPIs -- open

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

     [19] http://www.w3.org/WAI/ARIA/track/issues/1041

   JS: There's also a bunch of table-oriented properties which
   need mappings.

   <clown> issue-1042

   <trackbot> issue-1042 -- Need mappings for aria-details for all
   AAPIs -- open

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

     [20] http://www.w3.org/WAI/ARIA/track/issues/1042

   JS: And there's also ARIA details.
   ... I've created issues for all these things.
   ... Rich said that some of these are are probably covered in
   HTML 5.1.
   ... I think that's the case for many, but not for aria-details.
   ... Is it enough that I've told you that we need mappings? Or
   do I need to create actions for everyone.

   CS: I'm more likely to do it if there is an action.

   JD: Should we look to see what is already covered by HTML 5.1?

   <clown> action-2102

   <trackbot> action-2102 -- Richard Schwerdtfeger to Create
   mappings based on features in html 5.1 spec. -- due 2016-08-04
   -- OPEN

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

     [21] http://www.w3.org/WAI/ARIA/track/actions/2102

   JS: When Rich goes to do this, and finds something he cannot
   do, we can then create actions for just those.
   ... How does that sound?

   CS: We could do that, though this week would be better for me.

   JS: One action for all of it?

   CS: That's fine.

   <clown> ACTION: Cynthia to provide UIA mappings for roles feed,
   figure, and term; and aria-colcount, aria-colspan,
   aria-colindex, aria-rowcount, aria-rowindex, aria-rowspan, and
   aria-details. [recorded in
   [22]http://www.w3.org/2016/08/02-aapi-minutes.html#action01]

     [22] http://www.w3.org/2016/08/02-aapi-minutes.html#action01]

   <trackbot> Created ACTION-2103 - Provide uia mappings for roles
   feed, figure, and term; and aria-colcount, aria-colspan,
   aria-colindex, aria-rowcount, aria-rowindex, aria-rowspan, and
   aria-details. [on Cynthia Shelly - due 2016-08-09].

   <clown> action-2103

   <trackbot> action-2103 -- Cynthia Shelly to Provide uia
   mappings for roles feed, figure, and term; and aria-colcount,
   aria-colspan, aria-colindex, aria-rowcount, aria-rowindex,
   aria-rowspan, and aria-details. -- due 2016-08-09 -- OPEN

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

     [23] http://www.w3.org/WAI/ARIA/track/actions/2103

   issue-980

   <trackbot> Sorry, but issue-980 does not exist.

   action-980

   <trackbot> action-980 -- Cynthia Shelly to Describe/define
   managed aria related states: aria-setsize, aria-posinset,
   aria-level, focused, focusable with reference to section 5.5
   bullet 1 of the UAIG. -- due 2016-07-19 -- OPEN

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

     [24] http://www.w3.org/WAI/ARIA/track/actions/980

   JS: I've created action-2103.
   ... There's a note in there that lists all the items.
   ... Is that sufficient?

   CS: That's fine.

   <clown> issue-706

   <trackbot> issue-706 -- Describe/define AAPI managed states --
   open

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

     [25] http://www.w3.org/WAI/ARIA/track/issues/706

Managed States

   CS: I don't know if we can do anything on this topic without
   Rich.
   ... I even found documentation on the various platforms and
   still don't know the answer.

   JS: I will put this on the agenda.
   ... This is action-980
   ... This was open initially in 2014.
   ... No. 2012.

ISSUE-676/ACTION-2083: (Joseph) Review ATK/AT-SPI states for aria
states and properties.

   <clown> action-2083?

   <trackbot> action-2083 -- Joseph Scheuhammer to Review and
   update ATK/AT-SPI2 states in Core AAM -- due 2016-06-21 -- OPEN

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

     [26] http://www.w3.org/WAI/ARIA/track/actions/2083

   JS: There's an issue that Jason Kiss brought up a while ago.
   ... Last week, Joanie pointed out a note she'd written in the
   action as to what the different states were.
   ... But she was confused as to where it belonged.
   ... I responded the states and properties table.
   ... So I went through that table and compared what was there to
   what Joanie said.
   ... Most of the time they did.
   ... In some cases, the existing table was more thorough.
   ... I created a note on the action for Joanie to review.

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

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

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

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

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

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

   JS + JD: (Looks over table and proposed mappings and needs work
   comments and discusses)

   JS: Readonly is now cleared up.
   ... I think I need to do something with aria-hidden still.
   ... aria-hidden="true" says don't expose; aria-hidden="false"
   says not mapped.

   JD: That will have to change.

   JS: Some of the ATK states for the true/false, it says "set the
   state"/"clear the state".
   ... But on others, it says "not mapped".
   ... I would prefer it say "clear the state."

   JD: Example?

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

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

   JS: aria-haspopup

   JD: Actually in that case, I think "not mapped" is correct
   because clearing the state implies state-changed events; not a
   simple lack of exposure.

   JS: Could you go through these, then?

   JD: Reassign it back to me please. With a comment.

   JS: Done.

ISSUE-645: (All) remove 'checkable' object attribute requirement from
aria-pressed mapping requirements.

   <clown> issue-645?

   <trackbot> issue-645 -- remove 'checkable' object attribute
   requirement from aria-pressed mapping requirements -- open

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

     [31] http://www.w3.org/WAI/ARIA/track/issues/645

   JS: I think this is one I did a long time ago.
   ... It's a request from Alex to remove "checkable" object
   attribute from aria-pressed.
   ... It used to be the case that checkable was also supposed to
   be exposed.

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

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

   JS: I've removed the exposure and would like to close this
   issue.

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

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

   JS: The above URL is for aria-pressed="true". And there's no
   mention of "checkable" any longer.

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

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

   <jemmaKu> no objection

   <jemmaKu> for removing 'checkable' object

   JS: All I have done is remove the object attribute.
   ... The mappings are otherwise unchanged.

   JD: Fine with me.

   JS: Closed!

ISSUE-663: (Rich) Presentational children of some widgets have
doclick actions if make presentational who handles the click

   JS: Rich is not here.

   <clown> issue-663?

   <trackbot> issue-663 -- Presentational children of some widgets
   have doclick actions if make presentational who handles the
   click -- open

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

     [35] http://www.w3.org/WAI/ARIA/track/issues/663

   JS: He opened this issue back in 2014.
   ... I think he handled this as part of his changes related to
   presentaional overrides.
   ... But I'd like to check with Rich to be sure.

ISSUE-627: (All) Conflict between aria-autocomplete and HTML5.2
autocomplete.

   <clown> issue-627?

   <trackbot> issue-627 -- Conflict between aria-autocomplete and
   HTML5 autocomplete. -- open

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

     [36] http://www.w3.org/WAI/ARIA/track/issues/627

   JS: This is a tough one.
   ... To explain.
   ... HTML 5 introduced an autocomplete attribute which is on by
   default for inputs of type text

   <clown> <input type="text" …>

   JS: The above gets autocomplete="true".
   ... Which is exposed as state supports-autocomplete.

   <clown> <input type="text" role="spinbutton">

   CS: The values are supplied by the browser.

   JS: Correct.

   <clown> <input type="text" role="spinbutton"
   autocomplete="off">

   JS: But in the case of spinbutton, which doesn't functionally
   have an autocomplete, the mappings expose supports
   autocomplete.

   CS: The above, I think, will still have an autocomplete from
   the browser.
   ... And you'd have to do other work to make the above example
   work without an autocomplete.

   <clown>
   [37]http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/te
   sts/form/test_Spinner.html

     [37]
http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/form/test_Spinner.html

   JS: Dojo used to do something like the above because at that
   time we didn't have the "number" input type.
   ... The test page is above.
   ... It's type="text" still.
   ... But they also have autocomplete="off".

   CS: Having the autocomplete in this particular case is not that
   weird.

   <clown> <input type='text' role='combobox'
   aria-autocomplete='none' ...>.

   JS: Back to the issue....
   ... If you do the above (with combo box), you'll get
   supports-autocomplete exposed.

   CS: Again, the browser autocompleting is going to work.

   <clown> <input type='text' role='combobox'
   aria-autocomplete='none' autocomplete="off">.

   JS: If you set it to none?
   ... Does that mean you need to set both the ARIA property and
   the HTML property?

   CS: They are two different things.

   JS + CS: This is an authoring-practices issue; not mapping
   issue.

   Jemma: We made a combobox example in the APG.
   ... But I don't recall what was done.

   JS: Bryan, how do you feel about this?

   CS: I don't think there's a conflict; just naming confusion.

   BG: We have several examples (one that matches ARIA 1.0 and one
   that matches ARIA 1.1).
   ... So we can do this in the APG.

   JS: I'm going to retitle it to reflect naming confusion and
   re-assign it to APG.

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

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

ISSUE-627: (All) Conflict between aria-autocomplete and HTML5.2
autocomplete.

   Jemma: The above URL has Jon's example.

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

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

   CS: It's actually time.

   JS: True. Let's close the meeting.

Summary of Action Items

   [NEW] ACTION: Cynthia to provide UIA mappings for roles feed,
   figure, and term; and aria-colcount, aria-colspan,
   aria-colindex, aria-rowcount, aria-rowindex, aria-rowspan, and
   aria-details. [recorded in
   [40]http://www.w3.org/2016/08/02-aapi-minutes.html#action01]

     [40] http://www.w3.org/2016/08/02-aapi-minutes.html#action01

Summary of Resolutions

   [End of minutes]

Received on Tuesday, 2 August 2016 20:06:24 UTC