14:59:41 RRSAgent has joined #eval 14:59:41 logging to http://www.w3.org/2013/12/12-eval-irc 14:59:43 RRSAgent, make logs world 14:59:43 Zakim has joined #eval 14:59:45 Zakim, this will be 3825 14:59:45 ok, trackbot; I see WAI_ERTWG(Eval TF)10:00AM scheduled to start in 1 minute 14:59:46 Meeting: WCAG 2.0 Evaluation Methodology Task Force Teleconference 14:59:46 Date: 12 December 2013 14:59:59 zakim, this is eval 14:59:59 ok, shadi; that matches WAI_ERTWG(Eval TF)10:00AM 15:00:08 zakim, who is on the phone? 15:00:08 On the phone I see Kathy_Wahlbin 15:00:17 agarrison has joined #eval 15:00:51 +EricVelleman 15:01:21 +Shadi 15:01:32 I'll join telecon in a couple of minutes 15:02:02 +Detlev 15:02:04 +MartijnHoutepen 15:02:09 MoeKraft has joined #eval 15:02:55 +MoeKraft 15:03:12 Sarah_Swierenga has joined #eval 15:03:36 http://www.w3.org/WAI/ER/conformance/comments-20131129 15:03:50 +Sarah_Swierenga 15:04:27 who is scribing? 15:04:38 +[IPcaller] 15:04:41 richard has joined #eval 15:04:46 Mike_Elledge has joined #eval 15:04:52 scribe? 15:05:03 zakim, ipcaller is Richard 15:05:03 +Richard; got it 15:05:18 zakim, ipcaller is Alistair 15:05:18 sorry, agarrison, I do not recognize a party named 'ipcaller' 15:05:23 +Mike_Elledge 15:05:28 +[IPcaller] 15:05:30 fine 15:05:53 zakim, mute me 15:05:53 MartijnHoutepen should now be muted 15:06:03 scribe: Detlev 15:06:33 zakim, ipcaller is Alistair 15:06:33 +Alistair; got it 15:08:43 Shadi: Many comments, mote to come. Most disputed perhaps scoring, Use of review teams. 15:09:53 q+ 15:09:59 Shadi: There was a call to review reference to review teams - suggestion to respond by chsanging language from "highly recommended' to 'beneficial' 15:10:14 q? 15:10:20 ack me 15:11:12 http://www.w3.org/WAI/ER/conformance/comments-20131129#comment10 15:11:17 Kathy: Need not be highly recommended but still usefull, even by not so experienced evaluators - remains a good recommendation. 15:12:01 Remove +1 15:12:08 +1 15:12:13 +1 15:12:15 +1 15:12:21 Shadi: Any objections to changing from highly recommended change to something else? 15:12:23 +1 15:12:24 no 15:12:41 Shadi: resolution to change language, but section stays in 15:13:03 http://www.w3.org/WAI/ER/conformance/comments-20131129#comment11 15:13:23 Shadi: Comment No. 11 (Michael Cooper) concerning the removal of a section 15:14:05 http://www.w3.org/WAI/ER/conformance/comments-20131129#comment18 15:14:50 Shadi: Comment 18 )Gregg) :Concern about the use of the term "core functionality" 15:15:45 q+ 15:16:08 Shadi: Suggestion Gregg: better use DEPENDEND COMPONENTS 15:16:50 Richard: The thing is about function, not component, functionality should stay - could ber either core or common 15:17:34 Shadi asks people to look at comment 18 closely to solve this issue 15:17:58 Eric: This started with primatry functionality 15:18:11 Liz has joined #eval 15:18:27 Detlev Dependent components is not easy to grasp 15:18:43 Eric: can't we keep 'core functionality'? 15:18:58 Shadi: lets wait for responses first, then decide 15:19:05 +Liz 15:19:22 Shadi: explains difference between core and dependent.. 15:19:27 q? 15:19:36 q+ 15:19:46 q+ 15:19:46 q- richard 15:20:11 Liz has joined #eval 15:21:23 DF: i believe GVs concern is about opening the floodgates to subjective interpretations of core 15:22:34 ack me 15:22:38 Tim has joined #eval 15:22:39 DF: afraid of using complicated terms 15:23:02 Detlev explains what Gregg arguments against core functionality were 15:24:15 Kathy: Agrees that core functionality may not be ideal, bu tthe main thing is to link to a terms definition "core functionality' (or whatwever other term) 15:26:04 Shadi: Agreement that core functionality may be subject to misunderstanding we could truy dependend components 15:26:04 q+ 15:28:12 DF: trying to find an example of another term suggested bij GV; I think it was 'essential'. 'Dependent component' seems too complicated 15:28:40 [[From Gregg's comment: I would advise talking about "High Frequency pages" -- and "Pages needed to complete processes".]] 15:28:45 q+ 15:29:00 q- det 15:29:36 Detlev core is perhaps too narrow, better term needed 15:30:03 Alistair: does not like dependent components, makes no sense 15:30:32 Shadi: Resolution: We accept Greggs critique but think his suggestino is not ideal 15:30:38 http://www.w3.org/WAI/ER/conformance/comments-20131129#comment37 15:31:54 Shadi Comment 37: involving people with disabilities - one comment asking that non-optonal, the othe rtoo remove that sugestino because it adds not so much to checking, mire to usability 15:32:22 q- ag 15:32:46 q+ 15:33:18 q- ag 15:33:22 Shadi: Proposed resolution: Change to "Involving people with disabilities and people with aging-related impairments helps identify additional accessibility barriers that are not easily discovered by expert evaluation alone". 15:33:46 Alistair: happy with current text 15:33:53 q+ 15:34:05 Eric: also happy with Proposed resolution, AListair? 15:34:33 q- 15:35:05 +Tim_Boland 15:35:51 Alistair: Agrees with second comment that says for purposes of evaluation here, it doesn't add much to involve users 15:36:45 Shadi: Still true (ans should be stated) that it is still beneficial to involve users 15:37:41 Kathy: In user testing you always cstch issues that you wouldn't have caught otherwise, much if it not strictly a11y-related (also to AT, UA, usability etc) 15:38:15 Kathy: we should not open this too much so we do niot confuse users 15:38:59 change from 'discovered by the evaluators alone' to 'discovered by expert evaluation alone'? 15:39:17 Alistair: thinks change weakens the text - do we have to make the change? 15:39:54 no change 15:39:57 Detlev: Can't think aout that so wquickly... 15:40:56 Kathy; Expert evaluation alone will not catch all issues 15:41:52 Shadi: Explains rationale of proposed change to address concern 15:42:06 1+ 15:42:43 Alistair: not happy with change but go ahead 15:43:52 Eric: We need to keep the doc in line with general WAI guidance 15:44:14 Eric: we say it's optional anyway 15:45:12 Shadi: WCAG docs (Intro, Understanding..., mentions the importance of involving users also 15:45:28 http://www.w3.org/WAI/ER/conformance/comments-20131129#comment28 15:46:05 Shadi: Comment 28 - Sample size suggestion by David (Candadian Gov) 15:46:22 q+ 15:46:42 Shadi: Difficulty starts with determining the size (including DOM states) 15:47:04 q? 15:47:41 Shadi: Proposed Resolution: Add editor note and ask for more input on this issue, also ask David for details on source 15:48:06 q- richard 15:48:22 Richard: Our job is to evaluate, not to establish statistically correct sample 15:48:34 Richard: If possible, do the whole thing 15:49:11 Richard: else, follow the steps (common pages, add random sample) 15:49:22 http://www.w3.org/WAI/ER/conformance/comments-20131129#comment31 15:49:56 Shadi: Comment by Richard that we cannot prescribe random sampling 15:50:33 Richard: It is up to the evaluator to specify the random sample size because the need for that will be specific to the web site under review 15:50:52 paste? 15:50:53 http://www.w3.org/WAI/ER/conformance/comments-20131129#comment30 15:51:49 Shadi: There is no implication to sample. 15:52:20 Richard :Weoften do the whole site - should be visible as option 15:52:21 -Mike_Elledge 15:52:46 Shadi: If all has been tested, you can make a conformance claim 15:53:27 Shadi: back to sample size, reiterates proposed resolution 15:53:35 Shadi: Objections? 15:53:37 no 15:53:41 no 15:53:41 Agree 15:55:09 Shadi: Sample size is adaptive and site size specific - What is the objection of suggwesting 10% as random-sampled, Richard? 15:55:56 Richard: Seems it is too detailed, to resterictive 15:56:54 Richard: Would be enough to say use Random sample, let evaluator decide how to do it but record what he/she has done 15:57:28 Shadi: Aim was to introduce a minimunm and a threshold so it would scale 15:57:39 Have to drop early. Have a good weekend all! 15:57:44 -MoeKraft 15:58:42 Eric: OLd versions were very briedf and were beefed up for tthis version - we need to test the methodology so we will find out if it works, that will generate relevant feedback 15:58:54 http://www.w3.org/WAI/ER/conformance/comments-20131129#comment36 15:59:31 Shadi: about N.A. Gregg suggesting use of "not present" instead of N.A. 15:59:52 Shadi: has been discuss a lot in the WG 16:00:07 http://www.w3.org/WAI/ER/conformance/comments-20131129#comment38 16:00:44 Shadi: about the term correlation 16:01:11 Shadi: Please look at the disposition of comments and use the mailing list or survey for feedback 16:01:12 -Kathy_Wahlbin 16:01:22 I have to leave 16:01:41 -Detlev 16:01:49 sorry I had to leave 16:01:50 ill take over 16:02:01 scribe: MartijnHoutepen 16:02:31 SAZ: we'll discuss results with WCAG wg and ERT wg, sadly no publication this year 16:03:20 bye 16:03:25 -Liz 16:03:34 -Tim_Boland 16:03:34 -Alistair 16:03:36 -Richard 16:03:37 EV: thanks Shadi for overview, clustering of comment. Let's start discussions on the list 16:03:37 -Sarah_Swierenga 16:03:39 -Shadi 16:03:40 -EricVelleman 16:03:42 ericvelleman has left #eval 16:04:19 Shadi, will you finish the scribing ? 16:04:31 -MartijnHoutepen 16:04:32 WAI_ERTWG(Eval TF)10:00AM has ended 16:04:32 Attendees were Kathy_Wahlbin, EricVelleman, Shadi, Detlev, MartijnHoutepen, MoeKraft, Sarah_Swierenga, Richard, Mike_Elledge, Alistair, Liz, Tim_Boland 16:38:08 Kathy has left #eval 17:00:23 Bim has joined #eval 17:10:31 shadi has joined #eval 17:10:54 trackbot, end meeting 17:10:54 Zakim, list attendees 17:10:54 sorry, trackbot, I don't know what conference this is 17:11:02 RRSAgent, please draft minutes 17:11:02 I have made the request to generate http://www.w3.org/2013/12/12-eval-minutes.html trackbot 17:11:03 RRSAgent, bye 17:11:03 I see no action items