15:49:06 RRSAgent has joined #apa 15:49:06 logging to http://www.w3.org/2016/10/26-apa-irc 15:49:08 RRSAgent, make logs world 15:49:08 Zakim has joined #apa 15:49:10 Zakim, this will be 15:49:10 I don't understand 'this will be', trackbot 15:49:11 Meeting: Accessible Platform Architectures Working Group Teleconference 15:49:11 Date: 26 October 2016 15:49:29 agenda? 15:49:34 agenda+ preview agenda with items from two minutes 15:49:34 agenda+ next and future meetings 15:49:34 agenda+ Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/products/8 15:49:34 agenda+ new on TR http://www.w3.org/TR/tr-status-drafts.html 15:49:35 agenda+ APA's Accessibility Checklist [See Below] 15:49:36 agenda+ MAUR Redux--Update, Checklist, TTML Sync, Etc. [See Below] 15:49:39 agenda+ Other Business 15:49:41 agenda+ be done 15:51:41 zakim, next item 15:51:41 agendum 1. "preview agenda with items from two minutes" taken up [from janina] 15:51:49 present+ Janina 15:51:53 Chair: Janina 15:54:42 Rich has joined #apa 15:59:03 present+ Rich-Schwerdtfeger 16:00:20 present+ MichielBijl 16:00:34 present+ 16:02:13 agenda: https://lists.w3.org/Archives/Public/public-apa/2016Oct/0032.html 16:09:57 Ryladog_ has joined #apa 16:10:14 Present+ Katie_Haritos-Shea 16:10:15 scribe: MichielBijl 16:11:13 Topic: agenda review 16:11:27 JS: More discussion on survey form to share with spec writers 16:11:43 …where we would think they there will be accessibility concerns 16:11:58 …output from discussions last couple years 16:12:06 CSS WG (?) has something similar 16:12:24 It’ll stay on the agenda till finished. 16:12:37 Anyone with anything to add? 16:12:37 LJWatson has joined #apa 16:12:39 Any news? 16:13:07 LW: Looks like HTML 5.1 will get directors approval this week and will be published next week. 16:13:28 present+ LJWatson 16:13:34 zakim, take up next item 16:13:34 agendum 2. "next and future meetings" taken up [from janina] 16:13:42 ProposaL: APA will NOT meet on 23 November and 21 & 28 December. 16:13:43 Meetings in 2017 will begin 4 January. 16:14:14 JS: This is standard practice 16:14:22 Would resume on 4th of January 16:14:32 Anyone with have a problem with that calendar? 16:14:45 Okay, hearing none lets move on. 16:14:58 KHS: Yeah, no priblem 16:15:04 s/priblem/problem/ 16:15:13 zakim, take up next item 16:15:13 agendum 3. "Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/products/8" taken up [from janina] 16:15:25 JS: Michael, action! 16:15:34 action 297(?) 16:15:57 MC: was a timeline on it, if you’re busy it’s okay 16:16:07 Ted__ has joined #APA 16:16:08 JS: There is something, want to re-read the whole thing 16:16:22 present+ Ted 16:16:52 action-2097? 16:16:52 action-2097 -- Janina Sajka to Re-review https://www.w3.org/tr/webrtc/ webrtc 1.0: real-time communication between browsers -- due 2016-10-26 -- OPEN 16:16:52 http://www.w3.org/WAI/APA/track/actions/2097 16:17:07 action-2096 16:17:07 action-2096 -- Ted Drake to Check how micropub comments have been disposed -- due 2016-10-26 -- OPEN 16:17:07 http://www.w3.org/WAI/APA/track/actions/2096 16:17:34 MC: Should we leave Ted’s? 16:17:40 He just joined! 16:17:47 TD: Went through the comments 16:17:59 Looked like what we were asking for 16:18:13 Have to see if any action was taking on it 16:18:17 It looks good 16:18:24 Looks reasonable 16:18:29 Wondering what the action is 16:18:33 Not sure what the conflict is 16:18:48 https://github.com/microformats/microformats2-parsing/issues/2#issuecomment-236712535 16:18:51 MC: Would be useful to see if understanding from comment is same as understanding from comment 16:19:15 TD: Kind of the conflict going on is with parsing 16:19:23 Didn’t seem reasonable 16:19:43 *explains use case* 16:19:49 I’m interested in Micro pub 16:19:59 Don’t mind looking through the conte t 16:20:10 MC: Will look at it next week 16:20:26 action-2091? 16:20:26 action-2091 -- Janina Sajka to Review web animations https://www.w3.org/tr/web-animations-1/ -- due 2016-10-26 -- OPEN 16:20:26 http://www.w3.org/WAI/APA/track/actions/2091 16:20:42 MC: We need to recruit *laughs* 16:20:55 Let’s put on planning agenda for next week 16:21:17 action-2090 16:21:17 action-2090 -- Janina Sajka to Review portable web publications use cases and requirements https://www.w3.org/tr/pwp-ucr/ -- due 2016-10-26 -- OPEN 16:21:17 http://www.w3.org/WAI/APA/track/actions/2090 16:21:27 JS: That was nice 16:21:46 It’s a requirements document, it’s very thorough. 16:21:53 Web accessibility is well represented 16:22:00 MC: Will put in Wiki 16:22:06 We can close this action 16:22:12 close action-2090 16:22:12 Closed action-2090. 16:22:20 action-2086 16:22:20 action-2086 -- Richard Schwerdtfeger to Review https://www.w3.org/tr/input-events/ input events -- due 2016-09-28 -- OPEN 16:22:20 http://www.w3.org/WAI/APA/track/actions/2086 16:22:41 RS: Haven’t done that yet 16:22:50 MC: Is there a timeline on this? 16:22:56 No there isn’t a special timeline 16:23:12 RS: I’ll try to do that 16:23:17 action-2081 16:23:17 action-2081 -- Michael Cooper to See if web app manifest comments are dealt with https://www.w3.org/wai/apa/wiki/web_app_manifest -- due 2016-08-17 -- OPEN 16:23:17 http://www.w3.org/WAI/APA/track/actions/2081 16:23:30 MC: Getting more stale 16:23:48 I believe… 16:23:50 I believe… 16:24:18 action-2048 16:24:18 action-2048 -- John Foliot to Review https://www.w3.org/tr/ttml2/ timed text markup language 2 (ttml2) -- due 2016-10-06 -- OPEN 16:24:18 http://www.w3.org/WAI/APA/track/actions/2048 16:24:25 MC: We’ll leave that open 16:24:35 JS: A little longer, but not a lot longer, will need to read that too 16:24:39 actio-2029 16:24:44 action-2029 16:24:44 action-2029 -- John Foliot to Review discovery & registration of multimodal modality components: state handling https://www.w3.org/tr/mmi-mc-discovery/ -- due 2016-10-20 -- OPEN 16:24:44 http://www.w3.org/WAI/APA/track/actions/2029 16:24:50 MC: Leave open? 16:24:52 JS: yeah 16:24:55 action-2052 16:24:55 action-2052 -- Shane McCarron to Review https://www.w3.org/tr/shadow-dom/ shadow dom -- due 2016-09-28 -- OPEN 16:24:55 http://www.w3.org/WAI/APA/track/actions/2052 16:25:06 MC: Is this urgent? 16:25:13 JS: Don’t recall status 16:25:19 MC: Re-assigned from Cynthia 16:25:24 Can let it sit 16:25:26 JS: Okay 16:25:36 action-2069 16:25:36 action-2069 -- Michael Cooper to Follow up on http://www.w3.org/tr/media-source/ media source extensions -- due 2016-08-04 -- OPEN 16:25:36 http://www.w3.org/WAI/APA/track/actions/2069 16:25:46 MC: leave it 16:25:51 action-2070 16:25:51 action-2070 -- Lisa Seeman to Pick up the thread with https://www.w3.org/tr/css-counter-styles-3/ css counter styles level 3 on needing reply to their response to us -- due 2016-07-20 -- OPEN 16:25:51 http://www.w3.org/WAI/APA/track/actions/2070 16:25:58 JS: Will ping her 16:26:05 Have updated it 16:26:10 zakim, take up next item 16:26:10 agendum 4. "new on TR http://www.w3.org/TR/tr-status-drafts.html" taken up [from janina] 16:26:19 MC: There are 14! 16:26:31 Need to reply to ambient light 16:26:37 Same for audio devices 16:26:50 CSS Scroll Snap Module level 1 16:26:51 -> https://www.w3.org/TR/css-scroll-snap-1/ CSS Scroll Snap Module Level 1 16:27:04 We decided we wanted to have the CSS TF to look at it 16:27:12 It has gone to REC, but haven’t looked 16:27:18 JS: We need to recruit… 16:27:47 MC: Not sure we checked 16:27:53 Should we create an action? 16:28:20 action: janina to get CSS Scroll Snap Module Level 1 into CSS TF radar 16:28:20 Created ACTION-2098 - Get css scroll snap module level 1 into css tf radar [on Janina Sajka - due 2016-11-02]. 16:28:24 action-2098: https://www.w3.org/WAI/APA/wiki/CSS_Scroll_Snap_Module_Level_1 16:28:24 Notes added to action-2098 Get css scroll snap module level 1 into css tf radar. 16:28:50 MC: Next one: CSS Table Module Level 3 16:28:54 First public working draft 16:28:55 -> https://www.w3.org/TR/css-tables-3/ CSS Table Module Level 3 16:29:00 JS: So we have some time? 16:29:15 Should we assign an action? 16:29:27 MC: There is a big banner that covers a large part of my screen. 16:29:48 MC: We’ll defer for now 16:30:13 action: cooper to ping review of CSS Table Module Level 3 - due 15 Feb 16:30:14 Created ACTION-2099 - Ping review of css table module level 3 [on Michael Cooper - due 2016-02-15]. 16:30:38 Generic Sensor API 16:30:46 Media Source Extensions 16:30:56 MC: One of the ones I’m sitting on 16:31:00 Pub sub(?) 16:31:05 -> https://www.w3.org/TR/pubsub/ PubSub 16:31:15 First public working draft 16:31:34 MC: Would like Shane to do it 16:31:51 As in, Shane knows how to translate 16:32:04 JS: Extended time period but put on Shane 16:32:16 MC: 2-3 months? 16:32:18 action: shane to review PubSub https://www.w3.org/TR/pubsub/ - due 3 months 16:32:18 Created ACTION-2100 - Review pubsub https://www.w3.org/tr/pubsub/ [on Shane McCarron - due 2017-01-26]. 16:32:19 JS: 3 months is fine 16:33:02 Service Workers 1 16:33:09 JS: Think Léonie can be of help 16:33:15 LW: Possible not actually 16:33:26 Not a spec I have a great deal to do with out the three of us 16:33:30 -> https://www.w3.org/TR/service-workers-1/ Service Workers 1 16:33:57 JS: So we don’t know who to assign to? 16:34:06 LW: My hunch is that we don’t have to look at it 16:34:13 Will check with other co-chairs 16:34:18 JS: That’s perferct 16:34:33 TD: Not volunteering, but… 16:35:01 Will see a lot of people using it in the coming years 16:35:33 MC: Could give you an action to have someone on your team to look at it 16:35:48 JS: Lets give Léonie an action and let her do her thing 16:35:57 action: watson to check with web platform chairs about a11y implications of service workers https://www.w3.org/TR/service-workers-1/ 16:35:57 Created ACTION-2101 - Check with web platform chairs about a11y implications of service workers https://www.w3.org/tr/service-workers-1/ [on Léonie Watson - due 2016-11-02]. 16:36:17 LW: Week should be fine, thanks 16:36:18 action-2101: https://www.w3.org/WAI/APA/wiki/Service_Workers_1 16:36:19 Notes added to action-2101 Check with web platform chairs about a11y implications of service workers https://www.w3.org/tr/service-workers-1/. 16:36:31 MC: Next spec: spacial data on the web best practices 16:36:36 Is a working group note 16:36:36 -> https://www.w3.org/TR/sdw-bp/ Spatial Data on the Web Best Practices 16:36:39 No working drafts 16:36:53 Guess we can skip this 16:36:56 JS: yeah 16:37:00 Unless anyone objects 16:37:16 MC: Not sure what we did with other spacial specs 16:37:20 Next is… 16:37:26 another note 16:37:32 -> https://www.w3.org/TR/sdw-ucr/ Spatial Data on the Web Use Cases & Requirements 16:37:46 MC: Let’s see if they intend to do something with it 16:37:57 JS: Give it to me, give me two weeks 16:38:21 action: janina to review Spatial Data on the Web Use Cases & Requirements https://www.w3.org/TR/sdw-ucr/ - due 2 weeks 16:38:22 Created ACTION-2102 - Review spatial data on the web use cases & requirements https://www.w3.org/tr/sdw-ucr/ [on Janina Sajka - due 2016-11-09]. 16:38:59 action-2102: https://www.w3.org/WAI/APA/wiki/Spatial_Data_on_the_Web_Use_Cases_%26_Requirements 16:38:59 Notes added to action-2102 Review spatial data on the web use cases & requirements https://www.w3.org/tr/sdw-ucr/. 16:39:15 MC: Next up “Why is this open” 16:39:48 UI events code values 16:39:54 Rich you are reviewing? 16:39:55 -> https://www.w3.org/TR/uievents-code/ UI Events KeyboardEvent code Values 16:39:58 RS: Stuck in the review 16:40:05 MC: Does APA care? 16:40:15 RS: Aren’t those the values you assign to keys? 16:40:24 LW: Yeah, like keyCodes 16:40:34 RS: Not sure that’s an issue for us 16:41:44 MC: Has this been updated since 15th of December? 16:41:49 LW: Key values? 16:41:55 RS: Looking at keyevents 16:42:09 LW: They got changed from DOM Level 3 to keyevents 16:42:17 https://www.w3.org/TR/2016/WD-uievents-key-20161024/ 16:42:36 MC: there is a dated URI on TR 16:42:46 Something has not gone right 16:42:56 Dated URI: 16:42:57 -> https://www.w3.org/TR/2016/WD-uievents-key-20161024/ UI Events KeyboardEvent key Values 16:43:13 Is APA going to track this? 16:43:34 JS: Think we’re comfortable with what ARIA decides to do with it. 16:43:58 -> https://www.w3.org/TR/vehicle-information-service/ Vehicle Signal Server Specification 16:44:20 “The W3C Vehicle Signal Server Specification defines a WebSocket based API that enables client applications to GET, SET, SUBSCRIBE and UNSUBSCRIBE to vehicle signals and data attributes.” 16:44:33 action: janina to review https://www.w3.org/TR/vehicle-information-service/ Vehicle Signal Server Specification 16:44:34 Created ACTION-2103 - Review https://www.w3.org/tr/vehicle-information-service/ vehicle signal server specification [on Janina Sajka - due 2016-11-02]. 16:44:38 JS: Think it relates to personalisation 16:44:41 Give it to me 16:44:53 Need some time, how about 16th of November 16:44:56 action-2103 due 16 Nov 16:44:56 Set action-2103 Review https://www.w3.org/tr/vehicle-information-service/ vehicle signal server specification due date to 2016-11-16. 16:45:15 action-2103: https://www.w3.org/WAI/APA/wiki/Vehicle_Signal_Server_Specification 16:45:15 Notes added to action-2103 Review https://www.w3.org/tr/vehicle-information-service/ vehicle signal server specification. 16:45:19 MC: That clears TR! 16:45:23 *crowd goes wild* 16:45:27 zakim, take up next item 16:45:27 agendum 5. "APA's Accessibility Checklist" taken up [from See Below] 16:46:12 s/CSS WG/websec/ 16:46:24 JS: Main concern is what we do with our list 16:46:34 What to send to other groups when they’re formed 16:46:54 Question is, is what Michael drafted sufficient, what is missing? 16:47:07 MC: Don’t think it’s sufficient, so want to know what is missing. 16:47:50 KHS: Also sent a suggestion on the data format, might be relevant as well. 16:47:56 JS: I missed that, I’m sorry 16:48:05 KHS: Might have sent that directly to you 16:48:18 There is a requirement for health data 16:48:30 They must be accessible when transferred or viewed 16:48:43 Should meet—I think—WCAG Level A. 16:48:48 JS: So a US alw? 16:48:54 s/alw/law/ 16:51:01 JS: Is this a user requirement, more than a spec req? 16:51:54 KHS: So when I change insurance company, they need to give me my health record, it’s now digital. Anyone should be able to look at it, it must be accessible. 16:52:04 JS: Not clear how that affects the data format itself. 16:54:13 q? 16:55:08 LW: Katie do you think this needs a new spec? 16:55:18 KHS: No, think this should be on the accessibility checklist. 16:55:22 One example of where there are data file WCAG2 legal requirements is in the ACA regulations in the US Federal government for Electronic Health Records (as part of the Affordable Health Care Act ACA) where there are certification and test requirements identified. In plain English, the regulation/rule requires that when patients need to access/use their EHR via viewing, downloading or transmitting that the resulting files MUST be WCAG 2 Level A (or AA) confo[CUT] 16:55:38 Specifically the Certification Test Procedure says: The test procedure will evaluate the capability of the EHR technology to permit patients and their authorized representative(s) to view the provider’s name and office contact information and Common MU Data Set using ambulatory EHR technology; and the admission and discharge dates and locations, discharge instructions, and reason(s) for hospitalization, and the Common MU Data Set using inpatient EHR tech[CUT] 16:56:14 http://www.healthit.gov/sites/default/files/2014editionehrcertificationcriteria_mustage2.pdf 16:56:24 §170.314(e)(1) View, download and transmit 16:56:28 JS: Needs more discussion 16:56:35 §170.314(e)(1) View, download and transmit 16:57:22 https://www.healthit.gov/sites/default/files/170_314e1_for_final_posting.pdf 16:57:36 Test Procedure for §170.314 (e)(1) View, download, and transmit to a 3rd party with edge protocol testing 16:57:45 https://www.healthit.gov/sites/default/files/170_314e1_for_final_posting.pdf 16:57:52 RRSAgent, make minutes public 16:57:52 I'm logging. I don't understand 'make minutes public', MichielBijl. Try /msg RRSAgent help 16:57:56 RRSAgent, make minutes 16:57:56 I have made the request to generate http://www.w3.org/2016/10/26-apa-minutes.html MichielBijl 16:58:25 RRSAgent, stop