18:48:17 RRSAgent has joined #aapi 18:48:17 logging to http://www.w3.org/2016/08/02-aapi-irc 18:48:19 RRSAgent, make logs world 18:48:19 Zakim has joined #aapi 18:48:21 Zakim, this will be 18:48:21 I don't understand 'this will be', trackbot 18:48:22 Meeting: Accessible Rich Internet Applications Working Group Teleconference 18:48:22 Date: 02 August 2016 18:48:24 jemmaKu has joined #aapi 18:48:46 hi does anyone know pw to webex? 18:49:45 jemmaKu: for this meeting - the AAPI meeting? 18:49:49 yes 18:50:25 it's the same as the Thu aria meeting. I('m reluctant to type it into a channel that is being logged publicly) 18:50:55 that is enough hint. thanks 18:50:59 chair: Josephy_Scheuhammer. 18:51:25 good, jemmaKu. You're welcome. 18:51:48 agenda: this 18:51:57 agenda+ ACTION-2102: (Rich) Create mappings based on features in html 5.1 spec. 18:52:01 present+ JemmaJaeunKu 18:52:07 agenda+ ISSUE-676/ACTION-2083: (Joseph) Review ATK/AT-SPI states for aria states and properties. 18:52:14 agenda+ ISSUE-645: (All) remove 'checkable' object attribute requirement from aria-pressed mapping requirements. 18:52:22 agenda+ ISSUE-663: (Rich) Presentational children of some widgets have doclick actions if make presentational who handles the click 18:52:31 agenda+ ISSUE-627: (All) Conflict between aria-autocomplete and HTML5.2 autocomplete. 18:52:35 agenda+ Triage issues/actions: https://www.w3.org/WAI/ARIA/track/products/23 18:52:42 agenda+ Triage core-aam bugzillas: https://www.w3.org/Bugs/Public/buglist.cgi?component=Core%20AAM&product=ARIA 18:52:48 agenda+ Triage accname-aam bugzillas: https://www.w3.org/Bugs/Public/buglist.cgi?component=AccName%20AAM&product=ARIA 18:52:53 agenda+ Triage accname actions: https://www.w3.org/WAI/PF/Group/track/products/26 18:52:58 agenda+ be done. 18:58:43 clown has changed the topic to: WebEx Access Code 641 707 405 (Next meeting 09-Aug-2016, 20:00 UTC) 19:02:20 present+ Joseph_Scheuhammer 19:05:45 cyns has joined #aapi 19:06:09 scribe: joanie 19:06:15 present+ Joanmarie_Diggs 19:06:19 Zakim, take up item 1 19:06:19 agendum 1. "ACTION-2102: (Rich) Create mappings based on features in html 5.1 spec." taken up [from clown] 19:06:26 action-2102 19:06:26 action-2102 -- Richard Schwerdtfeger to Create mappings based on features in html 5.1 spec. -- due 2016-08-04 -- OPEN 19:06:26 http://www.w3.org/WAI/ARIA/track/actions/2102 19:06:46 JS: Rich took on an action last week. 19:06:56 issue-1038 19:06:56 issue-1038 -- Need mappings for role="feed" for all AAPIs -- open 19:06:56 http://www.w3.org/WAI/ARIA/track/issues/1038 19:07:01 JS: Last Thursday, I did a gap analysis between the ARIA spec and the mapping spec. 19:07:08 issue-1039 19:07:08 issue-1039 -- Need mapping for role="figure" for all AAPIs -- open 19:07:08 http://www.w3.org/WAI/ARIA/track/issues/1039 19:07:16 issue-1040 19:07:16 issue-1040 -- Need mappings for role="term" for all AAPIs -- open 19:07:16 http://www.w3.org/WAI/ARIA/track/issues/1040 19:07:20 JS: I found three roles (feed, figure, and term) which need mappings on all platforms. 19:07:27 issue-1041 19:07:27 issue-1041 -- Need mappings of aria-colcount, aria-colindex, aria-colspan, aria-rowcount, aria-rowindex, and aria-rowspan for all AAPIs -- open 19:07:27 http://www.w3.org/WAI/ARIA/track/issues/1041 19:07:38 JS: There's also a bunch of table-oriented properties which need mappings. 19:07:41 issue-1042 19:07:41 issue-1042 -- Need mappings for aria-details for all AAPIs -- open 19:07:41 http://www.w3.org/WAI/ARIA/track/issues/1042 19:07:45 JS: And there's also ARIA details. 19:07:52 JS: I've created issues for all these things. 19:08:10 JS: Rich said that some of these are are probably covered in HTML 5.1. 19:08:20 JS: I think that's the case for many, but not for aria-details. 19:08:37 JS: Is it enough that I've told you that we need mappings? Or do I need to create actions for everyone. 19:08:44 CS: I'm more likely to do it if there is an action. 19:09:34 JD: Should we look to see what is already covered by HTML 5.1? 19:09:44 action-2102 19:09:44 action-2102 -- Richard Schwerdtfeger to Create mappings based on features in html 5.1 spec. -- due 2016-08-04 -- OPEN 19:09:44 http://www.w3.org/WAI/ARIA/track/actions/2102 19:10:22 JS: When Rich goes to do this, and finds something he cannot do, we can then create actions for just those. 19:10:28 JS: How does that sound? 19:10:39 CS: We could do that, though this week would be better for me. 19:10:50 JS: One action for all of it? 19:10:53 CS: That's fine. 19:11:38 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. 19:11:39 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]. 19:11:49 action-2103 19:11:49 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 19:11:49 http://www.w3.org/WAI/ARIA/track/actions/2103 19:13:51 issue-980 19:13:51 Sorry, but issue-980 does not exist. 19:14:44 action-980 19:14:44 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 19:14:44 http://www.w3.org/WAI/ARIA/track/actions/980 19:15:29 JS: I've created action-2103. 19:15:41 JS: There's a note in there that lists all the items. 19:15:47 JS: Is that sufficient? 19:15:54 CS: That's fine. 19:16:14 issue-706 19:16:14 issue-706 -- Describe/define AAPI managed states -- open 19:16:14 http://www.w3.org/WAI/ARIA/track/issues/706 19:16:29 Topic: Managed States 19:16:43 CS: I don't know if we can do anything on this topic without Rich. 19:16:58 CS: I even found documentation on the various platforms and still don't know the answer. 19:17:04 JS: I will put this on the agenda. 19:17:23 JS: This is action-980 19:17:41 JS: This was open initially in 2014. 19:17:46 JS: No. 2012. 19:17:57 Zakim, next item 19:17:57 agendum 2. "ISSUE-676/ACTION-2083: (Joseph) Review ATK/AT-SPI states for aria states and properties." taken up [from clown] 19:18:05 action-2083? 19:18:05 action-2083 -- Joseph Scheuhammer to Review and update ATK/AT-SPI2 states in Core AAM -- due 2016-06-21 -- OPEN 19:18:05 http://www.w3.org/WAI/ARIA/track/actions/2083 19:18:17 JS: There's an issue that Jason Kiss brought up a while ago. 19:18:38 JS: Last week, Joanie pointed out a note she'd written in the action as to what the different states were. 19:18:49 JS: But she was confused as to where it belonged. 19:18:56 JS: I responded the states and properties table. 19:19:15 JS: So I went through that table and compared what was there to what Joanie said. 19:19:20 JS: Most of the time they did. 19:19:33 JS: In some cases, the existing table was more thorough. 19:19:55 JS: I created a note on the action for Joanie to review. 19:25:05 https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#ariaHiddenTrue 19:25:29 https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#ariaReadonlyTrue 19:25:42 https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#ariaReadonlyFalse 19:30:14 JS + JD: (Looks over table and proposed mappings and needs work comments and discusses) 19:30:29 JS: Readonly is now cleared up. 19:30:47 JS: I think I need to do something with aria-hidden still. 19:32:02 JS: aria-hidden="true" says don't expose; aria-hidden="false" says not mapped. 19:32:08 JD: That will have to change. 19:32:45 JS: Some of the ATK states for the true/false, it says "set the state"/"clear the state". 19:32:53 JS: But on others, it says "not mapped". 19:33:08 JS: I would prefer it say "clear the state." 19:33:21 JD: Example? 19:33:26 https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#ariaHaspopupFalse 19:33:28 JS: aria-haspopup 19:34:20 JD: Actually in that case, I think "not mapped" is correct. 19:34:29 JS: Could you go through these, then? 19:34:57 JD: Reassign it back to me please. With a comment. 19:35:45 s/is correct./is correct because clearing the state implies state-changed events; not a simple lack of exposure./ 19:35:49 JS: Done. 19:35:52 Zakim, next item 19:35:52 agendum 3. "ISSUE-645: (All) remove 'checkable' object attribute requirement from aria-pressed mapping requirements." taken up [from clown] 19:36:20 issue-645? 19:36:20 issue-645 -- remove 'checkable' object attribute requirement from aria-pressed mapping requirements -- open 19:36:20 http://www.w3.org/WAI/ARIA/track/issues/645 19:36:28 JS: I think this is one I did a long time ago. 19:36:51 JS: It's a request from Alex to remove "checkable" object attribute from aria-pressed. 19:37:11 JS: It used to be the case that checkable was also supposed to be exposed. 19:37:28 https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#ariaPressedTrue 19:37:30 JS: I've removed the exposure and would like to close this issue. 19:37:55 https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#ariaPressedFalse 19:37:57 JS: The above URL is for aria-pressed="true". And there's no mention of "checkable" any longer. 19:38:09 https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#ariaPressedMixed 19:38:15 no objection 19:40:21 for removing 'checkable' object 19:40:33 JS: All I have done is remove the object attribute. 19:40:50 JS: The mappings are otherwise unchanged. 19:40:56 JD: Fine with me. 19:41:00 JS: Closed! 19:41:33 Zakim, next item 19:41:33 agendum 4. "ISSUE-663: (Rich) Presentational children of some widgets have doclick actions if make presentational who handles the click" taken up [from clown] 19:41:40 JS: Rich is not here. 19:41:41 issue-663? 19:41:41 issue-663 -- Presentational children of some widgets have doclick actions if make presentational who handles the click -- open 19:41:41 http://www.w3.org/WAI/ARIA/track/issues/663 19:41:50 JS: He opened this issue back in 2014. 19:42:25 JS: I think he handled this as part of his changes related to presentaional overrides. 19:42:32 JS: But I'd like to check with Rich to be sure. 19:42:48 Zakim, next item. 19:42:49 agendum 5. "ISSUE-627: (All) Conflict between aria-autocomplete and HTML5.2 autocomplete." taken up [from clown] 19:42:56 issue-627? 19:42:56 issue-627 -- Conflict between aria-autocomplete and HTML5 autocomplete. -- open 19:42:56 http://www.w3.org/WAI/ARIA/track/issues/627 19:43:07 JS: This is a tough one. 19:43:12 JS: To explain. 19:43:39 JS: HTML 5 introduced an autocomplete attribute which is on by default for inputs of type text 19:43:41 19:44:02 JS: The above gets autocomplete="true". 19:44:20 JS: Which is exposed as state supports-autocomplete. 19:44:23 19:44:38 CS: The values are supplied by the browser. 19:44:41 JS: Correct. 19:45:12 19:45:17 JS: But in the case of spinbutton, which doesn't functionally have an autocomplete, the mappings expose supports autocomplete. 19:46:25 CS: The above, I think, will still have an autocomplete from the browser. 19:46:54 CS: And you'd have to do other work to make the above example work without an autocomplete. 19:47:24 http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/form/test_Spinner.html 19:47:26 JS: Dojo used to do something like the above because at that time we didn't have the "number" input type. 19:47:34 JS: The test page is above. 19:47:42 JS: It's type="text" still. 19:49:27 clown has left #aapi 19:49:37 clown has joined #aapi 19:49:48 JS: But they also have autocomplete="off". 19:50:29 CS: Having the autocomplete in this particular case is not that weird. 19:51:52 . 19:51:52 JS: Back to the issue.... 19:52:23 JS: If you do the above (with combo box), you'll get supports-autocomplete exposed. 19:52:40 CS: Again, the browser autocompleting is going to work. 19:52:43 . 19:52:54 JS: If you set it to none? 19:53:28 JS: Does that mean you need to set both the ARIA property and the HTML property? 19:53:42 CS: They are two different things. 19:54:04 JS + CS: This is an authoring-practices issue; not mapping issue. 19:54:28 Jemma: We made a combobox example in the APG. 19:54:38 Jemma: But I don't recall what was done. 19:54:52 JS: Bryan, how do you feel about this? 19:55:04 CS: I don't think there's a conflict; just naming confusion. 19:55:33 BG: We have several examples (one that matches ARIA 1.0 and one that matches ARIA 1.1). 19:55:42 BG: So we can do this in the APG. 19:56:06 JS: I'm going to retitle it to reflect naming confusion and re-assign it to APG. 19:56:30 Zakim, next item 19:56:30 agendum 6. "Triage issues/actions: https://www.w3.org/WAI/ARIA/track/products/23" taken up [from clown] 19:56:57 Zakim, previous item 19:56:57 I don't understand 'previous item', joanie 19:57:06 Zakim, take up item 5 19:57:06 agendum 5. "ISSUE-627: (All) Conflict between aria-autocomplete and HTML5.2 autocomplete." taken up [from clown] 19:57:23 Jemma: The above URL has Jon's example. 19:57:35 s/Zakim, previous item// 19:57:48 Zakim, next item 19:57:48 agendum 5 was just opened, joanie 19:57:55 Zakim, close this item 19:57:55 agendum 5 closed 19:57:56 I see 5 items remaining on the agenda; the next one is 19:57:56 6. Triage issues/actions: https://www.w3.org/WAI/ARIA/track/products/23 [from clown] 19:57:58 Zakim, next item 19:57:58 agendum 6. "Triage issues/actions: https://www.w3.org/WAI/ARIA/track/products/23" taken up [from clown] 19:58:38 CS: It's actually time. 19:58:46 JS: True. Let's close the meeting. 19:59:41 Zakim, part 19:59:41 leaving. As of this point the attendees have been JemmaJaeunKu, Joseph_Scheuhammer, Joanmarie_Diggs 19:59:41 Zakim has left #aapi 19:59:50 scribeOptions: -final 19:59:55 RRSAgent, stop 20:00:43 present+ Bryan_Garaventa, Cynthia_Shelly 20:00:56 regrets: Richard_Schwerdtfeger 20:01:03 RRSAgent, make minutes 20:01:03 I have made the request to generate http://www.w3.org/2016/08/02-aapi-minutes.html joanie 20:01:54 s/Josephy/Joseph/ 20:02:00 RRSAgent, make minutes 20:02:00 I have made the request to generate http://www.w3.org/2016/08/02-aapi-minutes.html joanie 20:02:20 RRSAgent, stop