13:57:18 RRSAgent has joined #eval 13:57:18 logging to http://www.w3.org/2013/09/05-eval-irc 13:57:20 RRSAgent, make logs world 13:57:20 Zakim has joined #eval 13:57:22 Zakim, this will be 3825 13:57:22 ok, trackbot; I see WAI_ERTWG(Eval TF)10:00AM scheduled to start in 3 minutes 13:57:23 Meeting: WCAG 2.0 Evaluation Methodology Task Force Teleconference 13:57:23 Date: 05 September 2013 13:58:15 Kathy has joined #eval 13:58:45 zakim, this is eval 13:58:45 ok, shadi; that matches WAI_ERTWG(Eval TF)10:00AM 13:58:54 + +31.30.239.aaaa 13:58:55 zakim, who is on the phone? 13:58:55 On the phone I see Mike, Liz, Shadi, +31.30.239.aaaa 13:58:59 + +1.978.261.aabb 13:59:12 zakim aabb is me 13:59:12 +MartijnHoutepen 13:59:16 Zakim, aaaa is me 13:59:16 +ericvelleman; got it 13:59:25 zakim, aabb is Kathy 13:59:25 +Kathy; got it 14:00:04 zakim, mute me 14:00:04 Kathy should now be muted 14:00:38 korn has joined #eval 14:01:17 ack me 14:01:29 zakim, mute me 14:01:29 Kathy should now be muted 14:01:41 +Detlev 14:01:43 zakim, who is on the phone? 14:01:43 On the phone I see Mike, Liz, Shadi, ericvelleman, Kathy (muted), MartijnHoutepen, Detlev 14:02:29 zakim, mute me 14:02:29 Detlev should now be muted 14:03:13 scribe: shadi 14:03:14 Zakim, mute me 14:03:14 MartijnHoutepen should now be muted 14:03:40 + +1.650.506.aacc 14:03:42 Eric: welcome to the call 14:03:50 ...tried to incorporate all changes into the recent Editor Draft 14:04:03 Zakim, aacc has Peter_Korn 14:04:03 +Peter_Korn; got it 14:04:43 scribe: Peter 14:04:43 scribenick: korn 14:05:42 Sarah_Swierenga has joined #eval 14:05:46 http://www.w3.org/WAI/ER/methodology/ 14:06:01 agenda? 14:06:14 topic: new editor draft 14:06:20 +Sarah 14:06:26 http://www.w3.org/WAI/ER/methodology/ 14:06:44 http://www.w3.org/WAI/ER/conformance/comments-20130226 14:08:21 Eric: key topics to discuss, likely on the mailing list in the coming week... 14:08:36 Eric: New conformance section, changes in 1b, how to choose a sample 14:09:03 Eric: in document, noted where the change comes from (e.g. disposition of comments), why the change, etc. 14:09:04 +Tim_Boland 14:10:54 topic: Discussion start about new section Conformance in the context of WCAG-EM 14:11:04 http://www.w3.org/WAI/ER/conformance/ED-methodology-20130903#conformanceintro 14:11:11 Vivienne has joined #eval 14:11:16 q 14:11:17 q+ 14:12:11 q+ 14:12:12 +[IPcaller] 14:12:17 zakim, IPcaller is me 14:12:17 +Vivienne; got it 14:13:09 q? 14:14:22 q- 14:14:46 Shadi: issue with the title of the section... "Conformance in the context of WCAG-EM" 14:15:17 zakim, mute me 14:15:17 Vivienne should now be muted 14:15:26 -Mike 14:15:26 Shadi: may need to tweek the wording of the title. Also comment AC81 (from Peter) and the use of the word "statements" 14:16:01 Shadi: also should be clear we aren't proposing a new/different conformance model here. 14:16:05 +Mike 14:18:06 Why not "Step 5.b: Provide an Accessibility Evaluation Statement"? 14:18:22 q- 14:19:47 Fredrick: worried about using the word "conformance" itself here. Could cause confusion. 14:19:48 q+ 14:20:11 Eric: uses the term "Accessibility Evaluation Conformance Statement", to try to be distinct. 14:20:23 q+ 14:21:09 Fredrick: Prefer to not use "conformcne" here; so "Accessibility Evaluation Statement" 14:22:28 Peter (from earlier in the thread): purpose / goal of this new section is to make clear that WCAG conformance claims cannot be made, by their definition, to our output, as our output is intentionally a sampling. 14:22:39 Sorry i was late in from a meeting . Can someone fill me in on what section we're discussing? 14:23:03 http://www.w3.org/WAI/ER/conformance/ED-methodology-20130903#conformanceintro 14:23:11 Peter (still from earlier): therefore we want to lay out the issues in this section, and set forth the idea that the output of WCAG-EM is a statement addressing the extent to which conformance was found. 14:23:48 q? 14:24:48 Shadi: likes what Tim is saying - avoiding the words "conformance" and "conformance claim" as much as possible. 14:25:26 Shadi: Q (to Peter perhaps): is it that we are trying to define the scope of WCAG-EM here? 14:26:14 Shadi: thinks that the second paragraph is more important; maybe flip the order. Seems we are more describing the limitations & scope, rather than any conformance requirements. Hence the disconnect of the title from the contents of the section. 14:26:18 ack s 14:26:25 q+ 14:26:28 scribe: shadi 14:27:13 Peter: appreciate to try to avoid conformance but important to talk about it when we introduce the evaluation statements or such 14:27:20 q- 14:27:43 ...because conforms is used inherently and needs to be addressed straight on 14:28:07 ...need to address the many ways people will use this 14:28:51 ...agree that title could be improved 14:29:05 ...maybe "output from WCAG-EM" 14:29:15 scribe: korn 14:29:21 ...but critical to have description of these aspects of the document 14:29:42 Eric: suggests we suspend further discussion of this section here, and shift it to the mailing list. 14:30:05 topic: Discussion start about changes to Step 1.b 14:30:24 http://www.w3.org/WAI/ER/conformance/ED-methodology-20130903#step1b 14:30:56 Define the goal of the evaluation 14:30:58 http://www.w3.org/TR/WCAG-EM/#step1b 14:31:47 Eric: changing 1b to be about "additional requirments", beyond what is set forth in WCAG-EM 14:32:13 q+ 14:32:52 q? 14:32:58 q+ 14:33:03 scribe: shadi 14:33:43 Peter: might be good to list examples of some of the things that are additional 14:33:46 ...not sure if the term "requirements" is precise 14:34:00 q- 14:34:05 ack me 14:34:05 ...maybe better "aspects" as they are more content than process aspects 14:34:09 scribe: korn 14:34:39 Detlev: might this also be a place to define an eval that is more limited (e.g. to explicitly NOT evaluate against some SCs) 14:34:56 Detlev: or to evaluation portions of a page (since WCAG applies to entire pages) 14:35:08 -Tim_Boland 14:35:12 q? 14:35:13 Detlev: thus you might skip "Page title", etc. since it wouldn't apply to a portion of a page. 14:35:29 +1 to this from Peter 14:35:41 q+ 14:35:45 ack me 14:36:39 Shadi: paraphrasing Detlev: if you have a bunch of templates / code objects / pieces of content, and you want to evaluate those on their own, and make an eval statement about those, you would want to set that forth here in step 1b. 14:37:34 Eric: this would be the place to put such a thing, though maybe a bit different of an "addition" (being a subtraction) than we had at first throught. 14:37:42 /throught/thought 14:37:55 q+ 14:38:16 Peter: perhaps "define any modifications to the evaluation process" 14:38:33 Peter: then in examples, we might have the one Detlev set forth 14:38:35 q+ 14:38:38 q- 14:38:41 ack me 14:39:05 Shadi: need to look back at the section "Using this methodology" and "scope" and "applicability". Those sections also list types of websites. 14:39:27 Shadi: we encourage the use of this methodology in different situations, but the primary focus is the website as a whole, as presented to user. 14:40:05 Shadi: lots of disucssion about incremental eval, development eval, regression eval. But... adding this (only) in step 1b may break what we said earlier. Perhaps it should (instead) be said earlier? 14:40:13 Zakim, mute me 14:40:13 Detlev should now be muted 14:40:14 Eric: pausing this disucssion here, to shift it to mailing list. 14:40:43 q+ 14:40:57 Eric: Primary observation from here is from Detlev - focusing eval to a subset of a page 14:42:13 Shadi: in the spirit of "addressing things head on", it might really be good under "scope of applicability" to have a section saying "you can still apply this guidance in other situations" and list them (such as Detlev's "part of a page", also "during development", etc.) 14:42:17 +1 14:42:27 topic: Discussion start about changes to Step 3: Select a Representative Sample 14:43:12 Eric: took outcome of earlier discussion (even from last year) and put it here. Not sure if it should be here, or in different form... 14:43:34 Eric: added "factors related to likelihood of a sample being representative" 14:43:53 q+ 14:44:16 ack me 14:45:31 Peter: likes section, but remains concerned with the lack of statistic rigor guidance here for how to determine the "likelihood of a sample being representative" 14:48:06 Peter: suggests we might again do more website testing under WCAG-EM with a focus on how similar/different the results are, to inform how much further guidance may be needed here for "representative sample" and "confidence" 14:48:34 Eric: concerned that there are so many ways in literature for doing sampling, we don't want to pick one above others 14:48:47 Eric: +1 to doing another test run again 14:49:14 topic: Discussion start about changes to Step 3.d: Include Complete Processes in the Sample 14:49:29 ack me 14:49:35 q- 14:50:08 q+ 14:50:43 Detlev: evaluators will need some guidance for following processes (not just "put in URL of a page"). Menus, forms, lightboxes, etc. 14:51:11 -Sarah 14:51:12 Detlev: only way to include such generated pages is to refer to the "base page" and how to get to the "generated page" 14:51:51 Detlev: sets forth doing it the "default" way, and then also suggests looking at some variants (e.g. input error) 14:52:32 Detlev: an obvious can of worms for very complex sites - all the potential complexity, and need to draw the line somewhere, make a judgement call as to how far to go. 14:53:20 Eric: this is one place in the methodology where we really take people by the hand. Originally just had a little text here; now we are doing much more leading people through "how you do this". Perhaps we should look at doing that amount of leading in other palces. 14:53:25 /palces/places 14:53:40 Detlev: risk is that we are too descriptive - too focused on a particular type of website. Need to think about that too. 14:54:33 Peter: consider "at least" in number 2; make clear that going through the default branch is a minimum. 14:54:50 Eric: discussion about the prescriptive-ness of this... anyone think this is too much? That we should do more of that level elsewhere? 14:54:53 Q+ 14:55:19 scribe: shadi 14:55:51 Peter: seems like the right direction but maybe not the right level of prescriptiveness 14:55:57 q+ 14:55:58 q+ 14:56:02 q- 14:56:09 scribe: korn 14:56:11 ack me 14:56:13 ack me 14:56:13 ...a bit more elsewhere may be helpfull too but need to check 14:56:48 q+ 14:56:51 zakim, mute me 14:56:51 Kathy should now be muted 14:56:53 Kathy: good to have this level of detail in this section, but have to be careful. If you lead too much by the hand, it may not fit certain circumstances. So agrees - evaluate level of prescriptive-ness on a section-by-section basis 14:56:55 q? 14:57:23 Vivienne: likes level of detail here. Finds with clients that guidance around complete processes is necessary. 14:57:48 Vivienne: thinks we will find other areas where more point-by-point instructions will be very helpful. 14:57:57 q- 14:58:03 zakim, mute me 14:58:03 Vivienne should now be muted 14:58:31 Mike: thinks we keep running into issue of how to define a representative sample. What is sufficient... A little reluctant to make things too detailed, but this seems like a good place for this level of detail. 14:58:52 Mike: maybe have examples here as well. 14:59:41 Eric: (summarizing) not hearing people saying they don't want this level of detail; should discuss on mailnig list whether we want this much, and where else in document we want this level of detail (or at least more detail than is there presently) 15:00:34 Eric: will start discussions of each of these on the mailing list (after Dutch dinner), and hopes we continue discussions there. 15:00:59 Eric: next week, hopes to have a survey so we can close down some of these discussions 15:01:05 topic: Other issues 15:01:11 Bravo! 15:01:12 Shadi: really great work Eric 15:01:32 bye 15:01:37 Ciao 15:01:43 good night all 15:01:45 bye 15:01:46 bye! 15:01:49 -Mike 15:01:54 -Kathy 15:01:56 -Detlev 15:02:02 -Vivienne 15:02:05 -ericvelleman 15:02:06 -Shadi 15:02:08 -MartijnHoutepen 15:02:10 -Liz 15:02:13 ericvelleman has left #eval 15:03:55 regrets: Moe 15:04:09 trackbot, end meeting 15:04:09 Zakim, list attendees 15:04:09 As of this point the attendees have been Mike, Liz, Shadi, +31.30.239.aaaa, +1.978.261.aabb, MartijnHoutepen, ericvelleman, Kathy, Detlev, Peter_Korn, Sarah, Tim_Boland, Vivienne 15:04:17 RRSAgent, please draft minutes 15:04:17 I have made the request to generate http://www.w3.org/2013/09/05-eval-minutes.html trackbot 15:04:18 RRSAgent, bye 15:04:18 I see no action items