13:48:49 RRSAgent has joined #eval 13:48:49 logging to http://www.w3.org/2012/04/05-eval-irc 13:48:51 RRSAgent, make logs world 13:48:51 Zakim has joined #eval 13:48:53 Zakim, this will be 3825 13:48:53 ok, trackbot; I see WAI_ERTWG(Eval TF)10:00AM scheduled to start in 12 minutes 13:48:54 Meeting: WCAG 2.0 Evaluation Methodology Task Force Teleconference 13:48:54 Date: 05 April 2012 13:53:24 Detlev has joined #eval 13:54:51 Kathy has joined #eval 13:55:48 WAI_ERTWG(Eval TF)10:00AM has now started 13:55:55 + +1.978.443.aaaa 13:56:17 vivienne has joined #eval 13:56:21 + +31.30.239.aabb 13:56:28 zakim, aaaa is Kathy 13:56:28 +Kathy; got it 13:56:30 +Shadi 13:56:45 MartijnHoutepen has joined #eval 13:57:01 zakim, aabb is Martijn 13:57:01 +Martijn; got it 13:57:34 +??P11 13:57:38 zakim, P11 is me 13:57:38 sorry, vivienne, I do not recognize a party named 'P11' 13:57:48 zakim, ??P11 is me 13:57:48 +vivienne; got it 13:58:38 zakim, pick a victim 13:58:45 Not knowing who is chairing or who scribed recently, I propose Martijn 13:58:48 ericvelleman has joined #eval 13:59:13 + +1.520.271.aacc 13:59:30 zakim, aacc is Don 13:59:37 +Don; got it 13:59:53 + +31.30.239.aadd 13:59:56 Zakim, mute me 14:00:00 sorry, MartijnHoutepen, I do not know which phone connection belongs to you 14:00:15 zakim, aadd is Eric 14:00:15 Zakim, Martijn is really MartijnHoutepen 14:00:24 +Eric; got it 14:00:25 +MartijnHoutepen; got it 14:00:29 Zakim, mute me 14:00:31 + +1.978.562.aaee 14:00:38 MartijnHoutepen should now be muted 14:00:43 zakim, aaee is Moe 14:00:43 +Moe; got it 14:00:47 + +49.404.318.aaff 14:01:17 Zakim, aff is Detlev 14:01:21 zakim, aaff Detlev 14:01:25 sorry, Detlev, I do not recognize a party named 'aff' 14:01:30 Sarah_Swierenga has joined #eval 14:01:34 I don't understand 'aaff Detlev', shadi 14:01:36 scribe: Martijn 14:01:38 korn has joined #eval 14:01:42 zakim, aaff is Detlev 14:01:43 scribenick: MartijnHoutepen 14:02:01 +Detlev; got it 14:02:24 zakim, mute me 14:02:29 + +1.517.353.aagg 14:02:33 zakim, mute me 14:02:45 ack me 14:02:51 Shadi should now be muted 14:02:52 zakim, mute me 14:02:57 + +1.517.432.aahh 14:03:00 Kathy should now be muted 14:03:03 zakim, mute me 14:03:09 zakim, mute me 14:03:13 vivienne should now be muted 14:03:20 shadi, are our logins mixed up? 14:03:21 vivienne was already muted, vivienne 14:03:25 Detlev should now be muted 14:03:32 Mike_Elledge has joined #eval 14:03:33 zakim, aagg is Sarah 14:03:39 +Sarah; got it 14:03:43 zakim, aahh is Mike 14:03:49 +Mike; got it 14:04:10 Eric: Welcome, we have some new members, Peter Korn, Moe, 14:04:25 zakim, mute me 14:04:27 +[Oracle] 14:04:45 zakim, oracle is Peter 14:05:00 Shadi should now be muted 14:05:30 +Peter; got it 14:05:39 Moe: I work at IBM accessibility center, consulting, training & testing accessibility 14:07:22 Peter: Oracle accessibility architect, originally from Sun, interested in WCAG/W3C and section 508 14:07:48 ack me 14:08:02 http://www.w3.org/2000/09/dbwg/details?group=48225&public=1 14:10:28 zakim, mute me 14:10:48 Shadi should now be muted 14:11:37 Eric: looking at public comments mail archive, only 2 received 14:12:14 E: maybe more to the end of april 14:12:34 + +1.703.272.aaii 14:13:00 zakim, aaii is Katie 14:13:00 +Katie; got it 14:13:18 E: If we have a lot of comments we will need a system to work on the comments, if it is not to much we will use a plain html table 14:13:56 Ryladog has joined #eval 14:14:36 E: we will start working on document as is, after 27th april we will process comments 14:14:58 E: hope to have a new draft in 2 months 14:16:39 E: new editor draft not yet up, need more input to fill section 4 and 5, discussion on the list on section headings 14:16:59 http://www.w3.org/TR/WCAG-EM/ 14:17:33 http://www.w3.org/TR/2012/WD-WCAG-EM-20120327/#step4 14:18:57 E: discussion on assistive technology on the list, input needed on step 4a check for the Broadest Variety of Use Cases 14:19:21 q+ 14:19:51 q? 14:20:04 ack Ryladog 14:20:58 EvalTF has joined #eval 14:21:26 Katie: start by identifying primary use case, there may be more purposes beyond that, 14:21:32 q+ 14:21:37 q+ 14:21:47 Moe has joined #eval 14:21:59 ack me 14:22:06 Katie: after primary use case define broadest variety 14:22:51 zakim, mute me 14:22:51 Shadi should now be muted 14:22:51 shadi: step4a relates to 1d, is it internal or public or mobile site, also relates 2b where we select key functionalities 14:23:02 Katie: refer to those sections 14:23:19 ak peter 14:23:25 ack peter 14:23:31 ack korn 14:23:34 q+ 14:23:52 q+ 14:24:06 Peter: what does use case mean when we shift from website to webapplication? is styling in an online texteditor a use case? 14:24:24 q? 14:25:46 Katie: could you phrase this as a question in the steps? 14:26:58 q+ 14:28:04 Peter: i am worried on how this translates to webapplications, some accessibility issues are less important than others, but can be critical in (non-)conformance 14:29:47 Peter: maybe reporting could include impact of problems 14:31:00 ack mike 14:31:44 q+ 14:32:09 Mike: should we be considering different use scenarios? 14:33:42 'scenario' could be quite confusing - sounds close to 'use case' 14:34:05 ack me 14:34:24 E: @mike could you elaborate on the difference between scenarios and use cases on the list 14:35:25 q- 14:36:03 Kathy: user stories more important in agile development model, we need to be careful to explain all flavours of user stories 14:36:48 ack me 14:36:59 zakim, mute me 14:36:59 Kathy should now be muted 14:38:35 zakim, mute me 14:38:35 Shadi should now be muted 14:38:59 shadi: I like this direction. To go back to Peters case: accessibility issues are the same on websites or webapplications, 14:39:30 shadi: we shouldn't make the difference, up to manager to read into findings 14:40:38 q+ 14:40:39 peter: features of an application are different then the distuingishment between use cases, 14:41:45 Eric: would be interesting for evaluators to have a method to define primary use case 14:41:52 q? 14:41:54 ack me 14:42:50 q+ 14:43:10 Detlev: issue on claiming conformance using this methodology, similar problem arises when sampling 14:43:40 D: all features of an application are part of the use case of using the application 14:44:32 D: I think it is benificial to claim conformance while not being totally conformant, if you point out the issues 14:45:28 Eric: not up to evaluator to decide if error is important, this is up to the manager 14:46:22 D: you will then never reach conformance 14:47:08 Zakim, mute me 14:47:08 Detlev should now be muted 14:47:22 Katie: we need to identify what was accessible and what wasn't, conformance claim will point to what has been evaluated 14:47:46 q+ 14:48:05 ack me 14:48:05 q+ 14:48:17 ack ryla 14:48:20 K: dependent of company to say: we will be compliant or not. For websites it is important to be precise 14:48:50 D: can you then leave out parts of the website? 14:49:47 D: in a application you couldn't conform because there are too much options to choose 14:50:22 Zakim, mute me 14:50:22 Detlev should now be muted 14:50:23 q? 14:50:37 Katie: yes, if you don't evaluate the whole page you can't claim anything 14:51:32 Peter: some website parts are highly dynamics, different data may give different pages and different outcomes of an evaluation 14:53:37 Peter: If the application is too big, the application may be changed while testing 14:54:40 Eric: we have to define boundaries in dynamic websites/applications 14:55:10 Eric: we will focus on a ready product, which we will evaluate 14:55:48 Sorry have to leave early 14:55:57 -Katie 14:56:44 q? 14:56:46 q+ 14:56:48 Peter: in reporting we can introduce terms/adjectives separate from conformance (f.e. substantial conformance) 14:56:50 ack korn 14:57:44 thins something like 'substantial conformance' would be a useful concept 14:59:11 ack me 15:00:54 shadi: if in testing things change, how can determine accessibility, in the documentation y/n is a minimum, but there is optional additional performances scores (section 5d) 15:02:54 eric: new methodology will be up soon (tuesday), 15:03:00 -Kathy 15:03:35 Eric: more discussion on wrinkles proposed by Peter 15:03:50 Zakim, unmute me 15:03:52 Thank--bye 15:04:06 bye 15:04:08 ok 15:04:12 ericvelleman has left #eval 15:04:19 MartijnHoutepen has left #eval 15:04:30 MartijnHoutepen should no longer be muted 15:04:42 -Sarah 15:05:03 -Don 15:05:07 -Mike 15:05:15 -Moe 15:05:21 -Peter 15:05:23 -vivienne 15:05:33 -Shadi 15:05:59 -Eric 15:06:01 -Detlev 15:06:31 -MartijnHoutepen 15:06:36 korn has left #eval 15:06:37 WAI_ERTWG(Eval TF)10:00AM has ended 15:06:41 Attendees were +1.978.443.aaaa, +31.30.239.aabb, Kathy, Shadi, vivienne, +1.520.271.aacc, Don, +31.30.239.aadd, Eric, MartijnHoutepen, +1.978.562.aaee, Moe, +49.404.318.aaff, 15:06:44 ... Detlev, +1.517.353.aagg, +1.517.432.aahh, Sarah, Mike, Peter, +1.703.272.aaii, Katie 15:13:28 Moe has left #eval 15:45:40 tarckbot, end meeting 15:45:51 trackbot, end meeting 15:45:51 Zakim, list attendees 15:45:51 sorry, trackbot, I don't know what conference this is 15:45:59 RRSAgent, please draft minutes 15:45:59 I have made the request to generate http://www.w3.org/2012/04/05-eval-minutes.html trackbot 15:46:00 RRSAgent, bye 15:46:00 I see no action items