14:53:50 RRSAgent has joined #wai-wcag 14:53:50 logging to http://www.w3.org/2014/06/17-wai-wcag-irc 14:53:52 RRSAgent, make logs public 14:53:52 Zakim has joined #wai-wcag 14:53:54 Zakim, this will be WAI_WCAG 14:53:54 ok, trackbot; I see WAI_WCAG()11:00AM scheduled to start in 7 minutes 14:53:55 Meeting: Web Content Accessibility Guidelines Working Group Teleconference 14:53:55 Date: 17 June 2014 14:54:05 Chair: AWK 14:54:09 agenda? 14:54:52 regrets+ Kathy Wahlbin, Kathleen Anderson, Barry Johnson 14:55:18 agenda+ Upcoming calls. No call July 1. 14:55:46 agenda+ Cognitive Task Force Report https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Main_Page#Reports 14:56:03 agenda+ June 10 Survey: https://www.w3.org/2002/09/wbs/35422/10thJune2014/ 14:56:41 agenda+ Review of open actions and issues. http://www.w3.org/WAI/GL/track/actions/ http://www.w3.org/WAI/GL/track/issues/ 14:57:00 agenda+ Review of comments https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses 14:57:15 agenda+ Start walking through WCAG SC for pros/cons/improvements: https://www.w3.org/WAI/GL/wiki/Post_WCAG_2 14:58:51 WAI_WCAG()11:00AM has now started 14:58:58 + +1.617.766.aaaa 14:59:17 Sailesh has joined #wai-wcag 14:59:25 zakim, aaaa is AWK 14:59:25 +AWK; got it 14:59:44 +David_MacDonald 14:59:55 +Sailesh_Panchang 15:00:15 Joshue has joined #wai-wcag 15:00:22 Wilco has joined #wai-wcag 15:00:54 marcjohlic has joined #wai-wcag 15:01:21 +??P11 15:02:02 Ryladog has joined #wai-wcag 15:02:03 Lisa_Seeman has joined #wai-wcag 15:02:07 +Marc_Johlic 15:02:17 +??P20 15:02:29 Zakim, who is on the phone? 15:02:29 On the phone I see AWK, David_MacDonald, Sailesh_Panchang, ??P11, Marc_Johlic, Michael_Cooper 15:02:42 + +31.30.239.aabb 15:02:46 David has joined #wai-wcag 15:02:47 zakim, agenda? 15:02:47 I see 6 items remaining on the agenda: 15:02:49 1. Upcoming calls. No call July 1. [from AWK] 15:02:49 2. Cognitive Task Force Report https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Main_Page#Reports [from AWK] 15:02:49 3. June 10 Survey: https://www.w3.org/2002/09/wbs/35422/10thJune2014/ [from AWK] 15:02:50 4. Review of open actions and issues. http://www.w3.org/WAI/GL/track/actions/ http://www.w3.org/WAI/GL/track/issues/ [from AWK] 15:02:50 5. Review of comments https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses [from AWK] 15:02:50 6. Start walking through WCAG SC for pros/cons/improvements: https://www.w3.org/WAI/GL/wiki/Post_WCAG_2 [from AWK] 15:02:51 zakim, i am +31 15:02:51 +Wilco; got it 15:03:38 +[IPcaller] 15:03:47 zakim, [IPcaller] is Joshue 15:03:47 +Joshue; got it 15:03:56 regrets: Kathleen_Anderson, Barry_Johnson, Kathy_Wahlbin 15:03:59 +Katie_Haritos-Shea 15:04:01 agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2014AprJun/0227.html 15:04:27 Zakim, agenda? 15:04:27 I see 6 items remaining on the agenda: 15:04:29 1. Upcoming calls. No call July 1. [from AWK] 15:04:29 2. Cognitive Task Force Report https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Main_Page#Reports [from AWK] 15:04:29 3. June 10 Survey: https://www.w3.org/2002/09/wbs/35422/10thJune2014/ [from AWK] 15:04:29 4. Review of open actions and issues. http://www.w3.org/WAI/GL/track/actions/ http://www.w3.org/WAI/GL/track/issues/ [from AWK] 15:04:30 5. Review of comments https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses [from AWK] 15:04:31 6. Start walking through WCAG SC for pros/cons/improvements: https://www.w3.org/WAI/GL/wiki/Post_WCAG_2 [from AWK] 15:04:52 I have made the request to generate http://www.w3.org/2014/06/17-wai-wcag-minutes.html MichaelC 15:05:01 https://www.w3.org/WAI/GL/wiki/Scribe_List 15:05:03 Chair: AWK 15:05:32 Zakim, who is on the phone? 15:05:32 On the phone I see AWK, David_MacDonald, Sailesh_Panchang, Lisa_Seeman, Marc_Johlic, Michael_Cooper, Wilco, Joshue, Katie_Haritos-Shea 15:06:00 scribe: marcjohlic 15:06:13 Zakim, take up item 1 15:06:13 agendum 1. "Upcoming calls. No call July 1." taken up [from AWK] 15:06:55 zakim, mute me 15:06:55 Joshue should now be muted 15:07:57 Zakim, next item 15:07:57 agendum 2. "Cognitive Task Force Report https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Main_Page#Reports" taken up [from AWK] 15:07:58 AWK: Most of US are typically out for July 4th week - no call scheduled for July 1 15:09:16 AWK: Update on Cognitive Task Force by Lisa Seeman 15:09:33 LS: Moving along - slow progress but there is progress 15:09:37 June Cognitive TF report: https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Reports#June_2014_-_Task_Force_Report 15:09:46 LS: 2 Important issues: 15:10:20 LS: 1) Trying to make a schedule for when we meet w/ WCAG WG - felt the most effective way would be to divide into chunks. This will give us useful deadlines 15:10:40 LS: Want to divide gap analysis - divide into 2 chunks (possibly 3) 15:11:04 LS: First chunk is a background review of disabilities and challenges they face with different ICTs 15:12:00 LS: Aim is to have first chunk ready for informal review (possibly just by chairs) 15:12:12 +q 15:12:17 LS: 6 weeks later to have more of an internal review by WCAG WG and PF 15:12:41 ack j 15:12:41 ack me 15:13:22 JOC: Did you pick user group types - or divide them - what was the methodology? 15:13:56 LS: Wanted to make them as diverse as possible - but also expertise and passion inside of the group 15:14:13 jon_avila has joined #wai-wcag 15:14:30 LS: Sorted by severity 15:14:47 LS: Diverse in functionality 15:15:36 LS: Brain function 15:16:24 + +1.571.389.aacc 15:16:34 zakim, I am aacc 15:16:34 +jon_avila; got it 15:16:53 LS: We've hit on the large groups - learning disabilities, dementia 15:16:59 zakim, queue? 15:16:59 I see no one on the speaker queue 15:17:11 zakim, mute me 15:17:11 Joshue should now be muted 15:18:11 LS: 2) Main work at the moment is to work on the gap analysis.. but also working on 1) Description of the different brain functions 15:18:44 LS: and 2) We're working on a page of "techniques". 15:19:16 LS: The idea is we don't want to lose ideas that come up in the discussions. So we want a place where folks can jot things down as they come up with them. 15:19:40 LS: Big discussion on what that document should look like. 15:19:53 LS: Open to feedback from WCAG WG on the structure of this page 15:20:27 http://accessibility.athena-ict.com/TechniquesCOGA.html 15:20:53 ack me 15:21:50 LS: Again main point is so that we don't lose ideas right now as these things are being discussed. 15:22:38 LS: Not a TF review document at this point 15:24:47 AWK: Will probably want to look at existing techniques at some point to see where these cognitive techniques can fit in 15:25:30 LS: So first chunk is looking at the different user groups (dyslexia etc) - and describing them and their challenges in using ICT. Part of the gap analysis.. stage 1 15:25:42 JOC: Any sense of a time frame on gap analysis? 15:26:34 LS: Hoping to send first chunk in about 6 weeks to 2 months - just for you to review. Full review for working group in about 3 months 15:26:47 LS: And another 3 months for the next chunk 15:27:21 LS: So altogether in 6 months a complete gap analysis 15:28:11 LS: Everything is on our wiki - so always feel free to have a look to see the current state 15:29:08 zakim, queue? 15:29:08 I see no one on the speaker queue 15:29:09 JOC: We'll touch base about the gap analysis toward the end of July and see where we're at - hopefully something for working group to review early august. 15:29:26 -Lisa_Seeman 15:29:36 zakim, mute me 15:29:36 Joshue should now be muted 15:29:36 Zakim, next item 15:29:37 agendum 3. "June 10 Survey: https://www.w3.org/2002/09/wbs/35422/10thJune2014/" taken up [from AWK] 15:30:55 AWK: Anyone else getting 408 errors when going to W3C wiki / comment pages 15:31:07 Wilco: Also getting them 15:31:18 AWK: Have to reload pages several times 15:31:44 MC: Will forward on to System's teams to look into 408 errors / issues 15:33:24 zakim, queue? 15:33:24 I see no one on the speaker queue 15:33:27 TOPIC: 1. Pull request #27 Proposed edit for ACTION-1378 15:36:13 ack me 15:36:39 zakim, mute me 15:36:39 Joshue should now be muted 15:38:40 RESOLUTION: Accept the pull request as proposed and edit the pull request per Josh's response. 15:39:14 TOPIC: 2. Pull request #28 ACTION-184 Example of validating multiple controls 15:40:13 MarcJ: I'd just like to see something better. 15:40:24 AWK: Are you happy with an everything is good message? 15:40:28 MJ: Yup 15:41:23 AWK: I may have changed the example when I pulled it into GitHub 15:41:45 AWK: Will take a look at fixing the example so that it does not give a 404 error when fields are correct. 15:42:01 ack me 15:42:10 zakim, mute me 15:42:10 Joshue should now be muted 15:43:29 MC: Original example (above) seems to be working 15:43:34 +q 15:43:39 ack me 15:43:47 RESOLUTION: Accept pull request 28 15:44:44 zakim, mute me 15:44:44 Joshue should now be muted 15:44:50 TOPIC: 3. New technique: Creating a conforming alternate version for web pages which are designed to be responsive / progressively enhanced 15:45:19 ack me 15:46:06 JOC: Still wasn't clear - some concerns about the framing of it. 15:47:33 AWK: Larger point of this technique is that if you're publishing web pages to a large variety of device types - specifically making different versions for ipods, minis, android, desktop - so that you have a lot of action going on. The suggestion is people may not have resources to test all of the versions. 15:48:25 AWK: Suggestion is that you want to ensure you're doing everything you can making all of your versions accessible, the way to reach conformance is by saying: "This is the version we are fully accessible with - and it can be reached by all other versions". 15:48:32 q+ 15:48:39 AWK: Concerns are that the other version may get left behind 15:49:33 JOC: As an overall would like description tidied up - like the edits that AWK has made. 15:50:06 jamesn_ has joined #wai-wcag 15:50:37 JOC: Example 1 seemed to be a toggle version using javascript - was that the intent? 15:50:56 rrsagent, make minutes 15:50:56 I have made the request to generate http://www.w3.org/2014/06/17-wai-wcag-minutes.html jamesn_ 15:51:10 AWK: Yes, that is correct - that is how Example 1 is working. Instead of just taking you to a different version, it is using a script to strip away the enhancements to bring you back to the simpler, pre-enhanced version 15:51:17 ack d 15:51:18 ack dav 15:51:22 DM: Few thoughts 15:52:06 i'll try number 3 15:52:24 +James_Nurthen 15:52:48 s/overall would/overall approach I would 15:53:38 +q 15:53:41 ack me 15:53:48 DM: We usually separate out progressive enhancement from responsive design 15:55:00 AWK: Talking about progressive enhancement and responsive design as being non-intersecting. 15:55:08 +q 15:55:55 ack j 15:55:58 AWK: My reading on this one is that it is using progressive enhancement to id the target browser and making some enhancements to the base html to arrive at a responsive design for that target 15:56:28 JOC: I see a lot of responsive design (as david pointed out) being at the CSS layer and not scripting 15:57:00 zakim, queue? 15:57:00 I see no one on the speaker queue 15:57:07 JOC: Don't see them as mutually exclusive - may be not real deficit in having htem together, but had initial concern with them being conflated - but may be unfounded? 15:57:37 According to wikipedia page they are related concepts.http://en.wikipedia.org/wiki/Responsive_web_design 15:57:50 thanks jon 15:57:51 q+ 15:58:47 ack sai 15:58:57 s/having htem/having them 15:59:14 Sailesh: Agree with David 16:00:06 +1 16:00:12 Sailesh: They are two different concepts - so maybe there should be 2 separate techniques 16:00:16 ack james 16:00:16 ack ja 16:00:21 http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/C29 16:00:23 JN: We already have a CSS technique for this - C29 16:00:33 http://www.w3.org/TR/WCAG-TECHS/C29.html 16:00:34 http://www.w3.org/TR/WCAG20-TECHS/C29.html 16:00:42 JN: Using a style switcher for conforming version 16:00:54 DM: It's not quite the same 16:01:15 +q 16:01:18 Sailesh: If we could pull progressive enhancement language into C29 16:01:40 Sailesh: Why does this technique talk about both PE and RD? 16:02:12 DM: I think it's a lot of CSS - most of it is CSS changing. May use scripting to control it, but it's CSS 16:03:33 JA: I sent a link from wikipedia - the concepts aren't the same but related 16:04:00 JA: I think they're related but i understand how they could be confusing to the reader. I don't have a strong opinion on this. 16:04:02 ack me 16:04:14 JN: Could we just remove "responsive" from the title? 16:04:41 JOC: Feel it could firm this technique up if it didn't mention "responsive". My hunch is that it should be left out. 16:05:44 Sailesh: Would argue to keep responsive and get rid of "progressive enhancement" 16:06:34 q+ 16:06:39 JOC: Progressive enhancement (PE) has been around, whereas Responsive Design (RD) is relatively new. 16:06:42 q? 16:07:21 ack jon_avila 16:07:29 AWK: So the answer is to remove PE or RD? Just don't have them both in the same technique because they are different? 16:08:27 JA: Based on reading the proposed technique it talks about the pre-enhanced technique. Would be better for PE. I would say we have a separate technique for RD. You have to make the same decisions for RD - "which version do you test". 16:08:33 +1 to Jon 16:08:44 JA: Goes back to the same conformance claims 16:09:01 zakim, mute me 16:09:01 Joshue should now be muted 16:10:03 DM: At some point I do want to create a technique in meeting zoom requirements with RD 16:10:15 DM: Maybe in RD technique we talk about this 16:10:53 +q 16:11:52 AWK: I'm not sure how this technique would be taken apart - it all seems intertwined. 16:12:00 ack me 16:12:26 JOC: Differing opinions on what RD actually is 16:12:44 JOC: Sounds like we're all coming at this from different angles 16:12:59 ack sail 16:13:02 JOC: In terms of progressing with this - I'd like to do whatever will create the least confusion 16:14:13 Sailesh: Primary focus should be RD - but how you attain it - via CSS, or PE can be different 16:15:04 zakim, queue? 16:15:04 I see no one on the speaker queue 16:15:56 AWK: Feel we're getting hung up on a few words here 16:16:14 q+ 16:18:12 q+ 16:18:17 ack jon 16:18:24 JOC: We should get Alistair in on a call as part of this discussion 16:18:37 JA: Test procedure would have to change too if we remove PE 16:20:13 +1 to changing pre-enhanced conforming alt vers language 16:20:22 zakim, queue? 16:20:22 I see jamesn_ on the speaker queue 16:20:23 ack jam 16:20:43 I can't support having a link to http://www.w3.org/TR/mobile-bp/ in this description at all 16:22:03 q? 16:23:08 +q 16:23:48 ack me 16:24:26 q+ 16:25:03 q+ 16:25:10 ack awk 16:26:44 ack jame 16:29:08 RESOLUTION: Leave open - Josh will contact Alistair to see if we can discuss next week on the call 16:31:18 -AWK 16:31:19 -Joshue 16:31:19 -jon_avila 16:31:21 -Sailesh_Panchang 16:31:21 -Katie_Haritos-Shea 16:31:22 -James_Nurthen 16:31:23 -Wilco 16:31:25 -Michael_Cooper 16:31:25 -David_MacDonald 16:31:32 zakim, list attendees 16:31:32 As of this point the attendees have been +1.617.766.aaaa, AWK, David_MacDonald, Sailesh_Panchang, Marc_Johlic, Michael_Cooper, Lisa_Seeman, +31.30.239.aabb, Wilco, Joshue, 16:31:35 ... Katie_Haritos-Shea, +1.571.389.aacc, jon_avila, James_Nurthen 16:31:46 rrsagent, make minutes 16:31:46 I have made the request to generate http://www.w3.org/2014/06/17-wai-wcag-minutes.html marcjohlic 16:31:54 Sailesh has joined #wai-wcag 16:33:23 -Marc_Johlic 16:33:25 WAI_WCAG()11:00AM has ended 16:33:25 Attendees were +1.617.766.aaaa, AWK, David_MacDonald, Sailesh_Panchang, Marc_Johlic, Michael_Cooper, Lisa_Seeman, +31.30.239.aabb, Wilco, Joshue, Katie_Haritos-Shea, 16:33:25 ... +1.571.389.aacc, jon_avila, James_Nurthen 17:04:52 jamesn has joined #wai-wcag 17:28:55 Sailesh has joined #wai-wcag