16:53:13 RRSAgent has joined #apa 16:53:13 logging to http://www.w3.org/2016/01/13-apa-irc 16:53:15 RRSAgent, make logs world 16:53:17 Zakim, this will be 16:53:18 I don't understand 'this will be', trackbot 16:53:18 Meeting: Accessible Platform Architectures Working Group Teleconference 16:53:19 Date: 13 January 2016 16:53:44 agenda? 16:53:54 zakim, clear agenda 16:53:54 agenda cleared 16:54:00 agenda+ preview agenda with items from two minutes 16:54:00 agenda+ APA Housekeeping http://www.w3.org/2015/10/apa-charter.html 16:54:00 agenda+ Actions Review (Specs) http://www.w3.org/WAI/PF/Group/track/actions/open 16:54:00 agenda+ new on TR http://www.w3.org/TR/tr-status-drafts.html 16:54:01 agenda+ Pending CSS Flexbox CR http://dev.w3.org/csswg/css-flexbox-1/ 16:54:03 agenda+ Proposed Final Design for W3C Technical Reports http://lists.w3.org/Archives/Public/public-apa/2016Jan/0007.html 16:54:06 agenda+ Draft APA Decision Policy http://www.w3.org/WAI/APA/decision-policy 16:54:08 agenda+ Other Business 16:54:11 agenda+ next and future meetings http://www.w3.org/Guide/1998/08/teleconference-calendar#s_273 16:54:14 agenda+ be done 16:54:46 zakim, next item 16:54:46 agendum 1. "preview agenda with items from two minutes" taken up [from janina] 16:59:43 fesch has joined #apa 17:00:07 agenda: https://lists.w3.org/Archives/Public/public-apa/2016Jan/0023.html 17:01:48 present+ LJWatson 17:02:43 present+ fesch 17:02:49 richardschwerdtfeger has joined #apa 17:03:05 Present+ Rich_Schwerdtfeger 17:03:19 present+ janina 17:04:21 scribe: fesch 17:06:15 what agendum is this? 17:06:20 present+ Joanmarie_Diggs 17:07:59 js: news items? 17:08:29 rs: Samsung US is moving to dpub 17:09:11 zakim, next item 17:09:11 agendum 2. "APA Housekeeping http://www.w3.org/2015/10/apa-charter.html" taken up [from janina] 17:09:38 js: we have tracker set up anything else? 17:09:53 q+ to ask about making tracker readonly 17:10:00 q- 17:10:19 mc: all is set up, wiki, tracker... please abandon the the PF tracker 17:10:51 mc: we are ready to request PF tracker be shut down 17:11:23 js: wiki for logging specs... provides bread crumbs... that may be remaining infrastructure 17:11:39 mc: I am putting specs in the wiki as we look at them 17:12:02 mc: I haven't copied stuff from the PF wiki to APA wiki, spec reviews are new 17:13:57 mc: need to change password... 17:14:41 JF has joined #apa 17:15:18 js: membership - James N (Oracle) lost, he couldn't get approval for another group, Cynthia not yet in... we are thin on browser support (only Yandex) 17:15:48 zakim, next item 17:15:48 agendum 3. "Actions Review (Specs) http://www.w3.org/WAI/PF/Group/track/actions/open" taken up [from janina] 17:16:07 https://www.w3.org/WAI/APA/track/products/8 17:16:41 close action-1763 17:16:41 Closed action-1763. 17:16:55 present+ JF 17:17:54 js: digital publishing will meet with us next week 17:18:28 Pointer Lock https://w3c.github.io/pointerlock/ 17:18:34 lw: have question on pointer lock 17:21:25 http://www.w3.org/TR/uievents/ 17:21:49 action-1749: http://www.w3.org/TR/uievents/ 17:21:50 Notes added to action-1749 Review ui events. 17:21:55 action-1750: http://www.w3.org/TR/uievents/ 17:21:55 Notes added to action-1750 Review ui events. 17:24:16 jamesn has joined #apa 17:24:22 Q+ 17:24:24 js: I don't see anyone setting up a UI without using ARIA, data changing on the fly, we may want them to make them say that in their spec. they have a section on security, so maybe we want an accessibility statement 17:25:21 q? 17:25:25 ack jf 17:25:33 http://www.w3.org/tr/webmidi/ 17:25:35 js: do we want to ask for sections on accessibility? 17:26:22 jf: At TPAC we talked about this and we have this as a global need as well 17:26:37 q? 17:27:24 js: I don't want to close this action without some comfort that accessibility is being addressed, maybe we want to point them to authoring guide 17:27:33 js: think about a statement for it 17:28:03 zakim, next item 17:28:03 agendum 4. "new on TR http://www.w3.org/TR/tr-status-drafts.html" taken up [from janina] 17:28:45 rs: those are the UI events from HTML is there anything new? 17:29:02 js: that is a question, we may be able to close it? 17:29:07 -> https://www.w3.org/TR/gamepad/ Gamepad 17:29:45 action: Léonie to review Gamepad https://www.w3.org/TR/gamepad/ 17:29:45 Created ACTION-2001 - Review gamepad https://www.w3.org/tr/gamepad/ [on Léonie Watson - due 2016-01-20]. 17:31:16 -> https://www.w3.org/TR/wcag2-ext-req/ Requirements for WCAG 2.0 Extensions 17:31:59 -> https://www.w3.org/TR/webmention/ Webmention 17:32:59 -> https://www.w3.org/TR/social-web-protocols/ Social Web Protocols 17:34:12 action: fesch to review Social Web Protocols https://www.w3.org/TR/social-web-protocols/ 17:34:12 Created ACTION-2002 - Review social web protocols https://www.w3.org/tr/social-web-protocols/ [on Fred Esch - due 2016-01-20]. 17:34:44 -> https://www.w3.org/TR/dwbp/ Data on the Web Best Practices 17:36:06 lw: found email requesting us look at presentation API on Nov 6 17:36:22 Presentation API http://w3c.github.io/presentation-api/ 17:40:00 jd: interested in topic, next couple of weeks is tough 17:40:28 action: joanie to review Presentation API https://www.w3.org/TR/presentation-api/ - due 17 Feb 17:40:28 Created ACTION-2003 - Review presentation api https://www.w3.org/tr/presentation-api/ [on Joanmarie Diggs - due 2016-02-17]. 17:41:56 zakim, next item 17:41:56 agendum 5. "Pending CSS Flexbox CR http://dev.w3.org/csswg/css-flexbox-1/" taken up [from janina] 17:42:41 js: rich wrote up a email explaining the concern 17:43:11 js: CSS has some good approaches, but haven't documented them 17:43:37 js: we may need to ask them to document it... lets remember what was said at TPAC 17:44:12 http://lists.w3.org/Archives/Public/public-apa/2016Jan/0025.html 17:44:18 jnurthen has joined #apa 17:44:37 rs: flexbox changes the DOM order which is different than visible order.... if the flexbox order is meaningful then tabindex should follow flexbox order 17:45:52 rs: young designers want to use it and it causes accessibility problems, creates work, folks with disability get a worse experience and accessibility folks look like meanies, 17:46:23 rs: totally preventable ... by having flexbox affect the tab and read order 17:46:30 TPAC Discussion: http://www.w3.org/2015/10/30-apa-minutes.html 17:46:54 rs: we have the same issue in WCAG 1 .... we are repeating history... 17:47:06 q? 17:47:14 rs: similar problem with content injection 17:47:21 q+ 17:47:48 rs: representative of a bigger problem, CSS working group needs to work on interoperability 17:48:10 js: agree with you rich 17:48:24 Q+ 17:48:32 Q+ 17:48:57 ack fe 17:49:09 fe: round display and grid layout have the same issue 17:49:29 ack jw 17:49:30 Jesse Beach 17:49:32 ack JF 17:49:38 ack lj 17:50:07 lw: in Sapporo, Jesse (facebook) presented a demo, had discussion, doesn't change DOM and not API something in the middle 17:50:57 jn: kind of works, affects keyboard sequence by not AT read order... two sequences are different in Firefox, other browsers may have wrong order but both orders the same 17:51:05 q+ 17:51:10 lw: in the browser is where stuff needs to happen 17:51:44 js: CSS need to document stuff they haven't yet documented, we may object to spec moving forward... 17:52:07 ack me 17:52:13 +1 to Janina's point(s) - fantasai spoke directly to the gaps in documentation 17:52:18 rs: happy to work with browser vendors, but CSS has to help and document, history is repeating 17:52:44 rs: we don't know what CSS next steps are... 17:53:22 js: I promised a response this week, fairly well recorded in minutes at TPAC... 17:53:55 js: thought the FF approach could work.... CSS wants to move to PR sometime around May 17:54:19 q? 17:54:22 ack 17:54:25 q? 17:54:27 js: need to have gap covered, documented or steps moving forward 17:54:29 ack me 17:54:49 s/in Sapporo, Jesse (facebook) presented a demo, had discussion, doesn't change DOM and not API something in the middle/in Sapporo, Jesse (facebook) presented a demo, had discussion about Firefox's attempt to resolve the problem, which doesn't change DOM or API but does something in the middle/ 17:55:35 js: don't mind stuff moving to CR as long as we can ask for changes in CR... 17:55:44 zakim, next item 17:55:44 agendum 7. "Draft APA Decision Policy http://www.w3.org/WAI/APA/decision-policy" taken up [from janina] 17:56:38 agenda? 17:56:48 zakim takeup item 6 17:56:57 zakim, take up item 6 17:56:57 agendum 6. "Proposed Final Design for W3C Technical Reports http://lists.w3.org/Archives/Public/public-apa/2016Jan/0007.html" taken up [from janina] 17:57:39 js: standard practice vs what WCAG requires 17:57:52 js: for links 17:58:28 js: WCAG on requires that it be recognized that a link be recognized as a link 17:59:07 js: we didn't find anything where WCAG says the foreground and background color changes... 17:59:26 Q+ 17:59:41 js: will cast the net wider, this is a major enough issue, that I can write this up for the WAI list 17:59:48 q? 17:59:50 js: comments? 17:59:53 ack jf 18:00:43 jf: One issue - when you have an actionable item, need a color identifier, the underline is not 18:01:15 jf: WCAG does not talk about identification of actionable items... 18:01:25 q+ 18:01:45 jf: I think actionable items need a contrast ratio 18:02:34 js: we need color contrast, do we want the text for a link need a different color? 18:02:37 q+ 18:03:11 jf: low vision user needs to be able to see and recognize an actionable element 18:03:34 q? 18:03:54 jn: she has modified the color contrast to 3:1 18:04:47 jn: 4.5 allows you to read, 3:1 can be seen, a survey of 1 said he liked the underlined links 18:05:09 q- 18:05:50 jf: I don't think we have enough data to say 4.5 for text and 3:1 for underline is OK 18:06:34 jn: there is an WCAG understanding document that says you can use color and other (underline) as a way to show it 18:06:51 jf: I disagree 18:07:32 jn: sometimes you need to, how else will you differentiate visited vs unvisited links? 18:07:59 jn: need the low vision folks to say 18:08:20 js: I should take this to a wider list 18:08:54 js: the problem happens when you add the third visited (vs unvisited) link 18:09:05 jn: folks can change their link color 18:09:31 jf: since this is a W3C style guide, we should eat our own dog food... 18:10:00 jn: I think this is a good template that helps people, want to see it adopted.... 18:10:27 jf: perhaps my objections are to big... 18:11:17 js: next week we will have dpub and pointerlock 18:11:29 rrsagent, make minutes 18:11:29 I have made the request to generate http://www.w3.org/2016/01/13-apa-minutes.html fesch 19:42:06 richardschwerdtfeger has joined #apa 21:30:17 chaals has joined #apa 21:38:53 richardschwerdtfeger has left #apa