12:21:14 RRSAgent has joined #eo 12:21:14 logging to http://www.w3.org/2007/04/20-eo-irc 12:21:19 zakim, this will be eowg 12:21:19 ok, shawn; I see WAI_EOWG()8:30AM scheduled to start in 9 minutes 12:21:27 chair: Judy 12:21:35 meeting: WAI EOWG 12:21:44 shadi has joined #eo 12:22:16 agenda: http://lists.w3.org/Archives/Public/w3c-wai-eo/2007AprJun/0013.html 12:22:41 Henny has joined #eo 12:22:47 ok, thanks shawn 12:22:53 scribe: shadi 12:23:24 Jack has joined #eo 12:26:46 WAI_EOWG()8:30AM has now started 12:26:53 +doyle 12:27:46 +Judy 12:28:57 zakim, code? 12:28:57 the conference code is 3694 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), shadi 12:29:10 Regrets: Helle 12:29:29 +Jack 12:30:01 +Andrew_Arch 12:30:33 +Shawn 12:30:43 +Shadi 12:30:47 Sylvie has joined #eo 12:31:06 agenda? 12:31:30 judy has joined #eo 12:31:34 +Loughborough 12:32:21 hello all I will try to connect to EOWG bridge with another phone number and another phone service so don't be surprised if it does not work properly. 12:32:23 +Henny_Swan 12:33:22 zakim, who's here? 12:33:22 On the phone I see doyle, Judy, Jack, Andrew_Arch, Shawn, Shadi (muted), Loughborough, Henny_Swan 12:33:24 On IRC I see judy, Sylvie, Jack, Henny, shadi, RRSAgent, Zakim, shawn, Andrew 12:34:01 shadi has changed the topic to: agenda: http://lists.w3.org/Archives/Public/w3c-wai-eo/2007AprJun/0013.html 12:34:54 +??P8 12:35:18 Topic: WCAG 2.0 Conformance section, Editor's Draft 12:35:27 http://www.w3.org/WAI/GL/WCAG20/#conformance 12:35:41 Alan has joined #eo 12:35:42 zakim, ??p8 is really Sylvie 12:35:42 +Sylvie; got it 12:35:43 zakim, ??P8 is Sylvie 12:35:44 I already had ??P8 as Sylvie, Andrew 12:36:35 +[IPcaller] 12:37:13 jb: first editorial pass of the guidelines from the WCAG WG 12:37:42 +Pat_Case 12:37:57 jb: Shawn and Judy have been coordinating with WCAG WG on how to make things even clearer 12:37:58 zakim, Pat_Case is Justin 12:37:58 +Justin; got it 12:38:34 jb: for example, would it be possible to take out some of the content from the conformance section? 12:38:55 ...to keep it brief and less complex to read 12:39:29 jb: want to compare the conformance section to other W3C publications 12:40:01 jb: after people have read the conformance section, how much do they understand? 12:41:01 hs: after reading, wasn't really sure understood what it exactly meant 12:41:01 Harvey has joined #eo 12:41:15 ...would be good t provide a summary and reduce complexity 12:41:26 aa: generally understood it 12:41:52 jb: would you be able to describe it to somebody? 12:41:57 jw: not really 12:42:07 aa: probably yes 12:42:15 jb: how would you describe it? 12:43:18 +Bingham 12:43:27 -Bingham 12:43:30 wl: conformance means meeting the success criteria 12:43:46 aa: there may be alternatives 12:44:01 +Bingham 12:44:16 [you do need to conform to the success criteria; you don't need to conform to the techniques; and there may be other ways that you can conform, too.] 12:45:58 hs: looks clear 12:46:32 q+ to remove the ", too" 12:47:16 q+ 12:47:58 jt: kind of understood how to do exceptions to the techniques, but sounds difficult and wouldn't want to do it 12:48:25 as: not sure if it is easily readable by non-native speakers 12:48:27 q- 12:48:32 ack alan 12:49:24 as: would describe conformance model as different technologies are supported, different ways to reach conformance 12:49:36 as: wondering why baseline is not mentioned? 12:49:44 slh: has been removed 12:50:39 Mark has joined #eo 12:51:10 jt: 12:51:30 slh: have additional external materials to explain the specifics 12:52:23 jb: when people are looking at what's normative vs what's external, what do people feel? 12:52:35 as: user agents 12:53:32 aa: additional information should suggest alternatives 12:53:40 jb: advisory techniques 12:54:43 wl: for each success criteria there are techniques, but that's not a normative definition of conformance 12:55:18 slh: approach is to just have the basic normative information in this document 12:55:32 ...the other document has examples and additional information 12:55:46 ...maybe even different sections to address different audience 12:56:38 jb: some W3C publications split up different parts of the documents into different chunks 12:56:52 q+ to ask (later when other topics are done) about "Accessibility-supported Content Technologies (AsCT)" 12:57:08 ...for example a condensed part of the normative section, then additional information 12:57:47 jb: Justin asked who the audience is, let's talk about that 12:58:26 ...what are the audiences for "conformance" -who and how will they use it 12:58:38 wl: people who will write about the guidelines 12:59:10 ack shawn 12:59:10 shawn, you wanted to ask (later when other topics are done) about "Accessibility-supported Content Technologies (AsCT)" 12:59:31 slh: web developer who wants to claim conformance 12:59:51 slh: policy maker who wants to decide conformance level 13:00:35 slh: users (particularly people with disabilities) who want to know what a conformance statement means 13:01:04 q+ to ask (later when other topics are done) about "Accessibility-supported Content Technologies (AsCT)" 13:02:41 jb: would it help to add a brief summary up-front? 13:04:02 wl: seems like there was a scope-creep, the section grew 13:04:33 jb: what about examples? 13:04:41 ds: wouldn't help 13:04:57 jt: depends on the audience 13:05:23 The challenge for cpolicymakers is how to EASILY figure out the conformance level that's right for a given piece of content, and how to operationlize that. Since a conformance statement means sticking your neck out to say "this is accessible", many people want to stick their neck out only as far as it needs to go. that's at least one audience 13:05:30 -doyle 13:05:54 jb: doesn't have to be necessarily within the same document 13:06:05 zakim, who is here? 13:06:05 On the phone I see Judy, Jack, Andrew_Arch, Shawn, Shadi (muted), Loughborough, Henny_Swan, Sylvie (muted), Alan, Justin, Bingham 13:06:07 On IRC I see Mark, Harvey, Alan, judy, Sylvie, Henny, shadi, RRSAgent, Zakim, shawn, Andrew 13:06:32 +??P0 13:06:47 zakim, ??p0 is really doyle 13:06:47 +doyle; got it 13:08:05 * sorry 13:08:09 s/The challenge for cpolicymakers is how to EASILY figure out the conformance level that's right for a given piece of content, and how to operationlize that. Since a conformance statement means sticking your neck out to say "this is accessible", many people want to stick their neck out only as far as it needs to go. that's at least one audience/ 13:08:35 Jack has joined #eo 13:12:43 as: potential confusion with respect to conformance levels and techniques 13:14:23 q- Judy 14:32:08 Henny_ has joined #eo 14:32:12 aa: belongs in understanding document 14:32:29 ds: think it is helpful information 14:33:08 slh: should be clear in all other supporting documents, not necessarily here 14:34:13 s/what do people think of "partial conformance"/what do people think of "partial conformance"? Content that conforms to WCAG 1.0 14:34:19 jb: thanks for the discussion, and especially the written comments in advance 14:35:02 jb: probably no meeting next week, likely no updated material 14:36:25 for april 27th: 14:36:43 andrew: prefer no meeting due to other weekend activities 14:36:50 -Justin 14:36:56 -doyle 14:36:57 -Loughborough 14:36:58 -Judy 14:37:00 -Sylvie 14:37:13 -Shadi 14:37:27 -Andrew_Arch 14:37:39 -Jack 14:37:47 -Shawn 14:37:49 WAI_EOWG()8:30AM has ended 14:37:50 Attendees were doyle, Judy, Jack, Andrew_Arch, Shawn, Shadi, Loughborough, Henny_Swan, Sylvie, Alan, Justin, Bingham 14:38:12 zakim, bye 14:38:12 Zakim has left #eo 14:38:21 rrsagent, make logs world 14:38:25 rrsagent, make minutes 14:38:25 I have made the request to generate http://www.w3.org/2007/04/20-eo-minutes.html shadi 14:38:27 rrsagent, make logs world 14:54:08 shawn has left #eo