14:50:09 RRSAgent has joined #wai-wcag 14:50:09 logging to http://www.w3.org/2014/06/24-wai-wcag-irc 14:50:10 RRSAgent, make logs public 14:50:12 Zakim, this will be WAI_WCAG 14:50:12 ok, trackbot; I see WAI_WCAG()11:00AM scheduled to start in 10 minutes 14:50:13 Meeting: Web Content Accessibility Guidelines Working Group Teleconference 14:50:13 Date: 24 June 2014 14:50:41 agenda+ Reminder No call next week - July 1 14:50:52 zakim, agenda? 14:50:52 I see 5 items remaining on the agenda: 14:50:53 3. June 10 Survey: https://www.w3.org/2002/09/wbs/35422/10thJune2014/ [from AWK] 14:50:53 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] 14:50:53 5. Review of comments https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses [from AWK] 14:50:54 6. Start walking through WCAG SC for pros/cons/improvements: https://www.w3.org/WAI/GL/wiki/Post_WCAG_2 [from AWK] 14:50:56 7. Reminder No call next week - July 1 [from Joshue] 14:51:55 zakim, clear agenda 14:51:55 agenda cleared 14:52:07 agenda+ Reminder No call next week - July 1 14:52:32 agenda+ Discussion with WCAG-EM about changes and requested review (Shadi - 15 minutes) 14:52:57 agenda+ If ready, discussion on EO proposal for 'techniques being informative' wording 14:53:17 agenda+ Review of open actions and issues. http://www.w3.org/WAI/GL/track/actions/ http://www.w3.org/WAI/GL/track/issues/ 14:53:36 agenda+ Review of comments https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses 14:53:52 agenda+ Start walking through WCAG SC for pros/cons/improvements: 14:53:52 New Survey https://www.w3.org/2002/09/wbs/35422/24June2014/ 14:53:52 https://www.w3.org/WAI/GL/wiki/Post_WCAG_2 14:54:13 agenda+ From June 10 Survey: https://www.w3.org/2002/09/wbs/35422/10thJune2014/ 14:54:13 Continuation of discussion on Alistairs technique and F76 (Items #3 and #4) 14:54:30 Scribe list: https://www.w3.org/WAI/GL/wiki/Scribe_List 14:54:36 Chair: Joshue 14:56:33 WAI_WCAG()11:00AM has now started 14:56:40 +[IPcaller] 14:56:42 zakim, [IPcaller] is Joshue 14:56:42 +Joshue; got it 14:56:52 Kenny has joined #wai-wcag 14:57:31 zakim, call shadi-617 14:57:31 ok, shadi; the call is being made 14:57:32 +Shadi 14:57:44 Wilco has joined #wai-wcag 14:58:37 alistair has joined #wai-wcag 14:59:36 zakim, who is on the phone? 14:59:36 On the phone I see Joshue, Shadi 14:59:39 bbailey has joined #wai-wcag 15:00:09 +[IPcaller] 15:00:11 zakim, ipcaller is alistair 15:00:11 +alistair; got it 15:00:26 +Wilco 15:00:52 +Kenny 15:01:03 +Bruce_Bailey 15:01:17 zakim, i am bruce 15:01:17 ok, bbailey, I now associate you with Bruce_Bailey 15:01:18 zakim, who is on the phone? 15:01:19 On the phone I see Joshue, Shadi, alistair, Wilco, Kenny, Bruce_Bailey 15:01:19 +??P20 15:01:25 zakim, mute me 15:01:25 Shadi should now be muted 15:01:46 -??P20 15:01:52 +??P22 15:02:25 jon_avila has joined #wai-wcag 15:02:59 https://www.w3.org/WAI/GL/wiki/Scribe_List 15:03:20 + +1.703.637.aaaa 15:03:25 zakim, I am aaaa 15:03:25 +jon_avila; got it 15:03:55 marcjohlic has joined #wai-wcag 15:04:09 EricVelleman has joined #wai-wcag 15:04:12 +Marc_Johlic 15:04:20 scribe: jon_avila 15:04:46 zakim, next item 15:04:46 agendum 1. "Reminder No call next week - July 1" taken up [from Joshue] 15:04:51 +David_MacDonald 15:05:17 +EricVelleman 15:05:26 + +1.703.825.aabb 15:06:12 zakim, next item 15:06:12 agendum 2. "Discussion with WCAG-EM about changes and requested review (Shadi - 15 minutes)" taken up [from Joshue] 15:06:24 ack me 15:06:30 http://lists.w3.org/Archives/Public/w3c-wai-gl/2014AprJun/0249.html 15:06:48 zakim, mute me 15:06:48 Joshue should now be muted 15:06:50 TOPIC: Updates with WCAG Evaluation Methodology 15:07:20 shadi: working on processing comments on January publication of working draft. Have reorganized and editorial changes. 15:07:58 shadi: few substantial changes from comments and discussions that we already had with WCAG WG. We believe that we have addressed all comments and arguments and this is a complete document that is ready for publication as WCAG WG note. 15:08:13 shadi: non-normative - informative document, support document to WCAG 2.0. 15:08:34 http://www.w3.org/WAI/ER/conformance/ED-methodology-20140623#step5d 15:08:43 shadi: Walk us through particular changes that may want our attention, 5d: provide an aggregated score. 15:08:59 David has joined #wai-wcag 15:09:11 link to doc again please 15:09:28 shadi: Before the score was based on adding up violations -- based on f2f meeting, that algorithm and procedure was removed. But leave in guidance and caution about when you provide an aggregated score. 15:09:34 http://www.w3.org/WAI/ER/conformance/ED-methodology-20140623#step5d 15:09:53 +q to ask if there is still any suggested metric in the doc to do a score with 15:09:58 http://www.w3.org/WAI/ER/conformance/ED-methodology-20140623#step4a 15:09:59 shadi: goal to provide guidance to those who provide this info but not prescribe something that isn't agreed upon by all parties 15:10:41 shadi: step 4a - could use WCAG review. How to check WCAG conformance. This isn't new and has been reviewed but this has been pulled together into one section with different structure with a different editorial approve. 15:11:23 shadi: Point to FAQ where review of techniques is not required for making conformance. Also talk about alternative versions, accessibility support, and non-interference; also link to more places in WCAG for guidance. 15:11:42 zakim, queue? 15:11:42 I see Joshue on the speaker queue 15:11:49 shadi: hope to get approve from WGs to publish this as WG note and provide to the public as a useful resource. 15:12:19 ack me 15:12:20 Joshue, you wanted to ask if there is still any suggested metric in the doc to do a score with 15:12:27 eric: Changes mostly rearranging content that has already been reviewed. 15:12:32 q+ to ask about full page alternate page vs. component 15:13:03 jo: Survey in following weeks call -- thanks for bringing this up. Do you have any suggested method for aggregation? 15:13:04 zakim, queue? 15:13:04 I see David on the speaker queue 15:13:32 shadi: we don't provide any method for scoring aggregation -- we provide info of info how they can be used and how they can be misleading. 15:13:51 shadi: There is ongoing research and activity. There is no single measure that addresses all of the quality criteria. 15:13:52 q+ to ask about reference FAQ rather than copy FAQ? I worry that FAQ is less authoritative and more likely to updated (so less stable). 15:14:11 ack dav 15:14:11 David, you wanted to ask about full page alternate page vs. component 15:14:59 david: You talked about alternative formats -- what about components versus pages. Example of date pickers, do you need date picker or will a text box suffice -- is there any discussion about that? 15:15:35 http://www.w3.org/WAI/ER/conformance/ED-methodology-20140623#alternate-versions 15:15:44 eric: Have not further interpreted those issues - we tried to summarize current guidance and provide resources. Our understanding is that WCAG allows both. 15:15:46 zakim, mute me 15:15:46 Joshue should now be muted 15:16:04 eric: we use example in understanding doc with a video that has captions and one that does not. 15:16:16 ack me 15:16:20 eric: info in understanding document could be further improved. 15:16:23 david: agree with that. 15:16:34 ack bruce 15:16:34 Bruce_Bailey, you wanted to ask about reference FAQ rather than copy FAQ? I worry that FAQ is less authoritative and more likely to updated (so less stable). 15:17:27 bb: really need to address language about components and alternative versions. Wanted to ask about EM - significant editorial changes. Why not have FAQ right inside the document? 15:18:07 eric: good question - could consider quoting them rather than referring to them. One click less -- downside is that if those get refined or updated then maintenance issues. 15:18:47 zakim, queue? 15:18:47 I see no one on the speaker queue 15:19:14 bb: FAQs are not subject to level of review as other documents. Rather have EM contain snapshot of FAQs at this time rather than links. 15:19:21 eric: could you put that in your survey? 15:19:53 shadi: we've opened a survey like we did last time. Prefer to have all comments in one place. 15:19:58 https://www.w3.org/2002/09/wbs/1/WCAG-EM-20140623/ 15:20:06 https://www.w3.org/2002/09/wbs/1/WCAG-EM-20140623/ 15:20:46 jo: let's use EM survey link -- send out on Friday to group. People will have time to answer. 15:21:24 shadi: Please put your comments in the survey and Eric and I will think about it. I was hoping survey was already open from Tuesday to Tuesday. 15:21:47 jo: will get survey emailed out to the list after the call. 15:22:43 shadi: Yes, that would be great to re-forward that -- let me know about timelines. If participants fill out that survey, Eric and Shadi will process it next week. On the next meeting on the 8th we can discuss. 15:23:46 shadi: on 8th come up with a log on how we process the comments. Perhaps get resolution for approval on that call if we can resolve all comments. 15:24:07 jo: will send out reminder that deadline is 1st. We will parcel feedback to WG and discussion on 8th. 15:24:11 zakim, queue? 15:24:11 I see no one on the speaker queue 15:24:54 david: brilliant to not choose one particular method for scoring. Do we have some language about why one was not chosen? 15:25:36 shadi: we say they can be misleading and may not provide real measurement on the level of accessibility of a site - provide links to research symposium. 15:26:34 jo: Anything else from Shadi or Eric? 15:26:52 zakim, next item 15:26:52 agendum 4. "Review of open actions and issues. http://www.w3.org/WAI/GL/track/actions/ http://www.w3.org/WAI/GL/track/issues/" taken up [from Joshue] 15:26:58 david: Thanks to group for effort. 15:27:16 jo: Thanks to Eric and Shadi and our colleague group. 15:27:16 zakim, mute me 15:27:16 Shadi should now be muted 15:27:20 ack me 15:27:54 zakim, take up item 3 15:27:54 agendum 3. "If ready, discussion on EO proposal for 'techniques being informative' wording" taken up [from Joshue] 15:27:58 -Shadi 15:28:39 mc: summarize proposal for EOWG -- question -- we already agreed about how technologies are imperfect. We want people to see it but we don't want to repeat multiple places. We need to work out a proposal and get team consensus. 15:28:40 -EricVelleman 15:28:52 Eric Dropping off also, bye all 15:29:04 See Understanding Techniques for WCAG Success Criteria for important information about the usage of these informative techniques and how they relate to the normative WCAG 2.0 success criteria. The Applicability section explains the scope of the technique, and the presence of techniques for a specific technology does not imply that the technology can be used in all situations to 15:29:04 create content that meets WCAG 2.0. 15:29:11 mc: proposal on the technique technology pages and one page for all. Add at top of page add a paragraph that mc will paste into IRC. 15:29:13 EricVelleman has left #wai-wcag 15:29:54 zakim, queue? 15:29:54 I see no one on the speaker queue 15:30:12 ¨Important information about Techniques¨ 15:30:21 mc: Top of every technique page -- not for top of technology pages. There would be a heading and disclaimer. At the bottom of each technique page a section already has a section -- that will be removed in lieu of this at the top. 15:31:08 Publication of techniques for a specific technology does not imply that the technology can be used in all situations to create content that meets WCAG 2.0 success criteria and conformance requirements. Developers need to be aware of the limitations of specific technologies and provide content in a way that is accessible to people with disabilities. 15:31:26 mc: Technology pages such as ARIA techniques as an example - have some paragraphs, proposal is to add a new paragraph just pasted in IRC by MC. This paragraph was already approved for introduction. 15:31:27 +Q 15:31:42 mc: two changes, 1 appears in like 600 places. 15:32:29 david: are we saying that st might not be sufficient? 15:32:47 mc: we are saying that technology is universally sufficient. 15:32:57 http://www.w3.org/WAI/GL/2014/05/sc-technology-mapping.html 15:33:10 mc: Means that you can use that technology to meet that SC. 15:33:31 ack me 15:33:33 mc: document showing that no technology as ST for all SC. This paragraph is just pointing that out. 15:33:51 shadi has left #wai-wcag 15:34:13 mc: First part discussed goes at the top of each technique. 15:34:39 jo: seems like page bloat and repetition Like to see a page that has these changes so we can see it. 15:34:45 mc: Can mock something up. 15:35:16 mc: not adding repetition, we are editing repetion as there is already a section at the bottom of each technique. 15:35:49 mc: Moving section and editing it. We are altering what is already repeated. 15:35:53 q+ 15:35:58 ack bruce 15:36:36 bb: like the idea of promoting but it makes harder to get access to main content of technique. 15:37:03 q+ 15:37:09 q+ 15:37:27 jo: first review of text seems a little wordy. Perhaps it could be chunked out. 15:37:57 ack david 15:38:07 jo: Another idea to edit current language at bottom and possibly move it to top. 15:38:23 david: not proposing to change any language -- but want to be clear about what we are saying. 15:39:04 david: Do people still need to do testing with AT even if you use a ST for a SC such as 1.3.1 15:39:12 wilco: you should test with AT 15:39:33 mc: ST are AT supported but you should use your judgement in testing with AT. 15:39:47 q+ To ask for discussion about utility at having disclaimer at top of page. 15:40:14 ack bruce 15:40:14 Bruce_Bailey, you wanted to ask for discussion about utility at having disclaimer at top of page. 15:40:27 mc: always been discussion - this proposal doesn't address this. 15:40:39 zakim, agenda? 15:40:39 I see 4 items remaining on the agenda: 15:40:40 4. Review of open actions and issues. http://www.w3.org/WAI/GL/track/actions/ http://www.w3.org/WAI/GL/track/issues/ [from Joshue] 15:40:40 5. Review of comments https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses [from Joshue] 15:40:41 6. Start walking through WCAG SC for pros/cons/improvements: [from Joshue] 15:40:41 7. From June 10 Survey: https://www.w3.org/2002/09/wbs/35422/10thJune2014/ [from Joshue] 15:40:48 bb: Already discussion at bottom - it's an important. Time spent wasn't wasted. Don't like idea of having it at the top of every page. 15:41:36 - +1.703.825.aabb 15:42:59 jo: wonder if 2nd sentence should be first. 15:43:48 q+ Okay, I like it. Applicability could use one sentence introduction anyway. 15:43:48 mc: Setence with link was put first on purpose. 15:43:50 me/ don't see this: Publication of techniques for a specific technology does not imply that the technology can be used in all situations to create content that meets WCAG 2.0 success criteria and conformance requirements. Developers need to be aware of the limitations of specific technologies and provide content in a way that is accessible to people with disabilities. 15:44:05 s/Setence/Sentence 15:44:08 q+ to say Okay, I like it. Applicability could use one sentence introduction anyway. 15:44:38 ack bru 15:44:38 Bruce_Bailey, you wanted to say Okay, I like it. Applicability could use one sentence introduction anyway. 15:44:42 mc: This the link from MC is only part of the proposal - the first part. 15:44:46 bb: like it 15:46:11 zakim, agenda? 15:46:11 I see 4 items remaining on the agenda: 15:46:13 4. Review of open actions and issues. http://www.w3.org/WAI/GL/track/actions/ http://www.w3.org/WAI/GL/track/issues/ [from Joshue] 15:46:13 5. Review of comments https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses [from Joshue] 15:46:13 6. Start walking through WCAG SC for pros/cons/improvements: [from Joshue] 15:46:13 7. From June 10 Survey: https://www.w3.org/2002/09/wbs/35422/10thJune2014/ [from Joshue] 15:46:16 mc: will work on a mock-up of 2nd part for technology pages for review. 15:47:54 JA: By adding this language we hope to not give people the impression that they can use ARIA to label any control. Context is important. 15:49:29 + +1.703.825.aacc 15:50:06 JA: Thats very general, I need an example to understand this. 15:50:27 mc: posted url of techniques page. 15:52:20 david: language is not clear what your explanation of the language is 15:53:01 q? 15:53:08 david: saw previous paragraph and agreed upon language -- it's not harming it -- it's just going to make people scratch their heads. 15:53:41 mc: couple of options: move on, pick up for next publication round, 3rd option to say let's improve for this publication round -- limited time. 15:53:57 - +1.703.825.aacc 15:54:17 david: Not harming -- just raise questions -- we could address this in later rounds. 15:55:23 mc: consensus text could be more clear - we can work on it later. right now we need to work on the where to put the text. 15:56:14 jo: personal feeling is that we can bounce it back to EO if people think it need to be more clear. 15:56:38 david: we aren't saying you can rely on this technique for this specific circumstances. 15:56:55 s/personal feeling is that we can bounce it back to EO if people think it need to be more clear./Personal feeling is that the agreed text isn't that back so I don't know if we need to bounce it back to EO 15:57:03 q+ 15:57:23 ack alis 15:58:30 q- 15:58:31 Alistair: from outsiders point of view that it's clear. It would be the rare person to make the jump that a ST means that the technology as a whole is acceptable to meet at SC. 15:59:16 jo: want to move agenda. 15:59:36 mc: Is there preliminary agreement to move proposal on. 16:00:08 jo: WG consensus on wording, but not on adding it to this additional place. 16:00:17 mc: does WG approval general direction. 16:00:18 +1 16:00:24 jo: Can people agree with general move? 16:00:27 +1 16:01:05 I expressed my concerns, and am happy with discussion and explaination. 16:01:54 jo: working group members on call support the proposed places to add wording. Formal proposal processing coming soon. 16:03:02 zakim, agenda? 16:03:02 I see 4 items remaining on the agenda: 16:03:03 4. Review of open actions and issues. http://www.w3.org/WAI/GL/track/actions/ http://www.w3.org/WAI/GL/track/issues/ [from Joshue] 16:03:03 5. Review of comments https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses [from Joshue] 16:03:03 6. Start walking through WCAG SC for pros/cons/improvements: [from Joshue] 16:03:03 7. From June 10 Survey: https://www.w3.org/2002/09/wbs/35422/10thJune2014/ [from Joshue] 16:03:10 action: michaelc to take this proposal to the EO group 16:03:11 Created ACTION-263 - Take this proposal to the eo group [on Michael Cooper - due 2014-07-01]. 16:03:13 zakim, close item 16:03:13 I don't understand 'close item', Joshue 16:03:29 zakim, close this item 16:03:29 agendum 3 closed 16:03:30 I see 4 items remaining on the agenda; the next one is 16:03:30 4. Review of open actions and issues. http://www.w3.org/WAI/GL/track/actions/ http://www.w3.org/WAI/GL/track/issues/ [from Joshue] 16:03:34 zakim, take up item 7 16:03:34 agendum 7. "From June 10 Survey: https://www.w3.org/2002/09/wbs/35422/10thJune2014/" taken up [from Joshue] 16:04:19 https://www.w3.org/2002/09/wbs/35422/10thJune2014/results#xtechsc2 16:04:20 jo: related to technique from last week kindly submitted by Alistair Alistair is on call to talk about item #3 on survey from June 10. 16:04:45 http://www.w3.org/WAI/GL/wiki/Creating_a_conforming_alternate_version_for_a_web_page_designed_with_progressive_enhancement 16:05:54 jo: AWK had made some changes to description. Has been some discussion w/ RWD and progressive enhancement. Two camps, RWD is just CSS, others say RWD can use JS. 16:06:42 alistair: Changed technique - removed all reference to RWD to make it clearly about progressive enhancement. Incorporated AWK text. 16:07:00 +James_Nurthen 16:07:05 alistair: added a description from Wikipedia about progressive enhancement. 16:07:46 alistair: want to claim conformance based on base site -- there are libraries to do this thing. this about how to make a claim based on this technique. 16:09:18 Alistair: so many tie ups between progressive enhancement and RWD. People are using PE to drive RWD. Use something like modernizr and then use CSS in much more stable environment. 16:09:34 +q 16:09:36 alistair: Could say RWD designed with progressive enhancement. 16:09:46 ack me 16:11:09 responsive web pages designed with progressive enhancement 16:11:15 jo: If this does straddle both different camps -- that's fine with me. Does anyone have any comments on Alistair's changes? 16:11:18 zakim, queue? 16:11:18 I see no one on the speaker queue 16:11:38 david: not sure about lowest common denominator for all devices accessing the content? 16:12:25 alistair: Use pure underlying HTML code as base. 16:13:32 alistair: allow people get back to pure version -- PE will enhance a page without asking people. 16:14:10 jamesn has joined #wai-wcag 16:14:18 jnurthen has joined #wai-wcag 16:14:23 zakim, queue? 16:14:24 I see no one on the speaker queue 16:14:50 james: sounds like we are sending accessibility users back to basic page. 16:14:55 zakim, mute me 16:14:55 Joshue should now be muted 16:15:54 alistair: reason to allow people to claim conformance on something rather than all versions that can't be tested. Use WCAG infrastructure to them claim conformance to all versions. 16:16:10 ack me 16:16:18 alistair: Allow people to claim conformance based on current guidelines. 16:16:43 jo: Text pre-enahnced conforming alternate version is wordy 16:17:27 james: Have hard time with technique and path that is already there in WCAG. 16:18:29 david: text versions go back to 99 -- you have all functionality at basic level -- enhanced from there. Don't want to go with lowest common denominator language. 16:19:04 jo: start with functioning page that does 80 to 90 of page's bells and whistles. 16:19:06 This is a line in the descfription i have a big problem with "One solution to this challenge is to select the pre-enhanced version of the web page (e.g. the DOM state created solely from the HTML in the source code in the absence of support for scripts, styles or non-HTML plugins) as the "fully conformant version". With regard to support, it presents the lowest common denominator version for all devices accessing the content." 16:19:41 alistair: Language of "version that can be broadly used" may be better than lowest common denominstor. 16:20:48 Alistair: very specific situation for people creating pages where it can be used in a multitude of environments -- have to claim conformance - you should claim on the base version. 16:21:30 alistair: enhanced version should be made as accessibility as possible. 16:22:50 jo: survey for call on 8th. 16:23:10 RESOLUTION: Leave open, Alistair to incorporate feedback. 16:23:21 Alistair: thanks for letting me talk about it. 16:23:22 zakim, agenda? 16:23:22 I see 4 items remaining on the agenda: 16:23:23 4. Review of open actions and issues. http://www.w3.org/WAI/GL/track/actions/ http://www.w3.org/WAI/GL/track/issues/ [from Joshue] 16:23:23 5. Review of comments https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses [from Joshue] 16:23:23 6. Start walking through WCAG SC for pros/cons/improvements: [from Joshue] 16:23:23 7. From June 10 Survey: https://www.w3.org/2002/09/wbs/35422/10thJune2014/ [from Joshue] 16:23:42 zakim, close this item 16:23:42 agendum 7 closed 16:23:43 I see 3 items remaining on the agenda; the next one is 16:23:43 4. Review of open actions and issues. http://www.w3.org/WAI/GL/track/actions/ http://www.w3.org/WAI/GL/track/issues/ [from Joshue] 16:23:50 zakim, take up item 5 16:23:50 agendum 5. "Review of comments https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses" taken up [from Joshue] 16:24:24 james: No concept that alternatives need to be of same efficiency as performing the task. Could take you 20 times as long. 16:24:29 q+ 16:24:42 james: might not meet courts or Section 508 equivalence. 16:24:50 Taking 20 times longer is not equivalent functionality 16:25:09 ack bruce 16:25:51 bb: 20 times is not equivalent functionality. This is huge issue with Department of Transportation for WCAG AA for website they have authority over -- they did talk about alternative conforming versions. 16:26:15 https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses 16:26:16 jo: Some open actions and issues that we will front load into calls. We had a full agenda today so we didn't get into them. 16:26:26 http://www.w3.org/2006/02/lc-comments-tracker/35422/WD-WCAG20-TECHS-20140107/2889 16:26:32 http://www.w3.org/2006/02/lc-comments-tracker/35422/WD-WCAG20-TECHS-20140107/2889 16:26:47 jo: We have some comments needing responses. James has one. 2nd one needs an owner. Does anyone want to draw up a response? 16:27:09 https://www.w3.org/2006/02/lc-comments-tracker/35422/NOTE-WCAG20-TECHS-20130905/2871 16:27:19 david: will take 2871 16:27:36 zakim, agenda? 16:27:36 I see 3 items remaining on the agenda: 16:27:38 4. Review of open actions and issues. http://www.w3.org/WAI/GL/track/actions/ http://www.w3.org/WAI/GL/track/issues/ [from Joshue] 16:27:38 5. Review of comments https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses [from Joshue] 16:27:38 6. Start walking through WCAG SC for pros/cons/improvements: [from Joshue] 16:27:45 zakim, next item 16:27:45 agendum 4. "Review of open actions and issues. http://www.w3.org/WAI/GL/track/actions/ http://www.w3.org/WAI/GL/track/issues/" taken up [from Joshue] 16:27:51 zakim, next item 16:27:51 agendum 4 was just opened, Joshue 16:27:52 zakim, next item 16:27:52 agendum 4 was just opened, Joshue 16:28:15 zakim, take up item 6 16:28:15 agendum 6. "Start walking through WCAG SC for pros/cons/improvements:" taken up [from Joshue] 16:28:27 jo: walk through of SC. Please answer survey if you have not already. Review the document proposal guide. 16:28:48 jo: Like institutional memory exercise. 16:29:10 rrsagent, make minute 16:29:10 I'm logging. I don't understand 'make minute', Joshue. Try /msg RRSAgent help 16:29:17 zakim, list attendees 16:29:17 As of this point the attendees have been Joshue, Shadi, alistair, Wilco, Kenny, Bruce_Bailey, Michael_Cooper, +1.703.637.aaaa, jon_avila, Marc_Johlic, David_MacDonald, 16:29:20 ... EricVelleman, +1.703.825.aabb, +1.703.825.aacc, James_Nurthen 16:29:34 rrsagent, draft minutes 16:29:34 I have made the request to generate http://www.w3.org/2014/06/24-wai-wcag-minutes.html Joshue 16:29:34 -Wilco 16:29:42 -James_Nurthen 16:29:43 -Michael_Cooper 16:29:45 -alistair 16:29:47 -Bruce_Bailey 16:29:47 -Joshue 16:29:47 -jon_avila 16:29:51 -David_MacDonald 16:29:54 -Marc_Johlic 16:30:08 -Kenny 16:30:08 zakim, bye 16:30:08 Zakim has left #wai-wcag 16:30:10 WAI_WCAG()11:00AM has ended 16:30:10 Attendees were Joshue, Shadi, alistair, Wilco, Kenny, Bruce_Bailey, Michael_Cooper, +1.703.637.aaaa, jon_avila, Marc_Johlic, David_MacDonald, EricVelleman, +1.703.825.aabb, 16:30:10 ... +1.703.825.aacc, James_Nurthen 17:26:09 Joshue has joined #wai-wcag 19:04:07 jamesn has joined #wai-wcag 19:34:52 Joshue has joined #wai-wcag 20:15:30 Joshue has joined #wai-wcag 20:43:51 Joshue has joined #wai-wcag