15:38:56 RRSAgent has joined #apa 15:38:56 logging to http://www.w3.org/2017/05/10-apa-irc 15:38:58 RRSAgent, make logs world 15:38:58 Zakim has joined #apa 15:39:00 Zakim, this will be 15:39:00 I don't understand 'this will be', trackbot 15:39:01 Meeting: Accessible Platform Architectures Working Group Teleconference 15:39:01 Date: 10 May 2017 15:39:07 agenda? 15:39:12 agenda+ TPAC 2017 https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2017 15:39:12 agenda+ Task Force Checkins 15:39:12 agenda+ Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/products/8 15:39:12 agenda+ new on TR http://www.w3.org/TR/tr-status-drafts.html 15:39:13 agenda+ Other Business 15:39:14 agenda+ next and future meetings 15:39:17 agenda+ be done 15:39:22 agenda? 15:39:31 zakim, clear agenda 15:39:31 agenda cleared 15:40:40 agenda+ preview agenda with items from two minutes 15:40:40 agenda+ TPAC 2017 https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2017 15:40:40 agenda+ Task Force Checkins 15:40:40 agenda+ Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/products/8 15:40:41 agenda+ new on TR http://www.w3.org/TR/tr-status-drafts.html 15:40:42 agenda+ Other Business 15:40:45 agenda+ next and future meetings 15:40:47 agenda+ be done 15:55:09 present+ 15:55:14 Chair: Janina 16:00:40 present+ Joanmarie_Diggs 16:02:23 agenda: https://lists.w3.org/Archives/Public/public-apa/2017May/0031.html 16:03:58 tdrake has joined #apa 16:04:06 present+ tdrake 16:05:40 zakim, next item 16:05:40 agendum 1. "preview agenda with items from two minutes" taken up [from janina] 16:06:31 janina: The agenda will focus on some passed-on items that need attention. 16:06:58 zakim, next item 16:06:58 agendum 2. "TPAC 2017 https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2017" taken up [from janina] 16:07:28 Reminder to book hotel. Have they updated the web page? 16:07:41 MichaelC: It has not yet been updated. 16:08:01 Janina: Next year's TPAC is in Lyon, France. 16:08:09 It's a nice facility. 16:08:35 tdrake: This year's TPAC, is it in San Francisco area? 16:08:42 janina: Yes, it is in Burlingame. 16:09:31 JF has joined #apa 16:10:01 agenda? 16:10:13 Any questions for TPAC? We need to develop an agenda and decide what groups to meet with. 16:10:29 Michael: ARIA, payments, automotive, authentication... 16:10:52 JF: Add cloud browser folks. It's a task force that came out of the web and tv interest group. 16:11:06 ARIA 16:11:06 Automotive 16:11:06 CSS 16:11:06 Internet of Things 16:11:06 Payments 16:11:07 Web Platform 16:11:09 Web Authentication 16:11:14 MichaelC: they changed names to something with entertainment. 16:12:06 JohnF: Web and tv - cloud browser TF 16:12:35 zakim, next item 16:12:35 agendum 3. "Task Force Checkins" taken up [from janina] 16:12:37 MichaelC: Media and Entertainment 16:12:49 Janina: we want to meet with them to implement the MAUR 16:13:09 COGA Status update? 16:13:25 MichaelC: bogged down and targeting next tuesday for publication 16:14:08 -> https://www.w3.org/community/payments-commerce-a11y/ Web Payments and Commerce Accessibility Community Group 16:14:24 SysReq = The community group was blocked and now it can be joined and go to work. 16:15:09 Janina, tdrake, and MichaelC are likely to join. 16:17:19 tdrake: CSS updates. Michael did the initial set up. The community jumped in and started commenting and a few issues are ready to close. I need to get feedback from MichaelC on closing process. 16:17:37 Janina: Report on CAPTCHA should be coming soon. 16:18:29 An upcoming call will focus on personalization. There's an ARIA module, a manifest, ... Let's use May 24 to focus on this conversation. 16:18:55 I'm looking for a list of people to invite for this meeting. 16:19:01 zakim, next item 16:19:01 agendum 4. "Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/products/8" taken up [from janina] 16:19:41 michaelC: I have a task to find specs that went forward without comments. Leave this open. 16:20:53 JF: I am looking at this. one point of interest: This document has an addendum: Algorithm for retrieving bundled collections of documents. I want to go through this in more detail. I'm about 80% done. There's some meat here and I need another week. 16:20:54 action-2128 due 1 week 16:20:54 Set action-2128 Review web publications for the open web platform: vision and technical challenges https://www.w3.org/tr/pwp/ due date to 2017-05-17. 16:21:01 close action-2127 16:21:01 Closed action-2127. 16:21:02 MichaelC: Janina to also review. 16:21:31 action-2124 due 1 week 16:21:31 Set action-2124 Follow up with johannes wilm on input events 1 and 2 wrt our comments on input events non-leveled due date to 2017-05-17. 16:21:33 Janina: waiting for Leonie on events action 16:21:38 action-2124: need LĂ©onie in call 16:21:38 Notes added to action-2124 Follow up with johannes wilm on input events 1 and 2 wrt our comments on input events non-leveled. 16:22:04 action-2119 due 1 week 16:22:04 Set action-2119 Review html 5.2 https://www.w3.org/tr/html52/ due date to 2017-05-17. 16:22:15 I need another week to finish review of HTML 5.2 16:22:36 action-2116 due 1 week 16:22:36 Set action-2116 Review ttml profiles for internet media subtitles and captions 1.0.1 (imsc1) https://www.w3.org/tr/ttml-imsc1.0.1/ due date to 2017-05-17. 16:22:44 JF: another week for action on TTML Profiles 16:23:12 action-2112: https://lists.w3.org/Archives/Public/public-apa/2017May/0033.html 16:23:12 Notes added to action-2112 Re-review push api https://w3c.github.io/push-api/. 16:23:15 Janina: Push API has a draft comment. We'd like to tweak on it and get group consensus. 16:23:41 We'd like to push Ted's issue to a group consensus for push events. 16:24:11 We could then push them as APA comments instead of individual user comments. 16:25:18 David, one of the web payment chairs, wants the push events to enable user preference for defining timing. This is good for all people, not just those with disabilities. 16:25:28 This action could be closed. 16:25:53 close action-2112 16:25:53 Closed action-2112. 16:26:14 Ted's comment: https://github.com/w3c/push-api/issues/257 16:26:58 MichaelC: Ted to take over CSS transitions. This can be closed as the issue has been created within GitHub and ready for follow up. 16:27:19 close action-2011 16:27:19 Closed action-2011. 16:27:34 zakim, next item 16:27:34 agendum 5. "new on TR http://www.w3.org/TR/tr-status-drafts.html" taken up [from janina] 16:27:56 New Publications: 6 new ones: CSS Grid Layout module 1 16:28:30 HTML Media Capture 16:28:41 -> https://www.w3.org/TR/html-media-capture/ HTML Media Capture 16:29:05 it defines a form action to utilize camera. 16:29:56 JF: i have a vague recollection of us looking at this. It doesn't have much UI. It exposes the camera to scripted abilities in a web page. 16:30:17 Janina: my concern is that you may have multiple cameras and devices. 16:30:35 JF: it simply exposes an API to script the camera on a mobile device. 16:30:56 you would be given a user interface to manipulate the camera, but this is just an api to script the camera 16:31:09 janina: there's another api for user interface capture and manipulation. 16:31:26 michaelC: closing this. it is specific to smart phone camera. No need to review. 16:31:36 -> https://www.w3.org/TR/microdata/ HTML Microdata 16:31:37 HTML MicroData. This is a new spec. 16:32:04 This avoids the problems from MicroFormats and is similar to RDFa. 16:32:57 JF: this was proposed after Yandex and other groups began using it. It's needs to be updated to keep it fresh. 16:33:58 There are no concerns and the editor, Chaarls, would keep an eye on any accessibility concerns. It requires a taxonomy. There may be some interactivity with taxonomy terms and manifest. 16:34:40 MichaelC: It doesn't give information on using a shared vocabulary. 16:34:52 No need to review 16:35:04 Overview of coverage JSON format 16:35:08 -> https://www.w3.org/TR/covjson-overview/ Overview of the CoverageJSON format 16:36:14 joint publication with OGC. Open Geospatial ... coverage JSON is something open geospatial does and this is a coverage document. I don't know if we need to review this. 16:36:23 janina: Give it to me. 16:36:48 JF: there's going to be some extension points. There is a relationship with wayfinding applications. This seems to be more of a backend thing. 16:36:49 action: Janina to review Overview of the CoverageJSON format https://www.w3.org/TR/covjson-overview/ 16:36:50 Created ACTION-2130 - Review overview of the coveragejson format https://www.w3.org/tr/covjson-overview/ [on Janina Sajka - due 2017-05-17]. 16:37:09 Michaelc: Does it give examples for future uses that we should have input. 16:37:17 JF: should we meet with them in Burlingame. 16:37:27 action-2130? 16:37:27 action-2130 -- Janina Sajka to Review overview of the coveragejson format https://www.w3.org/tr/covjson-overview/ -- due 2017-05-17 -- OPEN 16:37:27 http://www.w3.org/WAI/APA/track/actions/2130 16:37:45 MichaelC: we already have a full schedule, this shouldn't be needed. 16:37:48 action-2130: https://www.w3.org/WAI/APA/wiki/Overview_of_the_CoverageJSON_format 16:37:48 Notes added to action-2130 Review overview of the coveragejson format https://www.w3.org/tr/covjson-overview/. 16:37:56 action-2130 due 6 weeks 16:37:56 Set action-2130 Review overview of the coveragejson format https://www.w3.org/tr/covjson-overview/ due date to 2017-06-21. 16:38:06 janina: give me until end of june to review the document. 16:38:40 Push API: we've talked about this already. 16:39:31 -> https://www.w3.org/TR/webauthn/ Web Authentication: An API for accessing Public Key Credentials 16:39:33 michaelC: Web Authentication for accessing Public Key credentials. 16:39:46 They must have changed names. 16:40:34 They changed the name from "Web Api" to "an API", which makes it difficult to research. 16:42:10 It should have hit our wiki in February. The latest spec on scoped credentials is open. This is an API for a web application to request a public/private key and the browser to store the keys. 16:42:47 The spec doesn't define the user interface, but there needs to be something from the browser. Do we define this or should it default to UAG specification? 16:42:56 Janina: I'm inclined to let it go. 16:43:08 zakim, next item 16:43:08 agendum 6. "Other Business" taken up [from janina] 16:43:30 Other business: Content Security 16:43:31 agenda? 16:44:02 -> https://www.w3.org/WAI/APA/wiki/Content_Security_Policy_Level_3 Content Security Policy 16:44:04 we have several specs we passed on, there are several dealing with security. We've discovered we shouldn't have passed on them. Michael to explain bookmarklets 16:45:09 michaelC: someone mentioned their need to add headings to github comments. I created a bookmarklet, but it didn't work on github.com. Investigating this, the content security policy will block non white-listed scripts. 16:45:48 the content security shouldn't block bookmarklets as a user script, but the spec is very difficult to read. 16:46:19 JF: api-specs: can we elevate this topic at TPAC. 16:46:53 Janina: we need to talk about this on Wednesday. We need to hold them to a higher level than writing algorithms 16:47:40 JF: could we get 15-20 minutes? 16:48:05 Janina: this hampers our ability to do our job as well as those that are writing the spec if they can't say in plain english what this spec does. 16:49:05 MichaelC: I put this down on our agenda. Last year we proposed a break-out session. Perhaps we could do this for the event. 16:50:07 I am scheduled to talk with Ralph and we could discuss this. 16:52:01 Ted: The HTML Codesniffer bookmarklet is commonly blocked within https pages. I didn't think of this as the cause. I thought it was something in our javascript that was blocking the bookmarklet. 16:52:59 MichaelC: we need to see what defines whitelisted groups. 16:53:41 rrsagent, make minutes 16:53:41 I have made the request to generate http://www.w3.org/2017/05/10-apa-minutes.html MichaelC 16:53:51 JF: Cognitive and learning abilities group has also been investigating scripting to affect pages. 16:54:08 tdrake: JAWS 17 introduced domain specific scripting for web pages. 16:54:31 janina: create an action and ask for information. 16:55:06 michaelC: janina reviewed it a year ago, mentioned scripts, and assigned it to Shane. It was closed, but we weren't sure why it was closed. I can take this to understand intent. 16:55:38 janina: this may not be an accessibility-specific concern, but it is something that affects us. 16:56:05 action: cooper to ask WebAppSec if CSP is meant to block bookmarklets, and raise issue of a11y scripts that users explicitly request (not XSS) 16:56:07 Created ACTION-2131 - Ask webappsec if csp is meant to block bookmarklets, and raise issue of a11y scripts that users explicitly request (not xss) [on Michael Cooper - due 2017-05-17]. 16:57:16 zakim, next item 16:57:16 agendum 7. "next and future meetings" taken up [from janina] 16:58:34 zakim, bye 16:58:34 leaving. As of this point the attendees have been janina, Joanmarie_Diggs, tdrake 16:58:34 Zakim has left #apa 16:58:43 rrs, make minutes 16:59:00 rrsagent, make minutes 16:59:00 I have made the request to generate http://www.w3.org/2017/05/10-apa-minutes.html tdrake 16:59:22 rrsagent, bye 16:59:22 I see 2 open action items saved in http://www.w3.org/2017/05/10-apa-actions.rdf : 16:59:22 ACTION: Janina to review Overview of the CoverageJSON format https://www.w3.org/TR/covjson-overview/ [1] 16:59:22 recorded in http://www.w3.org/2017/05/10-apa-irc#T16-36-49 16:59:22 ACTION: cooper to ask WebAppSec if CSP is meant to block bookmarklets, and raise issue of a11y scripts that users explicitly request (not XSS) [2] 16:59:22 recorded in http://www.w3.org/2017/05/10-apa-irc#T16-56-05