15:40:52 RRSAgent has joined #apa 15:40:52 logging to http://www.w3.org/2017/05/17-apa-irc 15:40:54 RRSAgent, make logs world 15:40:54 Zakim has joined #apa 15:40:56 Zakim, this will be 15:40:56 I don't understand 'this will be', trackbot 15:40:57 Meeting: Accessible Platform Architectures Working Group Teleconference 15:40:57 Date: 17 May 2017 15:40:58 agenda? 15:41:03 agenda+ preview agenda with items from two minutes 15:41:03 agenda+ TPAC 2017 https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2017 15:41:03 agenda+ Push API CfC 15:41:03 agenda+ Task Force Checkins 15:41:04 agenda+ Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/products/8 15:41:06 agenda+ new on TR http://www.w3.org/TR/tr-status-drafts.html 15:41:08 agenda+ Other Business 15:41:11 agenda+ next and future meetings 15:41:13 agenda+ be done 15:50:49 15:50:57 present+ 15:51:01 Chair: Janina 15:51:10 regrets: Michiel, Leonie 15:57:52 tzviya has joined #apa 16:00:59 present+ Joanmarie_Diggs 16:02:07 present+ tzviya 16:05:25 present+ 16:05:50 Gottfried has joined #apa 16:06:10 scribe: Gottfried 16:06:13 zakim, next item 16:06:13 agendum 1. "preview agenda with items from two minutes" taken up [from janina] 16:07:00 Janina: any news? 16:07:03 (nobody) 16:07:07 zakim, close this item 16:07:07 agendum 1 closed 16:07:08 I see 8 items remaining on the agenda; the next one is 16:07:08 2. TPAC 2017 https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2017 [from janina] 16:07:14 zakim, open next item 16:07:14 agendum 2. "TPAC 2017 https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2017" taken up [from janina] 16:07:40 Janina: Draft agenda may be available in June. But make a hotel reservation now. 16:08:42 Janina: We don't know how to get the W3C rate for the hotel. 16:09:11 Janina: Will keep checking. 16:09:16 zakim, next item 16:09:16 agendum 3. "Push API CfC" taken up [from janina] 16:09:54 Janina: I have drafted comments. Case: you don't want to be interrupted. I got no comments. 16:10:41 ... I would like to reference Ted's Github issue. More generic use case. We need ways to tell to not push. 16:10:54 ... I will put out a CfC for a formal decision of the group. 16:11:11 zakim, next item 16:11:11 agendum 4. "Task Force Checkins" taken up [from janina] 16:12:02 Michael: Cleaning up Coga publications. Talked with ARIA chairs on Monday. 16:12:41 ... Trying to publish 3 COGA docs together. Focus on the REC-doc, i.e. ARIA doc. 16:12:59 ... My highest prio is on the cog support for WCAG. 16:13:40 Janina: No general problem with prioritization. But COGA needs to deliver its docs as in the charter. Should not stall them. 16:14:39 ... We need to have these docs published and reviewed 16:14:54 Michael: Docs are very long - can we expect them to be thoroughly reviewed? 16:15:21 Janina: Maybe publish gap analysis - without issues paper? 16:15:34 ... There might be other organizations interested in this. 16:15:55 Michael: Gap analysis is the most useful one. References the issue paper. 16:16:23 ... We could publish as group note. 16:16:49 q+ 16:17:20 s/group note/working draft 16:17:41 ... Danger of publishing a working draft as a note. 16:17:52 ... But publishing a working draft without a note is a bad idea. 16:18:01 ack t 16:19:06 Tzviya: Only a few people know about this work. You might get interested from DC and other accessibility organization that are focused on publishing. 16:19:36 ... What about the CSS task force? - Issue with personalization semantics. 16:20:00 ... Overwriting the layout with CSS semantics could cause problems. 16:20:48 Janina: I have prepared a set of invitations to this call next week. On the topic of mechanisms for personalization on the Web. 16:21:02 ... CSS, Media query, etc. 16:21:37 ... I am going to send out some emails. 16:21:56 Tzviya: I can join. Can pass it on to others. 16:22:04 Gottfried: Possible for me to join. 16:22:49 Janina: What can we do with our 12-year old CAPTCHA paper? - Not ready yet. 16:23:23 ... CSS task force had problems getting off the ground. May need some support to get started. 16:23:32 s/support/nudge 16:23:35 zakim, next item 16:23:35 agendum 5. "Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/products/8" taken up [from janina] 16:23:45 action-2131 16:23:45 action-2131 -- Michael Cooper to Ask webappsec if csp is meant to block bookmarklets, and raise issue of a11y scripts that users explicitly request (not xss) -- due 2017-05-17 -- OPEN 16:23:45 http://www.w3.org/WAI/APA/track/actions/2131 16:24:06 action-2129? 16:24:06 action-2129 -- Michael Cooper to Find publications that went straight to note without review opportunity -- due 2017-05-10 -- OPEN 16:24:06 http://www.w3.org/WAI/APA/track/actions/2129 16:24:32 Michael: 54% of notes last year were published without a review draft. 16:24:41 ... Will send this in an email to the wg. 16:25:40 ... There are some process changes needed. 16:26:29 action-2124? 16:26:29 action-2124 -- Janina Sajka to Follow up with johannes wilm on input events 1 and 2 wrt our comments on input events non-leveled -- due 2017-05-17 -- OPEN 16:26:29 http://www.w3.org/WAI/APA/track/actions/2124 16:26:46 Janina: I am still waiting for Leonie 16:26:48 action-2119? 16:26:48 action-2119 -- Janina Sajka to Review html 5.2 https://www.w3.org/tr/html52/ -- due 2017-05-17 -- OPEN 16:26:48 http://www.w3.org/WAI/APA/track/actions/2119 16:27:23 close action-2119 16:27:23 Closed action-2119. 16:27:24 Janina: Found no problem. Let's close it. 16:28:25 Tzviya: Issue on ARIA details tag was closed by Charles. Should be fine now. 16:29:05 zakim, next item 16:29:05 agendum 6. "new on TR http://www.w3.org/TR/tr-status-drafts.html" taken up [from janina] 16:29:28 -> https://www.w3.org/TR/motion-sensors/ Motion Sensors Explainer 16:30:13 Michael: We sometimes have a11y input on use cases. Do we want to deal with this? 16:30:34 Janina: Probably not - unless somebody has a particular use case. 16:30:56 Michael: (reading from the use case section) 16:31:33 Janina: No need to review 16:32:01 -> https://www.w3.org/TR/orientation-sensor/ Orientation Sensor 16:33:02 Michael: Guessing this is low-level, but nothing on the API level. 16:33:12 Janina: Yes, there could be a11y use cases. 16:34:15 Gottfried: This doc refers to the motion sensors explainer doc. 16:34:42 Michael: Cannot tell how comprehensive this API is. But guessing we probably care more about API uses than the API itself. 16:35:10 ... We need to come up with a white paper about web of things, device API, sensors etc. 16:35:23 Janina: We need to complain about API specs not explaining themselves. 16:35:38 Michael: Haven't made a formal complaint, only discussed this 16:35:40 action: cooper to make a fuss about algorithmic specs 16:35:41 Created ACTION-2132 - Make a fuss about algorithmic specs [on Michael Cooper - due 2017-05-24]. 16:35:44 Janina: Need to come back to this. 16:36:11 ... Need to pick up conversation with Ralf. Other groups are impacted too. 16:36:47 ... For us it is not only the problem of not being able to do an a11y review, but also resulting in badly written specs. 16:37:30 Michael: We have 23 specs that are marked "in active review". 16:37:42 ... 19 have a review assigned. 16:37:52 Janina: We should get back to this in early June. 16:38:16 zakim, next item 16:38:16 agendum 7. "Other Business" taken up [from janina] 16:39:05 Michael: I was reading on content security policy - looking for a11y issues - could not find out in the spec. Talked with Ralf. 16:39:27 ... Ralf said that we have to live with the preferred language style of the editor. No resources to train editors or add additional editors. 16:39:57 ... I believe we can still address this by drafting best practices to make editors aware of common problems. 16:40:17 ... This will be an ongoing conversation with Ralf and the architecture team. 16:40:29 Janina: Involve others? Internationalization? 16:41:03 Michael: Presentation of i18n on how to review specs. They have similar processes, but different tools. 16:41:15 ... I will discuss with them. 16:41:39 Janina: Best practices policy manual should address this. 16:41:51 Michael: Not a simple path. 16:42:24 Janina: There is a wider community that wants to look at an API and understand before diving into. 16:42:49 ... Should be a topic at the next TPAC on Wed. 16:43:07 Michael: We should gather other interested parties before TPAC. 16:43:56 Janina: Next call on architectural directions on achieving meaningful personalization. Folks from the wider APA community are invited. 16:44:13 ... I will send out the invitation. 16:44:48 zakim, bye 16:44:48 leaving. As of this point the attendees have been janina, Joanmarie_Diggs, tzviya, MichaelC 16:44:48 Zakim has left #apa 16:44:54 rrsagent, make log public 16:44:59 rrsagent, draft minutes 16:44:59 I have made the request to generate http://www.w3.org/2017/05/17-apa-minutes.html Gottfried 16:55:55 tzviya has joined #apa