13:58:06 RRSAgent has joined #eval 13:58:06 logging to http://www.w3.org/2013/06/06-eval-irc 13:58:08 RRSAgent, make logs world 13:58:10 Zakim, this will be 3825 13:58:10 ok, trackbot; I see WAI_ERTWG(Eval TF)10:00AM scheduled to start in 2 minutes 13:58:11 Meeting: WCAG 2.0 Evaluation Methodology Task Force Teleconference 13:58:11 Date: 06 June 2013 13:59:21 ericvelleman has joined #eval 13:59:31 Kathy has joined #eval 14:00:20 WAI_ERTWG(Eval TF)10:00AM has now started 14:00:29 + +31.30.239.aaaa 14:00:36 Zakim, aaaa is me 14:00:36 +MartijnHoutepen; got it 14:00:44 + +31.30.239.aabb 14:00:46 +Kathy 14:00:58 Zakim, aabb is me 14:00:58 +ericvelleman; got it 14:01:51 +Peter_Korn 14:03:10 Zakim, mute me 14:03:10 MartijnHoutepen should now be muted 14:05:10 scribe: MartijnHoutepen 14:05:17 yes 14:05:34 MoeKraft has joined #eval 14:05:41 topic: Disposition of comments and editor draft 14:06:01 EV: editor draft is in progress, probably before next meeting 14:06:03 +MoeKraft 14:06:39 EV: we will discuss this in the next telcon 14:06:49 topic: testrun 2 14:07:12 EV: 4 people responded 14:07:13 14:07:14 ack me 14:07:18 korn has joined #eval 14:07:32 richard has joined #eval 14:07:57 http://lists.w3.org/Archives/Public/public-wai-evaltf/2013Jun/0000.html 14:08:02 https://www.w3.org/2002/09/wbs/48225/testrun2/results 14:08:07 Martijn presents the summary of website#2 14:08:53 +matthias_samwald 14:10:09 richard has joined #eval 14:10:37 Detlev has joined #eval 14:10:45 -matthias_samwald 14:11:02 +Peter_Korn.a 14:11:05 +[IPcaller] 14:11:07 -Peter_Korn 14:11:28 q+ 14:12:00 Just peeking a bit over IRC today 14:12:10 zakim, IPcaller is Richard 14:12:10 +Richard; got it 14:12:31 q+ 14:13:05 PK: regular expressions maybe not needed, too formal 14:13:38 MH: agrees 14:13:43 Korn: It is confusing to talk about regular expressions. Using this as an example of formalizations. 14:14:09 q? 14:14:10 We don't need the full glory of regular expressions 14:14:14 q- 14:14:22 Korn: Wouldn't say regular expressions aren't needed. Just don't need a whole lot of them. 14:14:51 +Peter_Korn.aa 14:14:53 MK: we don't require them, but suggest re 14:15:00 -Peter_Korn.a 14:15:24 Moe: Regular expressions are not required but formalizations are recommended to identify the web pages in scope 14:16:12 Martijn: One thing to mention about Step 1, when we have a big website such as sub-domains you would need more contact with evaluation commissioner to define scope of evaluation. 14:16:31 Martijn: Since webiste is so big it is hard to know when to stop. Need input from commissioner. 14:17:49 MoeKraft: Martijn: Step 2, one evaluator listed common pages, others listed templates and how used. One evaluator looked at functionality, another looked a visual appearance, other evaluation looked at structure and sections of web pages. 14:18:13 MoeKraft: Martijn: not sure if guidance is clear since we have different results 14:18:37 q+ 14:18:49 Kathy: The comment regarding that the website is too big and need more help from commissioner, maybe we need to have guidance to break site into smaller pieces. 14:18:59 Kathy: Maybe have guidance on how to define scope of review. 14:19:07 q? 14:21:58 Korn: I think the problem is that exactly the problem we are tackling in the first place, We indicate that you have to sample. 14:23:29 MoeKraft: We did test this site and worked closely with the commissioner on defining the scope 14:23:53 Kathy: Maybe we need more guidance on communicating with the commissioner for example providing a set of questions to ask. 14:24:05 q? 14:24:09 ack me q- moe 14:24:13 q- moe 14:24:15 ack me 14:25:05 Martijn: Sometimes the scope of the website is simple and you do not need to interact with commissioner but sometimes the website is so big that we do need to involve the commissioner and I think providing more guidance on this would be helpful. 14:25:17 Martijn: For instance asking questions of the commissioner. 14:25:37 Note: Involvement of the website owner and/or website developer can be useful to help identify common web pages, functionality, technologies, and other aspects of the implementation that makes the evaluation procedure more efficient and effective. However, the evaluator is responsible for an objective and thorough evaluation. 14:26:28 help 14:27:00 Note: Involvement of the website owner and/or website developer (in addition to the evaluation commissioner) is not required but often helps identify use cases, functionality, and other aspects of the implementation that makes the evaluation procedure more efficient and effective. However, the evaluator is responsible for an objective and thorough assessment. 14:27:30 Eric: This is very general. Is this enough? 14:27:56 Eric: Do we need more information here? 14:27:57 scribe: MoeKraft 14:28:20 Q+ 14:28:41 +1 14:28:56 Should we add a statement that indicates based upon the size and complexity of the website that it would be good to ask questions of the commissioner to define the scope. 14:29:31 How do you meet the requirement for 'objective assessment', given that 4 evaluators arrived at different results? 14:29:38 Richard: No good to have components that are accessible and others that are not. It is important that the commissioner define what the elements are that belong in the scope of the test. 14:29:56 q+ 14:30:16 q- rich 14:30:26 q+ 14:30:30 q? 14:30:55 Richard: Concerned that we are getting away from our guidance to look at all components. 14:31:02 q- kath 14:31:13 Kathy: Not clear when to start and stop. Good idea to have questions to come up with representative example of all page.s 14:32:10 Kathy: There is a lot of information we can get from the commissioner before evaluating a site 14:32:28 Eric: This is used regularly in our testing in the Netherlands when to start and stop 14:32:40 q? 14:32:53 q+ korn 14:33:33 q- moe 14:34:20 Eric: Need help from the commissioner 14:34:28 q- korn 14:35:00 Just to respond to Richard is that we can get pulled into many different websites both owned by IBM and not and need guidance from commissioner as to what belongs to support website. 14:35:24 Korn: It is entirely appropriate for team to scope what pages it will look at in a given moment in time. 14:35:32 Tim has joined #eval 14:36:09 Martijn: Common functionality. Section 2b. Responses are pretty much the same from all respondents. 14:36:20 Martijn: Step 2b 14:37:17 Martijn: Step 2c Variety of web pages. One evaluator referred back to Step 2a where pages were already mentioned. Not sure if this means we don't really need 2c. Other responders described templates used. 14:38:06 Martijn: Step 2d is found to be confusing 14:38:15 Martijn: Technologies Used 14:39:12 Richard and I seem to agree that it would be the *custom* techniques that need to be listed 14:39:43 q+ 14:40:13 Moe: When looking at common functionality want to be careful to not test functionality but to test the access to the functionality 14:40:36 Richard: Be careful not to call Common Functionality but instead Important Functionality 14:40:56 Richard: Receiving many comments on this section from the public comments. 14:41:20 in the disposition of comments 14:41:25 Eric: Is there an alternative proposal in the results page? 14:41:55 +Tim_Boland 14:41:57 Richard: No. In the disposition of comments. 14:42:23 http://www.w3.org/WAI/ER/conformance/comments-20130226 14:42:42 http://www.w3.org/WAI/ER/conformance/comments-20130226#comment3 14:43:08 http://www.w3.org/WAI/ER/conformance/comments-20130226#section1cont 14:43:11 Look at ID 3 14:43:29 Eric: Concerned that people don't see Section 2 as the Exploration of the website. 14:43:43 Eric: The third step should product the sample. 14:43:50 Eric: Maybe not clear for everyone. 14:43:59 q+ 14:44:06 q? 14:44:15 q- rich 14:44:25 q - moe 14:44:28 q- moe 14:45:18 q+ 14:46:11 +Peter_Korn.aaa 14:46:16 Eric: Let's just flag this one. 14:46:17 -Peter_Korn.aa 14:46:18 q? 14:46:24 ack me 14:46:41 +1 14:47:09 Eric: Look into results of step 2. Do we have to put down everything there? flag this for review if we want to put everything there. Should it not be basis for sample? 14:47:11 Martijn: Maybe partly because in the results of the questionnaire we were asked what everyone did maybe we didn't have to note the list but this was asked of the questionnaire. 14:48:00 Moe: Step 2a states "During this step the common web pages of the website are identified and documented." 14:48:37 q+ 14:48:49 Martijn: Section 3: Selecting a sample. Two people gave URIs another person selected all pages. Last evaluator selected a small sample and guidance how to get to pages. 14:49:28 Martijn: People who gave URIs gave them to pages identified in sample 2. Comment regarding small sample, describes pages but no URIs. 14:50:12 Eric: Do we have an idea that these samples would miss things? Or would they cover the same things? 14:50:27 Martijn: Different scope produced different samples. 14:50:53 Martijn: Detlev had a much more in depthy scope and produced different results. 14:51:12 My hunch is that we would uncover many of the non-conformant things regardless of the exact shape of the sample... 14:51:20 q? 14:51:37 Martijn: May need to be more explicit. 14:52:33 Korn: Peter is looking at answers. A couple answers give a lot of pause. 1 evaluator is expecting to test all pages of web site. 14:52:51 Richard: Self contained element should be tested. 14:53:18 Korn: "All pages in the application will be evaluated. " 14:53:39 Richard: Scope was already defined in Step 1. So all pages in application were already defined. 14:54:59 Richard: Portal gave access to all support website. Did not identify all of ibm web site. Went by scope that indicated ibm.com/support. 14:55:18 Richard: Only checked the portal. 14:55:23 Richard: 9 pages 14:55:43 Eric: Home, Support, Downloads, etc. Tabs at top of pages 14:55:58 s /ibm/website2/ 14:56:41 q+ 14:57:57 q- korn 14:58:08 Korn: Find the product and other links on this page. Were these in scope or out of scope of the test? 14:59:03 Richard: Looked at horizontal menu, 7 tabs, and opened each tab, and followed links that went to portal. Downloads and Troubleshoot went to external areas. 14:59:14 Richard: Essentially looked at application as a portal. 15:00:09 Martijn: I agree with Richard. It is a portal. I did the same as Richard but also included some more static pages and inclued some functionality from main page, signing in, look for products. 15:00:18 q+ 15:00:23 q- mart 15:00:44 Eric: Interesting to see the differences in sample. 15:01:44 Moe: This brings us back to our first discussion regarding communicating to the evaluation commissioner to define the scope. 15:01:58 Eric: Looking for volunteer to write a summary of results for website 3. 15:02:31 Eric: Will search for a volunteer outside this telco. 15:02:41 -Kathy 15:02:42 -MoeKraft 15:02:42 -Peter_Korn.aaa 15:02:43 -Richard 15:02:51 trackbot, end meeting 15:02:51 Zakim, list attendees 15:02:51 As of this point the attendees have been +31.30.239.aaaa, MartijnHoutepen, +31.30.239.aabb, Kathy, ericvelleman, Peter_Korn, MoeKraft, matthias_samwald, Richard, Tim_Boland 15:02:52 korn has left #eval 15:02:59 RRSAgent, please draft minutes 15:02:59 I have made the request to generate http://www.w3.org/2013/06/06-eval-minutes.html trackbot 15:03:00 RRSAgent, bye 15:03:00 I see no action items