20:03:53 RRSAgent has joined #wai-wcag 20:04:45 +Michael_Cooper 20:05:39 MichaelC has joined #wai-wcag 20:06:19 http://www.w3.org/Consortium/Patent-Policy-20040205/ 20:06:23 hi Michael 20:08:20 +Paul_Bohman 20:08:47 agenda+ ian's proposal 20:10:15 agenda+ Confirm consensus from last week (no conformance level lower than minimum (e.g., A-), should not prevent peopel from reporting intermediat eprogress. 20:10:27 agenda+ process claims? 20:10:42 agenda+ formal conformance statements between levels? 20:10:43 +Loretta_Guarino_Reid 20:10:58 agenda+ Definition of Levels? 20:11:05 zakim, take up item 1 20:11:05 agendum 1. "ian's proposal" taken up [from wendy] 20:13:17 zakim, who's making noise? 20:13:21 (are others hearing echo?) 20:13:29 wendy, listening for 10 seconds I could not identify any sounds 20:13:32 (nope) 20:13:34 ? 20:14:20 MattSEA has joined #wai-wcag 20:14:32 gregg summarizes discussion form last week (scribe missed :\ dealing w/other stuff) 20:14:53 zakim, close this item 20:14:53 agendum 1 closed 20:14:54 I see 4 items remaining on the agenda; the next one is 20:14:55 2. Confirm consensus from last week (no conformance level lower than minimum (e.g., A-), should not prevent peopel from reporting intermediat eprogress. [from wendy] 20:15:18 zakim, take up item 2 20:15:18 agendum 2. "Confirm consensus from last week (no conformance level lower than minimum (e.g., A-), should not prevent peopel from reporting intermediat eprogress." taken up [from 20:15:21 ... wendy] 20:16:05 level lower than minimum? 20:16:39 no please :( otherwise what we make: pkzip-wcag ? 20:17:42 GVAN has joined #wai-wcag 20:17:50 q? 20:17:57 some organizations feel unlikely to meet minimum and suggested A- 20:18:04 related to scoping issue 20:18:06 ack Loretta 20:18:18 q+ 20:18:33 also, related to aggregation, number of pages, and how often content updated 20:18:40 ack Tom 20:19:02 if these organization don't meet minimum, they don't declare conformance... why if they are unable to make accessible web site we need to agree to give them possibility to put a conformance logo? 20:19:23 there is nothing stopping them from saying, "we don't meet minimum, but here' what we've done" 20:19:27 ack Microsoft 20:19:33 ack [Microsoft] 20:19:41 zakim, [Microsoft] is Mike_Barta 20:19:41 +Mike_Barta; got it 20:19:46 if minimum is not testable, then if site more than 100K suddently, doesn't bother? 20:19:59 testable - someone can verify it. 20:20:17 -Roberto_Ellero 20:20:44 consensus: we do not want to define a "lower than minimum" conformance claim (e.g., A-) 20:20:53 q+ 20:21:03 q? 20:21:17 ack Tom 20:21:20 ack Tom_Croucher 20:21:24 +??P1 20:21:31 zakim, ??P1 is Roberto_Ellero 20:21:31 +Roberto_Ellero; got it 20:21:46 zakim, mute me 20:21:46 sorry, rellero, I do not see a party named 'rellero' 20:21:50 we should actively encourage people to do as much as possible. 20:21:54 zakim, I am Roberto_Ellero 20:21:54 ok, rellero, I now associate you with Roberto_Ellero 20:22:00 zakim, mute me 20:22:00 Roberto_Ellero should now be muted 20:22:04 "do as much as you can & write that down" 20:22:29 hand up 20:22:39 ack David 20:23:04 don't encourage people calim conformance below min. level, but we don't discourage people to report progress between levels. 20:23:09 give people the option. 20:23:15 "give them permission" 20:23:17 ack John 20:23:18 so these make a conformance claim to single guidelines, not to a conformance level? 20:23:42 actively encourage report progress. perhaps provide a tool that they can use to make it easy to make comparisons. 20:23:56 ack bcaldwell 20:24:14 encourage claims via metadata (that implies intermediate steps), not useful to encourage what you did if not in metadata. 20:24:34 anyone feel that we should not encourage people to report in between. 20:24:40 hard enough to get people to report levels. 20:25:35 publicize progress between levels and further encourage them to do it in metadata. 20:25:41 q+ to ask clarification on john's q 20:25:49 ack wendy 20:25:49 wendy, you wanted to ask clarification on john's q 20:27:14 last week talked about vpat, "we support this criterion" - could go into metadata. also human description of what we've done. 20:27:15 ack mike 20:27:44 are we specifying a metadta scheme? or metadata policy? is it part of conformance? or just a good idea to do something like this? 20:27:54 a "good idea" - not must. not success criteria. 20:28:02 ben has joined #wai-wcag 20:28:43 metadata: if people were in the stream of content they are emitting, would make aggregation problem simpler. 20:29:01 then aggregated content could aggregate conformance info. makes it clearer about legal liability. 20:29:12 specifying communication means like that could be messy. 20:29:28 vpat would be one mechanism to publicize what you have done. 20:29:36 Like in P3P? 20:29:38 vpat is 508-specific 20:29:41 q+ 20:30:04 ack Tom_Croucher 20:30:23 perhaps we recommend that someone develop tools 20:30:31 yep this could be good 20:30:47 EARL is ideal format. 20:30:54 q+ EARL update 20:30:56 -Roberto_Ellero 20:31:13 useful to say something specific is specified to avoid interoperability problems. 20:31:18 q- 20:31:23 ack EARL 20:31:25 :) 20:31:27 :) 20:31:35 ack update 20:32:03 +??P1 20:32:04 zakim, ??P1 is Roberto_Ellero 20:32:04 +Roberto_Ellero; got it 20:32:18 zakim, I am Roberto_Ellero 20:32:18 ok, rellero, I now associate you with Roberto_Ellero 20:32:22 zakim, mute me 20:32:22 Roberto_Ellero should now be muted 20:32:36 We encourage people to document and publicize progress between conformance levels. Further we encourage them to do so via metadata when and as it is possible. 20:34:01 zakim, close this item 20:34:01 agendum 2 closed 20:34:02 I see 3 items remaining on the agenda; the next one is 20:34:03 3. process claims? [from wendy] 20:34:08 zakim, take up item 3 20:34:08 agendum 3. "process claims?" taken up [from wendy] 20:35:31 q+ 20:35:50 ack Tom_Croucher 20:36:13 shouldn't we say "look at ATAG" and that will guide you? 20:36:24 ATAG are authoring tool. we're talking about web apps. 20:36:31 it's a web app behaving as an authoring tool. 20:36:54 +??P13 20:36:57 if Web App generate contents, these are authoring tools :) 20:37:18 q? 20:37:20 q+ matt 20:37:28 ack David 20:37:52 learning from 508, can we encourage the huge sites to push the responsibility of the content onto their service providers. 20:37:59 e.g., reuters, and other news agencies. 20:38:35 ack matt 20:38:47 in ATAG 2.0, guideline 1 is "make interface accessible" 20:38:56 ISO TS/16071 20:39:06 working on ISO 16071 is benchmark for accessibility of s/w apps 20:39:18 for web apps, we'll point to wcag 20:39:32 ISO/TS, not ISO :) 20:39:45 will atag cover all dynamically generated content as well as all web apps? 20:40:05 atag addresses the interface of the input mechanism. the output is how test quality of tools. 20:40:10 it's output must conform to wcag 20:40:29 how does someone test output when content to output doesn't exist at time of test? 20:40:37 atag has stuff for templates and collateral built into wcag 20:40:55 if producing content from a template, that template musst be accessible ala wcag 20:40:58 ack loretta 20:41:48 pushing the requirement to contributor, but conerne that needs a way to make sure that contractor has fulfilled obligation. thus, need a way to test. 20:41:50 ack mike 20:42:13 zakim, [IBM] is Andi 20:42:13 +Andi; got it 20:42:16 atag is covering the tool is accessible, output conform to wcag. if the tool is using template of productin, it's still content the author is producing 20:42:44 if using something at build-time (fed in from diff system), the only testable way to handle is "person providing the feed is responsible for claim about feed" 20:42:48 ack [IBM] 20:42:49 q+ 20:43:04 our mailing list is good e.g., of web app that takes data from somewhere and presents. 20:43:23 also a Blog is an authoring tool, because it publish content input by an user? 20:43:38 also forum, chat, etc.? 20:43:44 1.3 "struct sep from presenation" - "derive programmatically" 20:43:57 q+ 20:44:08 mailing list is flat text. mailing list doesn't conform 20:44:19 it takes html markup out of messages 20:44:55 how do we apply this atag discussion to the mailing list discussion? 20:45:16 ack gvan 20:45:23 ack matt 20:45:41 not much of a stretch to call a mailing list an authoring tool. however, wouldn't. 20:45:55 the intent of posting to mailing list is not to create web content, it is ancillary. 20:45:56 q+ 20:46:45 it isn't intended to be created as web content. thus, person creating web content is not using an authoring tool. if that the case, atag would apply to mail clients or anything that has a text area that could end up on the web. 20:47:03 question is: is the archiving tool an authoring tool? similar to aggregator issue. 20:48:12 ack gvan 20:48:15 q+ to talk about ATAG and conversion tools 20:48:43 ack andi 20:48:49 ack mike 20:49:24 if you include something that you didn't author, you can only say it is accessible if the thing you include claims it is accessible. 20:49:29 q+ 20:50:02 in most cases, have a contract. if they claim conformance and don't, then should not be afraid of user suing, should be afraid of aggregator suing them. 20:50:16 you are responsible to use accessible content and create accessible content. 20:50:26 An important problem about backoffice is that it is necessary to be able to use also without js support 20:50:28 ack matt 20:50:28 MattSEA, you wanted to talk about ATAG and conversion tools 20:50:31 and the problem returns with backoffice :) 20:51:01 atag 1 has "converstion tools" 20:51:07 atag 2 "indirect authoring functions" 20:51:11 matt reads from draft 20:51:17 (could you put uri of what you read?) 20:52:10 only 4 cps in atag 1 that apply to conversion tools in atag 1. (since so limited) 20:52:15 (tools are so limited) 20:52:30 likely more applicable to wcag as a web app (e.g., of mailing list) 20:52:33 q? 20:53:19 atag is wcag-checking and repair+the user interface to prompt the author. 20:53:29 if there is no prompting, then value of atag is limited. 20:54:19 (about js support in backoffice) Even if the embedded editors (textarea, object) actually work only with recent versions of the browser, then the js support is less relevant than browser compatibility 20:54:58 you can only claim the lowest level of conformance of the materials you accept. 20:55:11 i.e., could not claim level 2 if 3rd party content on your site that only meets level 1 20:55:15 q? 20:55:45 "synthetic" falls between the cracks of atag and wcag. 20:56:05 if have a tool that converts word docs to html, should be covered by wcag? 20:56:09 b/c of the output. 20:56:31 conversion tool type in atag that uses microsoft word as an example. 20:56:37 and there are techniques 20:56:46 in cut&paste? 20:56:48 the user interface should meet atag, and output should meet wcag 20:56:52 or as an application? 20:57:15 reiterate in wcag that when we say 'authored' don't necessarily mean notepad. if author includes things from another source, other source should make assertion. 20:57:24 q? 20:58:00 -Matt 20:58:08 ack ben 20:58:25 the flexibility that we allow for scoping is important. 20:58:46 scope: can w3c claim that mails sent to mailing list is not accessible, but archives are conforming? 20:59:15 "we are accessble but x, y are not accessible" 20:59:23 for "user interface" intend also the HTML page content in a backoffice? 20:59:24 scope in such a way that can exclude content that have no control over. 20:59:27 q+ 21:00:22 ack mike 21:00:29 nabe has joined #wai-wcag 21:00:29 ack andi 21:01:10 if have a portal, portlet is a mail app, can't say that it is wcag compliant. 21:01:24 it's a web app 21:01:32 it's an aggregator question 21:01:35 +??P7 21:03:16 ack wendy 21:03:49 ack john 21:04:32 we can't recover intent, can't make it part of a test. 21:05:02 conformance claims between levels? 21:05:19 q+ 21:05:25 who feels we should have conformance claims in between? 21:05:26 ack Tom_Croucher 21:05:54 talked earlier about being open about what done between levels. 21:06:05 that suitable replacement for conformance claim (between levels) 21:06:17 could say "A" but never "A+" 21:07:18 consensus to remove statement in requirement doc that says 21:07:19 http://www.w3.org/TR/wcag2-req/ 21:09:48 C1 - We want to have recognition for accomplishment beyond baseline. 21:10:00 interpret: that we have Level 1, levle2,3 21:10:12 C2 - It is good to have levels of conformance rather than just all or nothing. 21:10:36 seems redundant with C2 21:11:32 s/C2/C1 21:11:38 combine them? 21:11:46 one gives rationale, second says what should be 21:11:54 good idea 21:12:46 c8 21:13:28 delete, " However, there is no agreement on whether, if checkpoints beyond the core set have been implemented, these need to be listed individually, with an "A+" conformance label associated with a list of additional checkpoints, or whether higher "discrete" levels of conformance (double-a, triple-a etc.) should be defined. " 21:13:30 ? 21:13:50 nabe1 has joined #wai-wcag 21:14:09 hi Takayuki 21:14:27 change statement from "If the working group defines a core set of checkpoints which must be satisfied before any conformance claim can be made, these will constitute a minimum level of conformance (e.g. "Level A")." 21:15:20 good morning. Today's discussion is difficult. ;-) 21:15:20 to "the WG will define a core set of criteria that must be satisfied before any conformance claim can be made, these will constitute a min. level of conformance (e.g., "Level A")." 21:15:39 s/criteria/success criteria 21:19:27 consensus statements are to help people coming onboard. keep track of where we have been and where we are. 21:25:37 -Michael_Cooper 21:29:43 action: wendy send proposals to changes in requirements document to the mailing list 21:30:26 consensus to publish consensus items in separate document. link to from home page. 21:31:15 heads up: will be redesigning home page per new WAI activity design. 21:32:06 RRSAgent, make log world-visible 21:32:47 http://www.w3.org/2004/04/08-wai-wcag-irc 21:34:37 ack David 21:35:00 perhaps separating conformance criteria (rules we set for ourselves) from definition of levels of conformance. 21:35:06 -Andi 21:35:09 currently, combined and confusing for people not involved in the process 21:36:01 everyone think about this is where we'll start next time 21:36:08 then, start out scope, before can clean up 1.2 21:36:51 -Paul_Bohman 21:36:52 -??P13 21:36:54 -Mike_Barta 21:36:54 good night! 21:36:55 -Loretta_Guarino_Reid 21:36:55 bye 21:36:56 -Tom_Croucher 21:36:57 -Wendy 21:36:57 -John_Slatin 21:36:57 Happy Easter! http://protty.it/images/prottybonsai1_JPG.jpg 21:36:58 -David_McDonald 21:36:59 -Ben_and_Gregg 21:37:00 -Roberto_Scano 21:37:02 -Bengt_Farre 21:37:25 -??P7 21:37:32 -Roberto_Ellero 21:37:33 -JasonWhite 21:37:34 WAI_WCAG()4:00PM has ended 21:37:35 Attendees were Roberto_Scano, Bengt_Farre, Wendy, Roberto_Ellero, John_Slatin, Tom_Croucher, JasonWhite, Matt, David_McDonald, Ben_and_Gregg, Michael_Cooper, Paul_Bohman, 21:37:37 ... Loretta_Guarino_Reid, Mike_Barta, Andi 21:38:09 Are you in summer time? 21:38:40 yes. u.s. switched to summer time on sunday, europe the week before. 21:39:15 Wow. so telecon starts at 5 am in Japan. 21:39:22 wow :) 21:39:35 :-) 21:39:43 good night from Venice :) 21:40:38 rscano has left #wai-wcag