20:46:57 RRSAgent has joined #wai-wcag 21:01:12 +Avi 21:01:16 -Michael_Cooper 21:01:17 +Michael_Cooper 21:01:39 +JasonWhite 21:01:43 +Yvette_Hoitink 21:01:45 +Wendy 21:01:58 zakim, who's on the phone? 21:01:58 On the phone I see Michael_Cooper, Avi, Yvette_Hoitink, JasonWhite, Wendy 21:03:08 +??P3 21:03:11 zakim, ??P3 is Ben 21:03:11 +Ben; got it 21:04:13 +[IBM] 21:04:42 Andi has joined #wai-wcag 21:04:55 +Becky_Gibson 21:05:01 +??P7 21:05:14 zakim, who's on the phone? 21:05:14 On the phone I see Michael_Cooper, Avi, Yvette_Hoitink, JasonWhite, Wendy, Ben, [IBM], Becky_Gibson, ??P7 21:05:17 Becky has joined #wai-wcag 21:05:19 zakim, mute ??P7 21:05:19 ??P7 should now be muted 21:05:19 zakim, ??P7 is bengt_Farre 21:05:20 +bengt_Farre; got it 21:05:38 ok it was muted in this end 21:05:41 +[Microsoft] 21:05:52 zakim, [IBM] is Andi 21:05:52 +Andi; got it 21:05:54 zakim, Ben is Ben_and_Gregg 21:05:54 +Ben_and_Gregg; got it 21:06:03 zakim, [Microsoft] is Mike 21:06:03 +Mike; got it 21:06:18 +Loretta_Guarino_Reid 21:06:53 Techniques Task Force Summary by Michael 21:06:59 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2004OctDec/0308.html 21:07:13 mc> getting ready to publish new WD's of HTML, CSS, and script techniques next week 21:07:26 agenda+ conformance - http://lists.w3.org/Archives/Public/w3c-wai-gl/2004OctDec/0235.html 21:07:27 mc> test files raising questions about techniques 21:07:30 gregg has joined #wai-wcag 21:07:38 agenda+ 2.4 - http://lists.w3.org/Archives/Public/w3c-wai-gl/2004OctDec/0259.html 21:07:49 agenda+ 2.5 - http://lists.w3.org/Archives/Public/w3c-wai-gl/2004OctDec/0268.html 21:08:00 agenda+ 1.4 - http://lists.w3.org/Archives/Public/w3c-wai-gl/2004OctDec/0248.html 21:08:13 agenda+ 1.1/1.2 - http://lists.w3.org/Archives/Public/w3c-wai-gl/2004OctDec/0307.html 21:08:33 mc> the vote on techniques from the Face to Face meeting was useful in highlighting problem areas 21:08:40 zakim, take up item 1 21:08:40 agendum 1. "conformance - http://lists.w3.org/Archives/Public/w3c-wai-gl/2004OctDec/0235.html" taken up [from wendy] 21:08:46 mc> plan to use that approach in the future 21:10:11 gv> conformance issues proposals 21:10:11 q+ 21:10:30 gv> Gregg will post final version to list 21:11:33 gv> proposes creating a document that describes our rationale for everything we did 21:11:46 gv> references back to bugs 21:13:41 q+ to say, "top level URI" 21:13:54 or base 21:14:12 gv> what is the term to describe www.something.com/directory/* ? 21:14:18 q? 21:14:20 +??P10 21:14:20 wc> top level URI? 21:14:28 yh> it's a folder 21:14:41 parital path 21:14:46 partial 21:14:53 wc> base, relative URIs 21:14:57 q+ to say I'm looking in XPointer spec... 21:15:18 q- 21:15:26 David_MacDonald has joined #wai-wcag 21:15:33 Thats me 21:15:33 wc> can't use top level because that refers to only the very top level and can't be used for branchess that start in a sub-directory 21:15:41 on the phone new person 21:15:46 q- 21:15:54 zakim, ?? is DAvid 21:15:54 +DAvid; got it 21:16:02 zakim, who's making noise? 21:16:12 bc> suggests changing "provisions" to "criteria" 21:16:15 Yvette, listening for 10 seconds I heard sound from the following: Ben_and_Gregg (50%), Andi (15%), Loretta_Guarino_Reid (4%) 21:16:19 no objections 21:16:37 zakim, mute me 21:16:37 sorry, David_MacDonald, I do not see a party named 'David_MacDonald' 21:16:41 bc> consistent use of delivery unit, not delivered unit 21:16:49 bc> need definition of delivery unit 21:16:59 wc> will use the one from the device independent WB 21:17:03 zakim DAvid is David_MacDonald 21:17:06 WB should be WG 21:17:19 zakim, DAvid is David_MacDonald 21:17:19 +David_MacDonald; got it 21:17:21 q? 21:17:29 ack b 21:17:31 http://www.w3.org/TR/di-gloss/#def-delivery-unit 21:17:32 zakim, mute me 21:17:32 David_MacDonald should now be muted 21:17:38 ack j 21:17:43 zakim, mute me 21:17:43 Yvette_Hoitink should now be muted 21:17:59 jw> agrees that we need a document that describes rationale for all decisions 21:18:28 jw> regarding URIs, clarifies proposals with regard to URIs 21:18:41 should reference W3C specification 21:20:20 gv and jw> specific wording "URI or set of URIs defined by a regular expression" 21:21:36 gv> continues "according to XML ... document" 21:21:58 Jason to provide specific proposal 21:24:21 lg> sent memo to Oliver Thereaux asking what he meant by "adding a conformance disclaimer" 21:24:22 http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=476 21:24:32 lg> response posted to bug 476 21:27:53 http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=837 21:28:49 q+ 21:28:53 gv> do we want to rethink our decision that techniques are not normative in light of our baseline decision 21:28:55 ? 21:30:05 no consensus to normative techniques at this time 21:31:58 q+ to say "metadat" 21:32:14 ack b 21:32:17 ack w 21:32:17 wendy, you wanted to say "metadat" 21:32:17 q+ 21:32:31 gv> with regard to machine readable conformance claims, we think they are a good idea but we don't think we can require them 21:33:06 wc> will have proposal soon on the type of metadata that is useful to provide but it will not be a level 1 requirement. 21:34:03 s/will/may not - not sure what liddy and jutta are thinking re: level for a proposed criterion related to providing metadata for content adaptation 21:34:07 ack d 21:34:51 dm> back to site map, reason may be to make site navigable - provides easy access to all links 21:35:26 zakim, mute me 21:35:26 David_MacDonald should now be muted 21:35:33 q+ to ask "why a-aa-aaa when we already have lvl 1, 2,3" 21:36:04 zakim, unmute me 21:36:04 Yvette_Hoitink should no longer be muted 21:36:21 gv> should we use AAA or Triple-A 21:37:01 yh> why do we have Level 1, 2, and 3 and then use something different (A, AA, and AAA) for conformance claim 21:37:24 ack y 21:37:24 Yvette, you wanted to ask "why a-aa-aaa when we already have lvl 1, 2,3" 21:37:31 ack j 21:38:01 zakim, mute me 21:38:01 Yvette_Hoitink should now be muted 21:38:44 -JasonWhite 21:39:06 gv> proposes using Triple-A for now to be consistent with other guidelines 21:39:12 group agrees 21:40:46 +JasonWhite 21:43:07 mb> disagrees with proposed resolution of 1076 21:43:24 q? 21:43:31 ack m 21:43:31 agreement to add paragraph in 1076 recommendation # 1 21:43:49 ack Mike 21:43:50 ack j 21:44:17 jw> what about messages or user interface that an application might generate that would not have a URI? 21:46:18 ack j 21:46:39 jw> not different from case where you have multiple versions of content that are retrieved from a URI 21:47:20 q+ to say "content negotiation" 21:47:25 zakim, unmute me 21:47:25 Yvette_Hoitink should no longer be muted 21:47:54 q- 21:48:37 gv> create a bug - what about content that is not tied to a specific URI? 21:49:09 zakim, mute me 21:49:09 Yvette_Hoitink should now be muted 21:50:12 ack j 21:51:09 jw> both Level 1 and the first part of Level 2 are for user agent support 21:51:32 gv> create a bug - explain clear delineation for when something goes in Level 1 or 2 for user agent support 21:52:48 q+ 21:52:59 q+ to say, "what is significant?" 21:53:02 zakim, unmute me 21:53:02 Yvette_Hoitink should no longer be muted 21:53:44 yh> what should conform to which level of WCAG should be for policy makers and should not be in the guidelines themselves 21:53:49 andi agrees with yh 21:55:28 gv> WCAG 2.0 is a standard of accessibility. It is up to others to determine when to implement. 21:55:48 zakim, unmute me 21:55:48 David_MacDonald should no longer be muted 21:55:53 zakim, mute me 21:55:53 Yvette_Hoitink should now be muted 21:55:55 q- 21:56:29 q= 21:56:33 q+ 21:57:39 bc> should we use priority to be consistent with other guidelines? 21:58:17 gv> agree to consider 21:58:23 zakim, unmute me 21:58:23 Yvette_Hoitink should no longer be muted 21:58:23 ack y 21:58:35 ack d 21:58:42 zakim, mute me 21:58:44 Yvette_Hoitink should now be muted 21:59:15 dm> will some people thing that WCAG 1.0 are "beginner" guidelines and WCAG 2.0 are "advanced"? 21:59:32 ack d 21:59:40 gv> with other specifications such as HTML, version number means the latest version of the spec 21:59:53 wc> recommends covering in transitional documents and education 22:00:30 proposed edits on conformance will go into the next draft 22:00:50 ack j 22:01:09 jw> in addition to considering "priority" as terminology, also consider using "provision" instead of "success criteria" to align with UAAG terminology 22:01:37 Guideline 2.4 summary 22:01:58 +Mike_Barta 22:02:40 q+ 22:02:51 zakim, close item 1 22:02:51 agendum 1 closed 22:02:52 I see 4 items remaining on the agenda; the next one is 22:02:53 2. 2.4 - http://lists.w3.org/Archives/Public/w3c-wai-gl/2004OctDec/0259.html [from wendy] 22:02:58 zakim, take up item 2 22:02:58 agendum 2. "2.4 - http://lists.w3.org/Archives/Public/w3c-wai-gl/2004OctDec/0259.html" taken up [from wendy] 22:03:20 q+ to ask about "perceivable unit in level 3 #4" 22:04:06 ack a 22:04:25 asw doesn't like word, "tools" better to use "mechanisms" as with other guidelines 22:04:37 asw don't like the level 1 criterion that is the same as another one. what is the purpose? 22:04:53 gv purpose: if you don't have a level 1 criterion, the entire guideline disappears from a list of level 1 criteria 22:05:17 gv this is a 2nd good reason for doing the level 1 criterion (i.e., multiple reasons for doing this task) 22:05:45 q+ to say "agree with andy" 22:05:52 ack w 22:05:52 wendy, you wanted to ask about "perceivable unit in level 3 #4" 22:06:11 wc> agree with Andi about use of "mechanisms" instead of "tools" 22:06:21 consensus 22:06:47 wc> L3 SC 4 uses term "perceivable unit". should be "delivery unit" 22:07:00 bc> also in L2 22:07:02 -Mike_Barta 22:07:21 ack j 22:07:55 jw> should remove editorial notes before publication 22:08:22 jw> rest of my comments posted to list do not have to be resolved prior to next draft 22:10:07 wc> should highlight that L1 SC is the same as GL 1.3 and ask for feedback on whether or not this is confusing 22:10:16 jw> recommends shortening 22:10:32 gv> editors will shorten editorial notes and ask reflective questions 22:10:49 ack y 22:10:50 ack y 22:10:50 Yvette, you wanted to say "agree with andy" 22:11:09 yh> supposed to do issue summary for 2.4 and 1.3 22:11:27 yh> plans to make proposal to integrate the two 22:11:43 yh> seems like 1.3 is a technique or success criteria for 2.4 22:12:34 yh> symptom of underlying problem that perhaps these two guidelines should not be two guidelines 22:13:04 q+ 22:13:24 q- 22:14:10 zakim, mute me 22:14:10 Yvette_Hoitink should now be muted 22:14:23 zakim, close this item 22:14:23 agendum 2 closed 22:14:24 I see 3 items remaining on the agenda; the next one is 22:14:25 3. 2.5 - http://lists.w3.org/Archives/Public/w3c-wai-gl/2004OctDec/0268.html [from wendy] 22:14:31 zakim, take up next item 22:14:31 agendum 3. "2.5 - http://lists.w3.org/Archives/Public/w3c-wai-gl/2004OctDec/0268.html" taken up [from wendy] 22:15:02 asw sent proposal just before mtg. 22:15:18 http://lists.w3.org/Archives/Public/w3c-wai-gl/2004OctDec/0326.html 22:15:41 2. If a user error is detected, and suggestions for correction are known 22:15:42 and can be provided without jeopardizing security or purpose, the error is 22:15:44 identified and the suggestions are provided in an accessible form that 22:15:45 meets WCAG 2.0 at Level A. 22:16:13 asw dont think need the clarification, it should be assumed. 22:16:25 gv is the error msg available through the uri 22:16:45 jw if not stated explicitly, and adding it, people iwll try to interpret it as it not needing to conform. 22:17:08 asw then do we need that to every guideline that adds contentt? 22:17:12 q+ to say "confusing" 22:17:28 gv that is a good question 22:17:50 sorry, I need to leave early today 22:17:55 -Becky_Gibson 22:18:10 wac good place for ednote? feedback about if needed or how interpreted? 22:18:15 zakim, unmute me 22:18:15 Yvette_Hoitink should no longer be muted 22:18:33 gv it's a reminder. anyone speak pro or con? 22:18:43 yh agree that it is confusing. 22:18:53 bc leave it as "provided in accessible form" 22:19:07 gv more vague - means, accessible at level 1 or 2? 22:20:56 wac only place we use this is in Guideline 4.2 and talks about conformance to UAAG (not conformance to WCAG) 22:21:36 resolved: remove that phrase 22:21:44 zakim, mute me 22:21:44 Yvette_Hoitink should now be muted 22:22:21 2. If possible for the natural language of the text, an option is provided 22:22:23 to check text entries for misspelled words with suggestions for correct 22:22:24 spellings. 22:22:56 jw there are invalid strings of characters 22:23:21 -Michael_Cooper 22:24:07 jw a more general way to say "spelling"? 22:24:20 asw go into general techniqus? 22:24:22 -Avi 22:26:01 zakim, unmute me 22:26:01 David_MacDonald was not muted, David_MacDonald 22:26:33 gv "misformed" words instead of "misspelled? 22:26:35 zakim, mute me 22:26:35 Yvette_Hoitink was already muted, Yvette 22:26:44 ack y 22:26:45 Yvette, you wanted to say "confusing" 22:26:51 ack m 22:27:34 mb validation could mean spelling as well as other errors 22:27:47 zakim, mute me 22:27:47 Yvette_Hoitink should now be muted 22:27:53 -bengt_Farre 22:28:19 zakim, unmute me 22:28:19 Yvette_Hoitink should no longer be muted 22:28:35 action: add mike's proposal to the issues list 22:28:47 action: add andi to future agenda to discuss other issues with 2.5 22:29:58 zakim, close this item 22:29:58 agendum 3 closed 22:29:59 I see 2 items remaining on the agenda; the next one is 22:30:00 4. 1.4 - http://lists.w3.org/Archives/Public/w3c-wai-gl/2004OctDec/0248.html [from wendy] 22:30:04 zakim, take up next item 22:30:04 agendum 4. "1.4 - http://lists.w3.org/Archives/Public/w3c-wai-gl/2004OctDec/0248.html" taken up [from wendy] 22:30:10 wendy, am I scribing again? 22:30:20 if you would, that would be great. 22:31:12 dm> still need algorithm for color contrast 22:31:23 q+ 22:31:59 ack a 22:32:03 q+ to say "where user input is required for which there is a known set of valid choices, present these choices to the user." 22:32:14 asw there are tools that check color contrast. won't they tell us the algorithm? 22:32:37 gv the values in the formula are the ones most of the tools are using. these are taken from ansi standards. 22:32:51 q- 22:33:04 gv they deal with measurements from the screen not in the content 22:33:59 q+ 22:35:10 dm> one bug deals with enlargeable text size, not appropriate to this guideline 22:35:36 gv> should go in user agent repair category. UA should be able to zoom text even if author has used fixed text size 22:35:52 q+ 22:36:18 wc> recommends adding something about a minimum default size 22:36:43 gv> but if the UA allows you to make it larger, you can just zoom it in 22:37:04 wc> some people use images for certain fonts because the fonts they want to use are not free 22:37:54 gv> add Wendy's comments to this bug (1025), change bug to a different category 22:38:25 q- 22:38:31 q- 22:42:59 david's wording reccs: http://lists.w3.org/Archives/Public/w3c-wai-gl/2004OctDec/0250.html 22:44:13 add a definition of audio contrast and include signal to noise info at end of Davi'd proposal? 22:44:25 resolved: accept david's proposed revisions 22:44:54 jw> would like my documented issues to be take up in the next draft 22:45:43 jw> another issue I didn't raise, there's a not about transcripts for multimedia at level 1 22:47:45 wd and jw will work out which of jw's issues will be picked up and which will wait until later 22:47:54 bc> have we removed multimedia from 1.1? 22:48:05 wc> no. we still use "non-text content" 22:48:39 gv> monomedia with interaction is missing 22:48:56 wc> thought we decided at f-2-f this was part of 4.2 22:49:17 gv> interaction only is part of 4.2. Presentation is part of 1.1 or 1.2 22:50:12 gregg to write an editorial note for 1.2 22:50:47 q+ 22:52:07 add to 1.1, if there is any time-based interaction with audio or video presentation, alternatives have to be synchronized. 22:52:25 -JasonWhite 22:53:04 wc> proposed editorial note for 1.2 that we still have to address monomedia that needs synchronized equivalents 22:54:37 wc> if have multimedia application, captions may not be the way to make it accessible 22:54:54 may be more appropriate to cover under 4.2 22:55:15 bc> left out the need for labeling multimedia. 22:55:19 wc> still in 1.1 22:55:34 wc> definition of non-text content includes multi-media 22:57:07 q+ 22:57:30 zakim, unmute me 22:57:30 Yvette_Hoitink was not muted, Yvette 22:58:39 wc> include note on 1.1 to clarify that it means a label is required for multimedia 22:58:44 ack Jason 22:58:47 ack b 22:59:05 gv> add note on 1.2 that single media with interaction is considered multimedia 23:00:03 gv> example of video where you have to click at a certain time to go to another page 23:00:59 -Mike 23:02:20 yh> concern that 1.1 L1 SC 1 is now applied to multimedia - not all multimedia is functional 23:02:40 wc> note has to be clear that "for multimedia that is functional, ...." 23:03:31 yh> okay under #2. 23:11:30 draft available for editorial review on Wednesday 23:11:49 Yvette, David, Andi, Loretta to help proof the draft 23:12:27 hoping Becky can do the script techniques 23:12:35 Andi has a resource that can help with that if Becky can't 23:12:39 -Loretta_Guarino_Reid 23:12:40 -Andi 23:12:41 -Wendy 23:12:42 -Yvette_Hoitink 23:12:46 Andi has left #wai-wcag 23:14:12 -Ben_and_Gregg 23:14:13 -David_MacDonald 23:14:14 WAI_WCAG()4:00PM has ended 23:14:15 Attendees were Michael_Cooper, Avi, JasonWhite, Yvette_Hoitink, Wendy, Becky_Gibson, bengt_Farre, Andi, Ben_and_Gregg, Mike, Loretta_Guarino_Reid, David_MacDonald, Mike_Barta 23:16:16 Yvette has left #wai-wcag 23:22:36 RRSAgent, make log world 23:29:36 zakim, bye 23:29:36 Zakim has left #wai-wcag 23:29:41 RRSAgent, bye 23:29:41 I see 2 open action items: 23:29:41 ACTION: add mike's proposal to the issues list [1] 23:29:41 recorded in http://www.w3.org/2004/11/11-wai-wcag-irc#T22-28-35 23:29:41 ACTION: add andi to future agenda to discuss other issues with 2.5 [2] 23:29:41 recorded in http://www.w3.org/2004/11/11-wai-wcag-irc#T22-28-47