13:55:19 RRSAgent has joined #eval 13:55:19 logging to http://www.w3.org/2011/10/06-eval-irc 13:55:21 RRSAgent, make logs world 13:55:21 Zakim has joined #eval 13:55:23 Zakim, this will be 3825 13:55:23 ok, trackbot; I see WAI_ERTWG(Eval TF)10:00AM scheduled to start in 5 minutes 13:55:24 Meeting: WCAG 2.0 Evaluation Methodology Task Force Teleconference 13:55:24 Date: 06 October 2011 13:55:40 WAI_ERTWG(Eval TF)10:00AM has now started 13:55:47 + +1.301.975.aaaa 13:55:59 ssirois has joined #eval 13:56:53 + +1.514.312.aabb 13:56:56 - +1.301.975.aaaa 13:56:58 + +1.301.975.aaaa 13:57:06 zakim, aabb is me 13:57:06 +ssirois; got it 13:57:23 Zakim, mute me 13:57:23 ssirois should now be muted 13:57:24 zakim, aaaa is Liz 13:57:25 +Liz; got it 13:57:58 + +1.978.443.aacc 13:58:01 AmyChen has joined #eval 13:58:46 zakim, aacc is Kathy 13:58:46 +Kathy; got it 13:58:59 zakim, call shadi-617 13:59:01 ok, shadi; the call is being made 13:59:05 +Shadi 13:59:31 + +1.925.694.aadd 13:59:41 zakim, aadd is me 13:59:47 +AmyChen; got it 13:59:49 zakim, mute me 13:59:53 zakim, mute me 13:59:54 zakim, who is on the phone? 13:59:57 Kathy should now be muted 14:00:01 AmyChen should now be muted 14:00:07 On the phone I see Liz, ssirois (muted), Kathy (muted), Shadi, AmyChen (muted) 14:00:33 +Katie_Haritos-Shea 14:01:33 richard has joined #eval 14:02:04 +??P38 14:02:06 Ryladog_ has joined #eval 14:02:35 + +666028aaee 14:02:39 zakim, ??p38 is Richard 14:02:39 +Richard; got it 14:03:01 zakim, aaee is Emmanuelle 14:03:01 +Emmanuelle; got it 14:03:07 zakim, who is on the phone? 14:03:07 On the phone I see Liz, ssirois (muted), Kathy (muted), Shadi, AmyChen (muted), Katie_Haritos-Shea, Richard, Emmanuelle (muted) 14:03:28 Tim has joined #eval 14:03:44 http://www.w3.org/WAI/ER/2011/eval/minutes.html 14:03:51 Topic: Welcome 14:03:59 LeonieWatson has joined #eval 14:04:20 I can try scribing. Do I just type notes in IRC? 14:04:40 scribe: AmyChen 14:05:10 ok 14:05:26 +Tim_Boland 14:05:38 sinarmaya has joined #eval 14:06:16 Shadi: top of list are candidates for scribing 14:06:43 http://www.w3.org/WAI/ER/2011/eval/eval-tf 14:06:54 + +1.517.353.aaff 14:07:53 zakim, aaff is Mike 14:07:53 +Mike; got it 14:08:00 Topic: Requirements 14:08:01 Shadi: some progress on list, transition from requirements phase to content development phase 14:08:28 http://lists.w3.org/Archives/Public/public-wai-evaltf/2011Oct/0010.html 14:08:32 Shadi: Richard proposed alternative concise requirements 14:08:53 http://lists.w3.org/Archives/Public/public-wai-evaltf/2011Oct/0025.html 14:09:10 + +30231125aagg 14:10:07 zakim, aagg is kostas 14:10:07 +kostas; got it 14:10:12 Shadi: Note that it is not engraved in stone, initial set of requirements for better understanding, good discussions 14:11:24 Shadi: From my perspective, req pretty stable. Kristen raised Objective and Validity. Open that up for discussion. 14:11:29 q+ 14:11:48 ack tim 14:12:49 +??P59 14:13:14 Tim: Intents of requirement, when possible should be the same. Present active tense, testability, partial results. Better to be consistent. Will employ versus "should" get equivalent results. General comments. Better to use declarative present tense to evaluate when see fit, pass/fail. 14:13:34 agarrison has joined #eval 14:14:02 zakim, ??59 is agarrison 14:14:02 sorry, shadi, I do not recognize a party named '??59' 14:14:09 zakim, ??P59 is agarrison 14:14:09 +agarrison; got it 14:14:21 q+ 14:14:28 ack r 14:15:28 Richard: Agree about the tense. Word "should" to try and limit it, discussions instead of exact comparison to be less strict. Not identical results. Used the word "should." Don't mind if changed. 14:15:46 q+ 14:16:13 Shadi: We want as much correlation as possible btw different evaluators, but how to find the wording and measure. Don't know if we can sort out at this early phase. Try to find wording we are all comfortable with, then get methodlogy where we want it to be. 14:16:17 ack m 14:16:34 Mike: Think we should have consistent headings in their structure and formatting. 14:17:15 Shadi: Leave this for discussion for editorial work. Does help to have consistency. 14:17:41 [[RQ 01 : Define methods for evaluating WCAG 2.0 conformance 14:17:41 The Methodology provides methods to measure conformance with WCAG 2.0 that 14:17:41 can be used by the target audience (see section 2 above) for evaluating 14:17:43 small and large websites, sections of websites or web-based applications.]] 14:17:50 Shadi: Req 1 - note that we did want to look at the heading for each of the req and tense. Any other comments on Req 1? 14:18:43 Question from phone: what is def of large website? 14:18:57 Shadi: proper wording, website regardless of size 14:19:16 s/Question from phone:/Tim: 14:20:20 [[RQ 02 – Clear, understandable, and translatable language 14:20:20 The methodology is written in clear language, understandable to the target 14:20:20 audience and capable of translation to other languages.]] 14:21:29 rq2 is just fine with me 14:21:44 capable is fine 14:21:54 q+ 14:21:56 [[RQ 04 - Tool and browser independent 14:21:56 The use and application of the Methodology is independent of any particular 14:21:56 evaluation tools, browsers, and assistive technology. It requires combined 14:21:56 use of manual and automated testing approaches to carry out a full 14:21:56 evaluation according to the Methodology.]] 14:22:27 q+ 14:22:36 ack m 14:23:05 should we use the term evaluation or assessment 14:23:09 Mike: Question about Req 2. Objectivity could be addressed in Req 2 to resolve some of the issues brought up. 14:23:31 Shadi: Please re-raise if forget. 14:24:07 [[RQ 05 - QA framework specification guidelines 14:24:07 The Methodology will conform to the Quality Assurance framework 14:24:07 specification guidelines as set in: http://www.w3.org/TR/qaframe-spec/.]] 14:24:28 Shadi: Good question. (Agarrison) Keep for later. 14:24:41 Shadi: R5 pretty straightforward. 14:24:44 [[RQ 06 - Reporting 14:24:44 The Methodology includes recommendations for reporting evaluation findings. 14:24:44 It will be based on the [href=http://www.w3.org/WAI/eval/template.html 14:24:44 standard template] and supplemented with machine-readable 14:24:45 [href=http://www.w3.org/WAI/intro/earl reports using Evaluation and Report 14:24:47 Language (EARL)].]] 14:24:48 q+ 14:24:57 ack r 14:25:32 q+ 14:25:33 q+ 14:25:57 Katie: Back to Req 4. Whoever recommened use and application language. independent of any browser, tools, AT. Like that wording. 14:26:01 ack m 14:26:34 Mike: Req 6 - difficulty understanding the statement. Methodology include info on how to report the findings, or recommendations based on the eval findings? 14:26:59 Shadi: Should include both. What do others think? 14:27:09 ack r 14:27:55 Richard: Req 6, the template talks about WAI 1, standard template to look from for report, know what questions we have to answer, such as define website to make it valid and reliable. 14:28:51 Shadi: Tried to separate the two points. We can update the template. Group that maintains that is EOWG. Base intial thoughts from there and update template with methology that we have. Template could be part of methology. Standardized reporting template. 14:29:19 Shadi: Methodology includes "how", woudl that make it clearer? 14:29:46 sorry, can you repeat the changes? 14:29:46 [[RQ 07 - Use of existing WCAG 2.0 processes 14:29:46 Wherever possible the Methodology will employ existing testing procedures in 14:29:46 the WCAG 2.0 Techniques documents rather than replicate them.]] 14:30:16 The Methodology includes recommendations for howe to report evaluation findings based on ... 14:30:39 RQ 07 is good 14:31:06 is testing procedures the right term? 14:31:42 Shadi: "The methology employes existing testing procedures." 14:32:12 Methodology employs existing WCAG 2.0 Techniques rather than replicate them 14:32:19 Allistair: There was a testing procedure at the end of every technique. 14:32:30 The Methodology employs existing testing procedures from WCAG 2.0 Techniques rather than replicate them 14:32:37 q? 14:32:44 q+ 14:33:08 +1 test procedure 14:33:25 Allistair: What about test procedure? nice to have one for each technique to limit it to that technique 14:33:42 ack r 14:33:45 Shadi: Diff to expalin lower level testing and the evaluation. interrelationship. 14:34:02 The Methodology employs existing testing procedures within WCAG 2.0 Techniques rather than replicate them 14:34:25 Katie: Agree with Test Procedure. Not sure about limiting it to one technique. Test Procedure covers overall intent of the requirement, instead of identifying specific techniques. 14:34:38 Shadi: Tried changing one word. Instead of "from" to "within" 14:34:40 that is better 14:34:46 +1 14:34:49 within is better 14:34:53 better 14:36:05 Q from phone: methodology for manual eval. Testing and tech not complete, only for automatic eval? 14:36:25 Shadi: Techniques not only for automatic testing. 14:36:46 Shadi: Techniques on WCAG working group. 14:36:46 shadi is echoing 14:37:08 zakim, mute emmanuelle 14:37:08 Emmanuelle should now be muted 14:37:56 LeonieWatson has joined #eval 14:38:09 Shadi: Techniques not exhaustive. This group not focus on the individual testing procedures, but rather on overall procedure aspect. 14:39:27 Shadi: Work being done outside W3C. Vendors, tools, testing techniques. Open initiatives for testing procedures. Some work to compile that. Fit into methodology. 14:39:31 q? 14:39:59 [[RQ 08 - Recommendations for scope and sampling 14:39:59 It includes recommendations for methods of sampling web pages and how to 14:39:59 ensure that complete processes (such as for a shopping site where all the 14:39:59 pages that are part of the steps in an ordering process) are included. Such 14:39:59 selections would be reflected in any conformance claim.]] 14:40:02 Shadi: Title of Req 7 needs to be updates 14:40:11 q+ 14:40:30 ack k 14:41:03 "It includes recommendations" might be "it defines" 14:41:14 Kostas: Concerned about req about sampling. General methods, but give examples? How can we cover all of the possibilities? Effective sampling? General recommendations and methods? How can we ensure the complete process? 14:41:20 q+ 14:42:19 q+ 14:42:25 Shadi: good example, give some numbers, based on website size. Need to develop. One of the big parts. Req 8 and 9 the biggest parts of the methodology. Depending on how well we do 8 and 9, then number 3, replicability will emerge 14:43:01 Kostas: Maybe need to be more specific. 14:43:04 q+ 14:43:04 ack me 14:43:08 ack amy 14:43:33 Amy: sampling will be a big part but we have lots of experience at Oracle 14:43:39 ack me 14:43:47 ...but ok with the wording as it stands now 14:44:07 Kathy: Suggest taking out the example. "Such as for a shopping site" Scenarios, concerned with throwing one specific thing in there. 14:44:21 Shadi: Better to define complete process in terminology section and link to it 14:44:25 zakim, mute me 14:44:25 Kathy should now be muted 14:44:29 ack a 14:44:34 +1 14:44:45 +1 14:45:15 q+ 14:45:20 Allistair: Recommendations, methods have to be consistent. Doesn't mean they have to be using those methods. 14:45:38 Allistair: Change to recommendations for scope and sampling 14:46:05 +1 14:46:06 +1 14:46:10 +1 14:46:11 +1 14:46:12 ack t 14:46:15 should be change from recommendations to just scope and sampling 14:46:15 +1 14:46:17 +1 14:46:31 +1 14:46:52 Sorry, Allistair means, take out recommendations 14:47:29 Tim: WCAG and ATAG discussions on what would be in a conformance claim. 14:47:41 Shadi: could go in reporting section on conformance claim 14:47:43 +1 14:47:50 +1 14:47:50 +1 14:47:52 +1 14:47:53 +1 14:48:07 q+ 14:48:17 [[RQ 09 - Includes tolerance metrics 14:48:17 It includes calculation methods for determining nearness of conformance. 14:48:17 Depending on the amount of tolerance, a failure could fall within a certain 14:48:17 tolerance level meaning that the page or website might be considered 14:48:17 conformant even though there is a failure. Such tolerances would be 14:48:18 reflected in any conformance claim.]] 14:48:48 remove includes from title, and change includes to defines 14:48:49 Shadi: Remove the last sentence, but any other thoughts? 14:49:04 I agree 14:49:30 [[RQ 10 - Support documentation 14:49:30 The document will give a short description of the knowledge necessary for 14:49:30 using the Methodology for evaluations.]] 14:49:32 Change Includes Tolerance metrics to Tolerance Metrics. 14:50:06 [[RQ 03 – Reliable 14:50:06 Different Web accessibility evaluators using the same methods on the same 14:50:06 website(s) should get equivalent results. Evaluation process and results are 14:50:06 documented to support independent verification.]] 14:50:24 Shadi: From Kriten on mailing list, that this does not go far enough. 14:50:53 ssirois has joined #eval 14:50:59 +q 14:51:02 Shadi: diluted the wording somewhat, will there really be 100%, same results. What would be reliable? 14:51:03 q+ 14:51:18 Shadi: Tim also raised the concern "should" 14:51:25 sorry, from earlier, nevermind 14:51:31 q- amy 14:51:36 ack r 14:51:57 The wording for R03 sounds nice and scientific - I support current form (should is fine) 14:52:18 Katie: 100% not going to happen, on the 80/20 reviewers. Will probably need something better than that when we get to the actual requirement. 14:52:18 sorry, irc connection trouble, but was on the phone all alone and haven't have something to disagry on that would have urge me to find the way to unmute myself over touchtone! ;) 14:52:40 ack m 14:53:03 Mike: "Should get equivalent and equally valid results." and define valid 14:53:11 q+ 14:53:25 Shadi: what diff btw equivalent and equally valid? 14:53:43 ack me 14:53:43 ack k 14:53:45 Mike: Equivalent results, but make sure valid. Maybe don't want to say equally. Maybe valid results. 14:54:08 Kathy: Comment on not 100% possible, if we define equivalent results. 14:54:32 Action: Equivalent results need to be defined. High correlation. Weave in validity. 14:54:32 Sorry, couldn't find user - Equivalent 14:54:51 zakim, mute me 14:54:51 Kathy should now be muted 14:55:15 Shadi: Mike earlier raised objectiveness and objectivity. Fits in req 2 14:55:55 Shadi: Reliable, R3, define equiv results and link to it 14:56:00 +1 14:56:04 +1 14:56:07 +1 14:56:09 +1 14:56:12 +1 14:56:14 +1 14:56:15 +1 14:56:17 +1 14:56:37 +1 14:56:43 Shadi: go back to Objective R2, how about Clear language that is unambiguous and understandable to audience 14:57:05 clear = unambiguous 14:57:11 Mike: Yes, seems to get at it to me. 14:57:22 q+ 14:57:28 ack a 14:57:43 Allistair: How about language that is clear and understandable to the audience. 14:57:56 clear is not testable 14:58:37 Q+ 14:58:37 sorry, repeat please? 14:58:59 Allistair: Unambigous might be harder to understand 14:59:22 Shadi: Replace clear rather than unambigous 14:59:51 15:00:00 Topic: Naming 15:01:37 Methodology for Assessing Website Conformity 15:02:06 Kostas: Sampling, Inspection, and Technical Evaluation (SITE) has the word "site" not to be confused with websites 15:02:28 (Kostas - was that what you were saying?) 15:02:37 What about MEAC? INSTEAD OF MAC? 15:02:37 Shadi: Let the creative juices flow for naming 15:02:58 Shadi: take it to the list and talk about it next week. 15:03:11 Thanks! Bye 15:03:14 Zakim, unmute me 15:03:18 cioa 15:03:20 Thanks everyone, bye! 15:03:20 trackbot, end meeting 15:03:20 Zakim, list attendees 15:03:21 RRSAgent, please draft minutes 15:03:21 I have made the request to generate http://www.w3.org/2011/10/06-eval-minutes.html trackbot 15:03:21 sinarmaya has left #eval 15:03:22 RRSAgent, bye 15:03:22 I see 1 open action item saved in http://www.w3.org/2011/10/06-eval-actions.rdf : 15:03:22 ACTION: Equivalent results need to be defined. High correlation. Weave in validity. [1] 15:03:22 recorded in http://www.w3.org/2011/10/06-eval-irc#T14-54-32 15:03:27 Bye, bye!