15:49:07 RRSAgent has joined #apa 15:49:07 logging to http://www.w3.org/2016/03/30-apa-irc 15:49:09 RRSAgent, make logs world 15:49:09 Zakim has joined #apa 15:49:11 Zakim, this will be 15:49:11 I don't understand 'this will be', trackbot 15:49:12 Meeting: Accessible Platform Architectures Working Group Teleconference 15:49:13 Date: 30 March 2016 15:49:18 zakim, agenda? 15:49:18 I see nothing on the agenda 15:49:23 agenda+ preview agenda with items from two minutes 15:49:23 agenda+ Web Payments Teleconference Reminder -- Shane, Janina 15:49:23 agenda+ CSUN Highlights -- Open Discussion 15:49:23 agenda+ CSS Progress -- Rich, Cynthia, Michael, Leonie 15:49:24 agenda+ W3C Spec Styling Issues -- Michael 15:49:25 agenda+ Actions Procedure Tweaks -- Janina, Michael 15:49:28 agenda+ Actions Review (Specs) https://www.w3.org/WAI/APA/track/products/8 15:49:30 agenda+ new on TR http://www.w3.org/TR/tr-status-drafts.html 15:49:33 agenda+ Other Business 15:49:35 agenda+ next and future meetings 15:49:38 agenda+ be done 15:51:51 chair: Janina 15:51:59 zakim, next item 15:51:59 agendum 1. "preview agenda with items from two minutes" taken up [from janina] 15:57:43 present+ Janina 15:58:23 present+ Joanmarie_Diggs 16:00:04 fesch has joined #apa 16:03:44 Gottfried has joined #apa 16:05:58 present+ Michiel_Bijl 16:06:08 present+ fesch 16:08:12 Rich has joined #apa 16:09:41 text/list 16:10:09 present+ MichaelC 16:11:02 janina has changed the topic to: APA Teleconference; Wednesday 30 March 16:12:16 scribe: me 16:12:26 scribe: Gottfried 16:13:19 zakim, next item 16:13:19 agendum 2. "Web Payments Teleconference Reminder -- Shane, Janina" taken up [from janina] 16:14:03 Janina: We have committed to work on a review as a subteam. Next Mon at 1pm EDT. 3 people have signed up. Others are welcome to join. 16:14:12 zakim, close item 16:14:12 I don't understand 'close item', Gottfried 16:14:18 zakim, close this item 16:14:18 agendum 2 closed 16:14:20 I see 9 items remaining on the agenda; the next one is 16:14:20 3. CSUN Highlights -- Open Discussion [from janina] 16:14:25 zakim, open next item 16:14:25 agendum 3. "CSUN Highlights -- Open Discussion" taken up [from janina] 16:15:15 Janina: Really hot braille display... 16:15:57 Rich: Pearson working on an editor for digital math, supports braille displays. Awesome. 16:16:33 ... If the user can navigate a math equation via keyboard, math understanding increases by 10-15%. 16:17:24 Janina: American Printing House & NFB cooperation for braille display. 16:17:44 ... Will be much cheaper than current devices, about $500. 16:18:27 zakim, next item 16:18:27 agendum 4. "CSS Progress -- Rich, Cynthia, Michael, Leonie" taken up [from janina] 16:21:09 Rich: We asked them to deal with the interop issue, e.g. flex box, content injection. If it doesn't support accessibility, WCAG people will be forced to mark this technology as not accessible. 16:21:28 ... Then it comes back to you - why didn't you make this accessible? 16:22:49 ... Met with Rosson and Bogdan, CSS co-chair. Interop spec for CSS. Can we work on this together? How do we staff it? - Was a good meeting. 16:23:31 Michael: Called "CSS accessibility API mapping spec". Best practices doc is needed. They had agreed to work on this in the past. 16:24:45 ... They told us it would be helpful to provide test cases demonstrating the concerns. We also talked of solving the navigation problem. Need to take a look at this from a broader perspective, across technologies (HTML, CSS, SVG). 16:25:28 ... For flex-box issues and similar layout issues, we need the navigation problem solved. But cannot be done quickly. We might not be able to close this work before they close the specs. 16:25:59 ... Joint tf between APA and CSS wgs? If CSS doesn't support this, we could create a CSS focus group ourselves. 16:26:29 Janina: Who could do this? 16:26:51 Michael: Cynthia? Bogdan? 16:27:27 ... We need to help them understand the issues and to solve them. We need to provide resources for this. 16:27:44 Janina: How can we make them understand the problem? 16:28:01 Michael: Test cases. 16:28:26 ... CSS flex-box is implemented, and we can easily demonstrate the problem. 16:29:05 Janina: Maybe Matt is interested in this? 16:29:34 Rich: The a11y tree needs to be reordered. With that they did not have an issue. 16:30:55 ... They were reluctant to deal with keyboard tab index issues. They want tab index modifications be done by the author. Might be less problematic than restructuring the DOM. But the solution for tab index requires positive integers to change order. Very brittle solution. We need to go back and look at kb navigation again, also other types of input. 16:31:45 ... Similar issues with SVG, directional navigation - not possible with tab index. Feature in XHTML was to build a link chain for focus navigation. We need to bring back this concept back. 16:32:09 q+ 16:33:07 ack me 16:33:09 Michael: I was referencing most of what you said. We keep referring to other groups to solve the problem. 16:33:53 ... Rough plan was to start now with CSS a11y API mapping. Navigation issues need to be addressed likely in a separate document. 16:34:10 ... Still need the people to work on this 16:34:40 Janina: Still concerned about whether CSS and other graphics people are fully convinced about what we talk about is a real problem. 16:35:05 ... We need to illustrate the problem in a couple of test pages. 16:35:20 Michael: Issue of generated content not being exposed is already illustrated. 16:35:50 Fred: Talk to Matt and Brian? 16:36:02 s/Brian/Bryan/ 16:36:33 ... Show them how it impacts the user. Need the personal user experience and awareness of the issue. 16:36:50 Michael: Walk them through a demo file rather than just talking. 16:37:36 Janina: We can invite Bryan. 16:38:21 ... Next steps are to draw Matt and/or Bryan into another conversation. 16:38:33 Michael: Cynthia should be involved as well. Also ARIA wg. 16:38:52 ... Session in ARIA group on CSS. 16:39:05 Rich: Right now, don't have any room on our plates. 16:40:03 Michael: Suggest Cynthia starts the mapping, and ARIA should be informed that this would become a deliverable of them. 16:40:27 Rich: No time right now at all in ARIA, until ARIA advances. 16:40:56 Michael: Fair enough. What can we do on this from an APA perspective? 16:41:20 ... Can we take this up in APA? 16:42:06 Janina: How can we avoid going silent on this? Let me see if we can talk with Matt and Cynthia next week. First step would be to demonstrate the issues. 16:42:27 ... Put together some illustrations to keep activity happening. 16:42:39 Michael: Rosson was saying he would come back to this group. 16:42:49 ... Willing to talk to us by end of this week. 16:43:29 ... Should also inform WAI coordination committee (or similar name). 16:43:40 zakim, next item 16:43:40 agendum 5. "W3C Spec Styling Issues -- Michael" taken up [from janina] 16:44:03 Janina: What is left over? 16:44:28 Michael: People weren't surprised by the styles. We need to sort out problems over time. 16:44:55 ... In theory, they want to revise the styles annually. Both an opportunity to get improvements in next time, but also obligation to check things out next year. 16:45:18 Gottfried: Is there a process for us to check their styles before they go public? 16:45:34 Michael: Yes, there is a process. We missed it this time - wasn't well coordinated. 16:45:54 zakim, next item 16:45:54 agendum 6. "Actions Procedure Tweaks -- Janina, Michael" taken up [from janina] 16:46:19 s/wasn't well coordinated/wasn't well coordinated on our end/ 16:46:50 Janina: How can we work with our actions more cleanly? 16:47:06 ... Suggest to make the action item reviews simply as pending/done etc. 16:47:32 ... If people have finished their action items, they should send a message to the group, and i will then take it up for the agenda of the next meeting. 16:48:01 Gottfried: Good suggestion. Email with action item number gets recorded in the system. 16:48:19 Michael: People need to remember this. 16:48:50 Gottfried: Send automatic reminders? 16:49:47 Michael: Not a feature as far as i know. Could send a feature request. Also can get ennoying for authors. 16:50:05 Gottfried: Send an automatic email when the action item is created? 16:50:15 Michael: Yes, we can make this setting. 16:50:22 Janina: Good suggestion 16:50:25 zakim, next item 16:50:25 agendum 7. "Actions Review (Specs) https://www.w3.org/WAI/APA/track/products/8" taken up [from janina] 16:51:03 action-2019? 16:51:03 action-2019 -- Fred Esch to Review css fragmentation module level 3 https://www.w3.org/tr/css-break-3/ -- due 2016-03-16 -- OPEN 16:51:03 http://www.w3.org/WAI/APA/track/actions/2019 16:51:15 Fred: Same issues as other CSS specs. 16:51:40 ... Did an update on this. 16:51:44 close action-2019 16:51:44 Closed action-2019. 16:51:50 action-2016? 16:51:50 action-2016 -- Michiel Bijl to Review clipboard api and events http://www.w3.org/tr/clipboard-apis/ -- due 2016-03-16 -- OPEN 16:51:50 http://www.w3.org/WAI/APA/track/actions/2016 16:52:34 Michiel: I have sent an issue to them. We can now close this action. 16:52:43 Michael: Should we wait for the response before we close it? 16:52:52 https://github.com/w3c/clipboard-apis/issues/26 16:53:38 Michiel: They have replied. 16:53:55 close action-2016 16:53:56 Closed action-2016. 16:54:21 ... Spec should be focused on what happens between browser and JavaScript. Issue is regarded as off-topic. 16:54:33 Michael: Can we put this on the agenda of next week? 16:55:05 zakim, next item 16:55:05 agendum 8. "new on TR http://www.w3.org/TR/tr-status-drafts.html" taken up [from janina] 16:55:36 Michael: There are 14 specs we haven't look at yet 16:55:45 -> https://www.w3.org/TR/cssom-1/ CSS Object Model (CSSOM) 16:56:28 Michael: Wondering if it is just a DOM for CSS. Maybe not so important for us. Do we need to look at this? 16:56:35 Fred: I will look at this. 16:57:37 ACTION: fresch to review CSS Object Model (CSSOM) https://www.w3.org/TR/cssom-1/ by 2016-04-13. 16:57:37 Error finding 'fresch'. You can review and register nicknames at . 16:57:49 -> https://www.w3.org/TR/css-snappoints-1/ CSS Scroll Snap Points Module Level 1 16:57:57 ACTION: fesch to review CSS Object Model (CSSOM) https://www.w3.org/TR/cssom-1/ by 2016-04-13. 16:57:58 Created ACTION-2020 - Review css object model (cssom) https://www.w3.org/tr/cssom-1/ by 2016-04-13. [on Fred Esch - due 2016-04-06]. 16:59:25 ACTION: MichaelC to review CSS Scrolll Snap Points Module Level 1 https://www.w3.org/TR/css-snappoints-1/. 16:59:25 Created ACTION-2021 - Review css scrolll snap points module level 1 https://www.w3.org/tr/css-snappoints-1/. [on Michael Cooper - due 2016-04-06]. 16:59:41 action-2020? 16:59:41 action-2020 -- Fred Esch to Review css object model (cssom) https://www.w3.org/tr/cssom-1/ by 2016-04-13. -- due 2016-04-06 -- OPEN 16:59:41 http://www.w3.org/WAI/APA/track/actions/2020 16:59:43 action-2020 due 2 weeks 16:59:43 Set action-2020 Review css object model (cssom) https://www.w3.org/tr/cssom-1/ by 2016-04-13. due date to 2016-04-13. 17:00:33 zakim, bye 17:00:33 leaving. As of this point the attendees have been Janina, Joanmarie_Diggs, Michiel_Bijl, fesch, MichaelC 17:00:33 Zakim has left #apa 17:00:37 actions? 17:01:25 rrsagent, make log member 17:01:48 rrsagent, remove action 1 17:01:48 I'm logging. I don't understand 'remove action 1', Gottfried. Try /msg RRSAgent help 17:02:24 rrsagent, drop action 1 17:02:31 actions? 17:02:50 rrsagent, draft minutes 17:02:50 I have made the request to generate http://www.w3.org/2016/03/30-apa-minutes.html Gottfried 17:28:35 Rich has joined #apa 18:07:57 Rich has joined #apa 18:27:03 Rich has joined #apa 18:40:46 Rich has joined #apa 18:55:18 rrsagent, make log world 18:55:20 rrsagent, bye 18:55:20 I see 2 open action items saved in http://www.w3.org/2016/03/30-apa-actions.rdf : 18:55:20 ACTION: fesch to review CSS Object Model (CSSOM) https://www.w3.org/TR/cssom-1/ by 2016-04-13. [2] 18:55:20 recorded in http://www.w3.org/2016/03/30-apa-irc#T16-57-57 18:55:20 ACTION: MichaelC to review CSS Scrolll Snap Points Module Level 1 https://www.w3.org/TR/css-snappoints-1/. [3] 18:55:20 recorded in http://www.w3.org/2016/03/30-apa-irc#T16-59-25