13:54:12 RRSAgent has joined #eval 13:54:12 logging to http://www.w3.org/2012/10/04-eval-irc 13:56:10 Zakim, this will be eval 13:56:10 ok, MartijnHoutepen, I see WAI_ERTWG(Eval TF)10:00AM already started 13:57:02 ack me 13:57:28 zakim, who is on the phone? 13:57:28 On the phone I see ??P3, +1.978.443.aaaa 13:57:51 zakim, aaaa is me 13:57:51 +Kathy; got it 13:57:58 zakim, ??P3 is me 13:57:58 +vivienne; got it 13:58:19 Liz has joined #eval 13:59:03 +Liz 13:59:33 +MartijnHoutepen 14:00:07 zakim, who is on the phone? 14:00:07 On the phone I see vivienne, Kathy, Liz, MartijnHoutepen 14:00:28 Sarah_Swierenga has joined #eval 14:01:16 ericvelleman has joined #eval 14:01:19 zakim, mute me 14:01:19 vivienne should now be muted 14:01:33 Zakim, mute me 14:01:34 regrets: Tim, Alistair, Moe 14:01:40 MartijnHoutepen should now be muted 14:02:07 chair: Eric 14:02:26 +Sarah 14:02:28 ack me 14:03:03 +Eric_Velleman 14:03:24 scribe: Sarah 14:05:21 zakim, mute me 14:05:21 MartijnHoutepen should now be muted 14:05:23 zakim, mute me 14:05:23 Kathy should now be muted 14:05:53 topic: comments until now 14:06:11 korn has joined #eval 14:06:33 scribe: sarah 14:06:49 EV: We will collect all the received comments into a disposition of comments and publish this after the comments close 14:07:34 ack me 14:07:49 +[Oracle] 14:07:51 Zakim, Oracle has Peter_Korn 14:07:51 +Peter_Korn; got it 14:07:59 zakim, mute me 14:07:59 MartijnHoutepen should now be muted 14:08:07 item #3 random sampling survey 14:08:44 http://lists.w3.org/Archives/Public/public-wai-evaltf/2012Oct/0017.html 14:09:07 yes 14:09:09 q+ 14:09:10 yes 14:09:15 yes 14:09:29 +Katie_Haritos-Shea 14:09:36 q+ 14:09:40 ack me 14:10:29 q+ 14:10:57 vivienne: evaluation commissioner - maybe need question; to what extend do the views of the commissioner change the sample selection? 14:11:10 Ryladog has joined #eval 14:11:12 zakim, mute me 14:11:12 vivienne should now be muted 14:11:16 q? 14:11:16 q+ 14:11:34 ack me 14:11:45 q- korn 14:12:19 mike_elledge has joined #eval 14:13:00 peter: concern with survey is that is focused on external evaluation and sampling. If this the only view we have then we'll miss other users and use cases, e.g., web apps, templates, boundary condition testing. 14:13:12 q- 14:13:24 +Mike 14:13:37 martijn: add questions if you like 14:14:02 ericvelleman has joined #eval 14:14:08 peter: the questionnaire would have to expand significantly, so we might want to break them up into two questionnaires 14:14:10 -Eric_Velleman 14:14:22 q+ 14:14:35 sorry, my phone was also on internet, so I will have to dial in again 14:15:22 ericvelleman has left #eval 14:15:34 peter: different survey for structured reviews for websites that are too big, or have too many permutations 14:15:38 ericvelleman has joined #eval 14:16:15 martijn: maybe another questionnaire for in-house testing 14:16:36 +Eric_Velleman 14:17:07 peter: craft a placeholder for random sampling for other types of website 14:17:11 [[I wonder if we need two questionnaires that follow each other to dig deeper into particular areas (such as web applications) rather than splitting by in-house/external modalities?]] 14:17:34 q? 14:17:56 ack me 14:18:11 zakim, mute me 14:18:11 MartijnHoutepen should now be muted 14:18:40 Kathy: need more for web applications. right now we have #12 that can start the discussions. is that enough? 14:19:43 peter: how do you adjust your sampling approach? your testing approach? adjustment could be to remove Random from the title and add it to specific items. 14:21:08 kathy: #3 - this would change depending on what type of evaluation is done 14:21:16 q? 14:22:27 * vivienne agrees that we should change the title and make the survey about sampling, not just random 14:22:35 q- 14:23:28 kathy: mobile apps, websites, web apps, etc. 14:24:10 kathy: methodology is very focused on websites; internal vs external views of applications should be addressed 14:24:39 zakim, mute me 14:24:39 Kathy should now be muted 14:24:42 q? 14:24:45 ev: need to account for these ideas 14:26:13 q+ 14:26:14 katie: agrees with peter and kathy re: internal vs external views. when we figure out the universe of this document, we need to consider historic components of the project 14:26:30 q+ 14:26:44 shadi: mobile has to be in the scope 14:26:45 q- Ryladog 14:26:46 +1 14:26:49 q? 14:26:50 yes, mobile has to be there 14:26:57 +1 14:27:17 +1 mobile 14:27:47 [[not advocating to remove mobile but wondering about terminology difference between "mobile app" versus "mobile website"]] 14:28:33 peter: include mobile as part of the universe. question about re-review: white box testing where the engineering group tells you we made lots of changes in these areas, so we focus on the new areas. how would this adjust the sampling? 14:28:42 q? 14:28:45 ach me 14:28:49 q- korn 14:28:53 ack kathy 14:29:30 q+ 14:29:36 kathy: also missing is the role of automated testing. do automated tests change the sampling strategy? 14:29:57 q? 14:30:31 ack me 14:30:38 q+ 14:30:40 ev: good idea for a new question 14:31:14 zakim, mute me 14:31:14 Kathy should now be muted 14:31:17 +1 14:31:40 +1 14:32:02 vivienne: likes adding question about automated testing. sometimes uses automated tools to help decide on pages to test for manual review. 14:32:03 zakim, mute me 14:32:03 vivienne should now be muted 14:32:04 q? 14:32:09 +1 14:32:11 q- viv 14:33:06 ev: send proposed questions/revisions to the list 14:33:15 sure 14:34:42 q? 14:34:43 q+ 14:34:52 q- korn 14:35:50 peter: native apps shouldn't be within the scope. 14:36:58 katie: agrees that native apps shouldn't be included, but if it opens in a browser it should be included. 14:38:12 peter: if it's not something that users can direct their browsers to view, then it shouldn't be included 14:38:36 q+ 14:38:53 peter: e.g., iTunes is not within scope 14:38:53 [[propose a question to compare *sampling* in mobile web apps vs in traditional web apps]] 14:40:06 katie: the excell version (plugin) that opens in the browser is covered by WCAG. so, bottom line is 'if it opens in a browser it is included.' 14:40:27 q? 14:40:27 ack me 14:41:45 zakim, mute me 14:41:46 Kathy should now be muted 14:41:58 kathy: add on to Katie's comment, there are instances where the majority of the application runs in a browser but calls out a native app, then that should be included. 14:42:55 ev: add your questions to the questionnaire list by next Tuesday 14:43:52 ev: next agenda item: goodness criteria - propose discussing this on the next call 14:44:18 ev: agenda item 5: approaches for tolerance 14:45:55 http://www.w3.org/WAI/ER/2011/eval/track/issues/1 14:47:42 peter: aggregating individual results into a conformance statement - my fundamental concern is how to convey the results in a meaningful fashion; red, yellow, green ratings for the outputs are minimally helpful. 14:47:55 q+ 14:48:22 ramoncorominas has joined #eval 14:48:35 peter: confidence level is key 14:48:55 ack me 14:50:24 vivienne: does failing one item means failing overall - we have decided yes, but we may want to consider a 'not quite there' rating, a 'conditional pass' 14:50:49 q+ 14:50:49 q+ 14:50:52 zakim, mute me 14:50:52 vivienne should now be muted 14:50:53 ack me 14:51:04 vivienne: this approach encourages developers to get those items fixed to get a complete pass 14:52:39 katie: uses a similar approach. uses high, medium, low severity for the items; also has rating for impact for persons with disabilities, e.g., descriptive text on a spacer image vs an unlabeled link that would impact PWD more. 14:53:04 q? 14:53:41 [[I see three parts of the evaluation "output": (1) conformance to WCAG - yes/no; (2) some type of score - indicative to help "motivate" developers and decision makers; (3) report - to show the types of issues to explain the "severity" and guide developers on how to fix issues]] 14:54:02 ev: two discussions on tolerance - 1) confidence level or 2) severity/impact for PWD 14:55:25 q+ 14:56:04 q+ 14:56:20 q- 14:56:26 peter: these two approaches are closely linked; confidence of what you are reporting is a given. but how do you convey 'good, but not perfect' or 'not horrible' vs sites that are mostly inaccessible, since this is very valuable info? 14:56:46 ev: we should continue this discussion on the list 14:57:31 ev: agenda item #6: graphic 14:59:33 kathy: sent a couple of graphics to the list. want feedback on 1) what do we see as the differences in interactions with the different steps? and 2) how to convey this in the graphic?. e.g., the arrows don't overlap, but they should. 14:59:59 Nice job Kathy 15:00:07 ev: graphics are colorful and clear, so let's get them finalized 15:00:29 kathy: working with WCAG group on the graphic, too. 15:00:45 ack me 15:00:47 bye - have a good week 15:00:48 bye 15:00:49 okay, bye all 15:00:51 [[I really like the lify-cycle approach]] 15:00:52 -vivienne 15:00:55 vivienne has left #eval 15:00:55 bye 15:00:58 -Kathy 15:01:06 -Katie_Haritos-Shea 15:01:11 -Mike 15:01:13 -[Oracle] 15:01:15 -Sarah 15:01:17 -vivienne 15:01:18 Shadi, are you making the minutes? 15:01:34 -Eric_Velleman 15:01:35 korn has left #eval 15:01:35 ericvelleman has left #eval 15:01:35 -Liz 15:01:41 ok thanks shadi 15:01:45 bye 15:01:46 trackbot, end meeting 15:01:46 Zakim, list attendees 15:01:49 As of this point the attendees have been +1.978.443.aaaa, Kathy, vivienne, Liz, MartijnHoutepen, Sarah, Eric_Velleman, Peter_Korn, Katie_Haritos-Shea, Mike 15:01:49 MartijnHoutepen has left #eval 15:01:54 RRSAgent, please draft minutes 15:01:54 I have made the request to generate http://www.w3.org/2012/10/04-eval-minutes.html trackbot 15:01:55 RRSAgent, bye 15:02:12 -MartijnHoutepen 15:02:16 WAI_ERTWG(Eval TF)10:00AM has ended 15:02:19 rrsagent, make logs world 15:02:21 Attendees were +1.978.443.aaaa, Kathy, vivienne, Liz, MartijnHoutepen, Sarah, Eric_Velleman, Peter_Korn, Katie_Haritos-Shea, Mike 15:02:27 rrsagent, make mnutes 15:02:27 I'm logging. I don't understand 'make mnutes', shadi. Try /msg RRSAgent help 15:02:32 rrsagent, make minutes 15:02:32 I have made the request to generate http://www.w3.org/2012/10/04-eval-minutes.html shadi 15:02:42 rrsagent, bye 15:02:42 I see no action items