14:04:35 RRSAgent has joined #eval 14:04:36 logging to http://www.w3.org/2013/09/19-eval-irc 14:04:37 RRSAgent, make logs world 14:04:38 Zakim has joined #eval 14:04:40 Zakim, this will be 3825 14:04:40 ok, trackbot; I see WAI_ERTWG(Eval TF)10:00AM scheduled to start 4 minutes ago 14:04:41 Meeting: WCAG 2.0 Evaluation Methodology Task Force Teleconference 14:04:41 Date: 19 September 2013 14:05:36 scribe: korn 14:05:40 shadi has joined #eval 14:06:26 Topic: Welcome 14:06:59 Sarah_Swierenga has joined #eval 14:07:10 Zakim, mute me 14:07:10 sorry, MartijnHoutepen, I don't know what conference this is 14:07:18 Zakim, this is 3925 14:07:20 sorry, MartijnHoutepen, I do not see a conference named '3925' in progress or scheduled at this time 14:07:20 Topic: Walkthrough smaller changes in editor draft 14:07:22 Zakim, this is 3825 14:07:22 ok, MartijnHoutepen; that matches WAI_ERTWG(Eval TF)10:00AM 14:07:22 +[IPcaller.a] 14:07:29 zakim, IPcaller.a is me 14:07:29 +Vivienne; got it 14:07:30 zakim, who is on the phone? 14:07:31 On the phone I see Kathy, +31.30.239.aaaa, +1.313.322.aabb, Peter_Korn, +31.30.239.aacc, [IPcaller], Vivienne 14:07:32 + +1.517.432.aadd 14:07:58 Zakim, aacc is me 14:07:58 +MartijnHoutepen; got it 14:08:00 Zakim, aaaa is me 14:08:00 +ericvelleman; got it 14:08:11 aadd is me 14:08:22 zakim, vivienne is shadi 14:08:22 zakim, ipcaller is Vivienne 14:08:22 +shadi; got it 14:08:23 +Vivienne; got it 14:08:26 Zakim, aadd is Sarah_Swierenga 14:08:26 +Sarah_Swierenga; got it 14:08:26 zakim, who is on the phone? 14:08:27 On the phone I see Kathy, ericvelleman, +1.313.322.aabb, Peter_Korn, MartijnHoutepen, Vivienne, shadi, Sarah_Swierenga 14:08:57 Zakim, aabb is Mike_Elledge 14:08:57 +Mike_Elledge; got it 14:09:05 Zakim, mute me 14:09:05 MartijnHoutepen should now be muted 14:10:17 http://www.w3.org/WAI/ER/conformance/ED-methodology-20130903 14:10:20 + +1.617.480.aaee 14:10:22 agenda? 14:10:40 zakim, mute me 14:10:40 Vivienne should now be muted 14:11:47 Eric working on a new editor's draft, so woud like to skip over topics we discussed earlier. 14:12:48 q? 14:13:36 q+ 14:13:49 zakim, ack me 14:13:49 unmuting Vivienne 14:13:50 I see no one on the speaker queue 14:15:50 Vivienne - suggest we say "this methodology describes the min. req. for one approach to evaluating a webiste" 14:16:06 q+ 14:17:33 peter: keep in mind that every part of this note is advisory 14:17:51 ...but vivienne's wording highlights this well 14:18:00 q+ 14:18:03 ack k 14:18:57 Mike: ~+1 to Peter. EvalTF is a pretty "weighty" document. Anything we can do to help folks understand that this is simply 1 way of doing this. Also keep the document streamlined. 14:19:08 q+ 14:19:12 ack M 14:19:32 + 14:20:00 peter: could try progressive disclosure approach 14:20:16 +1 14:20:22 ...first describe methodology at a higher level 14:20:22 ...then drill deeper into specifics later on 14:20:51 ...not sure what specific changes are needed for this 14:21:07 ack k 14:21:21 Kathy - a verbal +1 as well. 14:22:10 Kathy: adding a summary section at the top might be an approach to this. 14:22:16 q+ 14:22:27 +1 14:22:39 Eric: another approach as this is throughout the docment is to put more into appendicies. 14:22:46 Kathy: does seem overwhelming. 14:23:33 q+ 14:23:45 ack k 14:24:04 Peter suggested expand/collapse widgets as an option - see WCAG2ICT doc. 14:24:22 http://www.w3.org/WAI/ACT/deliverables#eval_guide 14:24:27 Peter: take a look at http://www.w3.org/WAI/GL/2013/WD-wcag2ict-20130905/accordion 14:25:27 Shadi: many folks we expect to use this document won't be the typical readers of a W3C spec. 14:26:37 q+ 14:27:07 Bim has joined #eval 14:27:22 ack me 14:27:58 Shadi: W3C / WAI has funding to work on interactive guides for evaluators. Could include WCAG-EM, as well as other educational materials for evaluation 14:28:36 Mike: discussion reminds him of how handy the old WCAG 1.0 "wallet card" was. 14:28:56 http://www.w3.org/WAI/WCAG20/glance/ 14:29:08 called WCAG 2 at a Glance 14:30:41 http://www.w3.org/WAI/ER/conformance/ED-methodology-20130903#step3f 14:30:42 Topic: (sub-topic) Step 3F 14:31:19 q+ 14:31:23 q+ 14:31:50 Eric: discuss optional/non-optionality of this step 14:32:48 q+ 14:32:54 ack M 14:33:29 q+ 14:33:50 ack k 14:34:59 Peter: rather than the optional/non-optional-ality of this section, we should use this section to CAPTURE the fact that redundant pages were found. E.g. a site with 3 unique pages and 500 all of the same template is a site on which the evaluation will have a high degree of confidence - what is found on one/two of the 500 would likely apply to all. 14:35:12 ... so we should retain the knowledge of the reduncancy, not just toss it out. 14:35:27 q- 14:35:43 Kathy: agrees we shouldn't take this out; reasons to have redundancy in the sample. Esp. if the site has different developers, etc. 14:35:43 q+ 14:35:57 MoeKraft has joined #eval 14:36:00 Kathy: so there are reasons to have redundancy in sample. 14:36:36 Sarah: reading the exact language, and what we are saying in 3f - if you happen to pick the same page as you did earlier, you would then select a different one (don't evaluate the precisely same page twice) 14:36:42 + +1.978.899.aaff 14:36:43 - +1.617.480.aaee 14:36:52 ... "... thta are identical with other web pages in the sample..." 14:36:58 /thta/that 14:36:59 zakim,aaff is Moe 14:36:59 +Moe; got it 14:37:20 Eric: this discussion illustrates that we need to work on the text, as people on the call are reading the text differently. 14:37:21 zakim, aaee was Moe 14:37:21 I don't understand 'aaee was Moe', MoeKraft 14:37:47 Eric: thinks we all agree if we mean the "same page" we should take it out. 14:38:47 ack me 14:39:24 Peter: interpretation of "... that are identical with other web pages in the sample..." as meaning the precisely same page is not consistent with "Filter the sample to eliminate excessive redundancies." (as "excessive" suggests that sometimes looking at the same/identical page multiple times is OK, so long as you aren't doing it "excessively" 14:39:27 q- 14:39:49 Eric: we all agree that taking identical pages out is OK? 14:39:51 q+ 14:39:59 ack S 14:41:00 Zakim, mute me 14:41:00 MartijnHoutepen should now be muted 14:42:02 Peter: put "uniqueness" of items in the sample into step 3.e. Then 3.f can be a discussion about "appearing to be similar", and about hetero-/homo-genaity 14:42:15 +1 14:42:22 Yes, I agree with the other callers about this 14:42:27 Eric: thought's on Peter's suggestion? 14:42:35 +1 14:42:42 +1 14:43:19 Topic: (sub-topic) Section 5 introduction 14:43:22 http://www.w3.org/WAI/ER/conformance/ED-methodology-20130903#step5 14:47:15 Topic: (sub-topic) move now to discuss performance score 14:47:49 q+ 14:48:18 q+ 14:49:22 peter: if we don't have a common way to score, there can't be comparability 14:49:42 ack k 14:49:47 q+ 14:49:47 ...but again don't think should have performance score whatsoever 14:50:02 q- 14:50:46 Kathy: agrees with Peter - so much that can go into a score (not just WCAG 2.0 compliance, but severity of issue, impact on various different PwDs, needs) it get so very difficult. 14:50:57 http://jimthatcher.com/favelets/ 14:51:22 q+ 14:51:25 ... maybe look at what Knowbility has done for their scoring, also Jim Thatcher's work. So may want to lok at that, lots of different ideas there. 14:51:37 zakim, ack me 14:51:37 I see shadi on the speaker queue 14:52:09 Vivienne: understand's what Peter is saying, his concerns. But it's not just because people want it; in some situations it is required (for when you are comparing things). 14:52:10 q+ 14:53:10 ... so need some way of recording things in a stastical manner. How to compare the same website over time. So has no problem with saying "scoring isn't part of the scope", but still providing some suggestions on this. Because the question is going to get raised, etc. 14:53:48 ... we shouldn't just bury our heads in the sand and say "don't do it". We need to deal with the issue. 14:54:03 Eric: we should find some way to give a score, even if we provide caveats around it. 14:54:24 q+ 14:54:29 ack me 14:54:38 zakim, mute me 14:54:38 Vivienne should now be muted 14:54:55 Shadi: is going to be somewhat contradictory... (is really torn). Agrees with lots of the arguments raised. There are uses cases for scoring, use cases against. 14:55:21 ... we previous agreed that we wanted to provide scoring for comparing their own websites over time, not to compare different websites with each other. 14:55:54 ... so thinks it might be good that we don't provide a single approach, but rather several they can use. We are far away from comparing different sites effectively. 14:56:33 ... concern is that people use this to compare against each other, in which case maybe we should dig our heads into the sand. 14:56:36 q? 14:58:31 We do not make it a step but make it a section about Performance scores, and say we will not make it. They can be helpful but are dubious. Then have appendix about resources of performance scores… Not part of WCAG-EM to make performance score. 14:59:09 -Kathy 14:59:22 +1 14:59:27 Peter: perhaps a way forward: (a) we don't make this a formal step, (b) we talk about all of the challenges in performance scores - that they are NOT valid for inter-site comparisons but can be helpful for giving a quick look at improvements/regressions in a single site, and (c) have an appendix with resources for folks that want to use them ONLY for site improvement evaluation. 14:59:33 sounds like it might work - depends on the wording 14:59:39 +1 15:00:06 Eric: will put this onto a survey; thinks this may be the best way forward. 15:00:09 q? 15:00:13 ack me 15:01:15 Moe: have no problem with this as a separate section, but want to echo some of the thoughts/ideas discussed. May be that you have a single evaluator looking at multiple websites, using the same scoring methods to compare them (may also be for the same commissioner). 15:01:37 ... so comparing multiple websites could be OK. But no problem in a separte section. 15:02:03 Topic: Further steps and agenda 15:02:28 Eric: working on a survey for final changes on the doc, & new editor draft. You will first get the survey, then next week we can discuss outcomes from that survey. 15:03:35 bye everyone! 15:03:39 -Sarah_Swierenga 15:03:39 ciao! 15:03:43 -MartijnHoutepen 15:03:43 ericvelleman has left #eval 15:03:44 -Moe 15:03:45 good night all 15:03:46 -Peter_Korn 15:03:46 -shadi 15:03:46 -Mike_Elledge 15:03:50 -ericvelleman 15:03:52 -Vivienne 15:03:54 WAI_ERTWG(Eval TF)10:00AM has ended 15:03:54 Attendees were Kathy, +31.30.239.aaaa, +1.313.322.aabb, Peter_Korn, +31.30.239.aacc, +1.517.432.aadd, MartijnHoutepen, ericvelleman, shadi, Vivienne, Sarah_Swierenga, Mike_Elledge, 15:03:54 ... +1.617.480.aaee, +1.978.899.aaff, Moe 15:04:19 trackbot, end meeting 15:04:19 Zakim, list attendees 15:04:19 sorry, trackbot, I don't know what conference this is 15:04:27 RRSAgent, please draft minutes 15:04:27 I have made the request to generate http://www.w3.org/2013/09/19-eval-minutes.html trackbot 15:04:28 RRSAgent, bye 15:04:28 I see no action items