19:47:37 RRSAgent has joined #wai-wcag 19:47:43 RRSAgent, make log world 19:54:36 rellero has joined #wai-wcag 19:54:48 Hi 19:55:54 WAI_WCAG()4:00PM has now started 19:56:01 +Katie_Haritos-Shea 19:56:53 Yvette_Hoitink has joined #wai-wcag 19:56:58 Hi guys 19:58:48 +[Microsoft] 19:59:06 Typical Microsoft, always trying to beat the competition ;-) 19:59:38 rcastaldo has joined #wai-wcag 19:59:38 +Michael_Cooper 19:59:41 zakim, I am Michael_Cooper 19:59:41 ok, Michael, I now associate you with Michael_Cooper 19:59:47 Hi folks :-) 19:59:58 Ciao 20:00:04 Did anyone receive the agenda? I don't see any items on the list since yesterday afternoon 20:00:14 +Bengt_Farre 20:00:36 Ciao 20:00:40 ciao 20:00:45 -Bengt_Farre 20:00:54 +??P5 20:01:04 zakim, ??P5 is Yvette_Hoitink 20:01:04 +Yvette_Hoitink; got it 20:01:08 +Bengt_Farre 20:01:24 +Wendy 20:01:26 +??P7 20:01:32 zakim, ??P7 is Ben 20:01:32 +Ben; got it 20:01:50 zakim, who's on the phone? 20:01:50 On the phone I see Katie_Haritos-Shea, [Microsoft], Michael_Cooper, Yvette_Hoitink, Bengt_Farre, Ben, Wendy 20:01:51 strange getting code not valid ? 20:02:11 +Bengt_Farre.a 20:02:13 +Kerstin_Goldsmith 20:02:24 btw I am not on yet ... 20:02:46 i bet the 2 bengts are the 2 robertos 20:03:22 yes, without microphone 20:03:41 zakim, Bengt_Farre may be Roberto_Ellero 20:03:41 +Roberto_Ellero?; got it 20:03:49 :-) 20:03:57 zakim, Bengt_Farre.a may be Roberto_Castaldo 20:03:57 +Roberto_Castaldo?; got it 20:04:05 passcode is not valid ? 20:04:06 ok bengt, you're right. you're not here yet. :) 20:04:07 zakim, rellero is Roberto_Ellero 20:04:07 sorry, rellero, I do not recognize a party named 'rellero' 20:04:18 zakim, who's on the phone? 20:04:18 On the phone I see Katie_Haritos-Shea, [Microsoft], Michael_Cooper, Yvette_Hoitink, Roberto_Ellero?, Ben, Wendy, Roberto_Castaldo?, Kerstin_Goldsmith 20:04:33 zakim, [Microsoft] is Mike_Barta 20:04:33 +Mike_Barta; got it 20:04:37 zakim, I am Roberto_Ellero 20:04:37 ok, rellero, I now associate you with Roberto_Ellero? 20:04:50 zakim, who's on the phone 20:04:50 I don't understand 'who's on the phone', Yvette_Hoitink 20:04:59 +JasonWhite 20:05:01 Scribe: Ben 20:05:07 zakim, who's on the phone? 20:05:07 On the phone I see Katie_Haritos-Shea, Mike_Barta, Michael_Cooper, Yvette_Hoitink, Roberto_Ellero?, Ben, Wendy, Roberto_Castaldo?, Kerstin_Goldsmith, JasonWhite (muted) 20:05:14 zakim, mute me 20:05:14 Yvette_Hoitink should now be muted 20:05:19 Topic: TTF summary (Michael Cooper) 20:05:21 agendum 1: techniques task force update from Michael 20:05:26 zakim, mute me 20:05:26 sorry, rcastaldo, I do not see a party named 'rcastaldo' 20:05:44 publishing internal working drafts of CSS, HTML and Gateway tomorrow (Sept. 3) 20:05:54 01zakim, rcastaldo is Roberto_Castaldo 20:06:11 zakim, I am Ben 20:06:11 ok, bcaldwell, I now associate you with Ben 20:06:12 q+ to say "f2f: what month?" 20:06:43 q- 20:06:44 integrating notes and pointers related to open issues in drafts 20:06:48 thx :-) 20:07:08 01zakim, I am Roberto_Castaldo 20:07:14 techniques testing: not much new since last week, but testing is going to become a high priority in the near future 20:07:35 currently working on process for that and developing proposed test resources 20:07:45 -Kerstin_Goldsmith 20:08:00 +Kerstin_Goldsmith 20:08:16 work on additional techniques drafts is beginning 20:08:25 q? 20:08:35 ack Kerstin 20:08:47 +John_Slatin 20:09:00 KG: if you had an xtra person to help w/ techniques a) do you need extra help and b) where is most help needed? 20:09:30 MC: definately need xtra bodies - especially with combing lists and resources for new techniques and issues that have been raised, but not yet processed... 20:09:49 also need help propsing, revising and writing techniques, test files, conducting user-agent tests, etc... 20:10:00 across all technologies? 20:10:31 yes - more help with technologies that have not yet received much attention 20:10:34 +[IBM] 20:10:52 MC: anyone who is looking to help, the TTF can find something for you... 20:11:01 WC: face to face 20:11:11 Andi has joined #wai-wcag 20:11:25 zakim, unmute me 20:11:25 Yvette_Hoitink should no longer be muted 20:11:26 q+ 20:11:27 90% certain to have it in Dublin 19-22 October, first 2 days techniques, then working group 20:11:38 currently looking for hotel alternatives 20:12:43 http://lists.w3.org/Archives/Public/w3c-wai-gl/2004JulSep/0489.html 20:13:22 zakim, mute me 20:13:22 Yvette_Hoitink should now be muted 20:13:31 Topic: 1.2 issue summary 20:14:03 (30 minutes) 20:14:20 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2004JulSep/0528.html 20:15:34 wendy's issue summary and proposal - http://lists.w3.org/Archives/Public/w3c-wai-gl/2004JulSep/0532.html 20:16:13 issues summarized in notes linked to from mail 20:17:05 open issues indicated that there was a great deal of confusion around exceptions in guideline 1.2 20:17:33 some of the exceptions may be part of policy - ex. Telecom Act 1996 20:18:26 q- 20:18:29 ack yvette 20:18:31 q+ 20:18:33 ? do people agree that excptions are confusing? can the be dealt with in policy? 20:18:38 ack John 20:18:39 ack john 20:18:43 zakim, mute me 20:18:43 Yvette_Hoitink should now be muted 20:18:52 JS - agree that exceptions are policy issues 20:19:17 bengt has joined #wai-wcag 20:19:30 JS - might be a good idea to look at legislation in other countries to find comparable examples (perhaps in gateway rather than guidelines, but might be useful) 20:19:32 ack jason 20:20:21 JW - concerned that policy should be kept out of guidelines 20:21:16 ex. anti-descrimination laws in some countries may conflict w/ exceptions in guidelines that address policy 20:21:40 ack andi 20:21:46 JW - agree with wendy's suggestion to keep policy references out 20:22:07 ASW - agree with approach, but how will policy makers know that they should adress this issue? 20:22:15 q+ to say "tech equivalent for policy makers" 20:22:35 ack yvette 20:22:35 zakim, unmute me 20:22:36 Yvette_Hoitink, you wanted to say "tech equivalent for policy makers" 20:22:38 Yvette_Hoitink was not muted, Yvette_Hoitink 20:23:22 YH - we've talked about this before - handle in document that is targeted to policy makers? 20:23:44 zakim, mute me 20:23:44 Yvette_Hoitink should now be muted 20:24:05 WC: f2f in July raised this (policy maker document) and Katie has an action item to dig deeper 20:24:12 q+ 20:24:25 ack jason 20:25:31 JW: 1.) a time-dependent of other multimedia presentation is likely to have a URI - so given the kind of conformance claims we've been discussing, scoping can be addressed in the claim 20:26:17 ack john 20:26:30 2.) we should make it very clear in the guidelines that policy decisions about unjustifiable hardship, diffucult to implement requirements, etc. are (deliberately) not included in guidelines. we need to point that out to policy makers 20:27:23 JS: indication that some nations already have laws on the books regarding what should and should not be captioned might be enough to say to policy makers that this issue need to be addressed and that other policies provide some guidance for how to do that 20:27:24 ack andi 20:27:43 -Kerstin_Goldsmith 20:28:00 ASW: re: jason's comment about scope - scoping is helpful, but only solves the problem if claiming confomrnace is voluntary (you can't scope it out if you're required by law to do it) 20:28:07 +Kerstin_Goldsmith 20:28:20 ASW: not sure policy maker document is still the right thing to do 20:30:33 WC: issues with multimedia that is only available for a short time, phase-in plans 20:30:36 ack Katie 20:32:15 JS: we may need more information about how others handle captioning requirements - where there are already captioning requirments, how are phase-in and exceptions for types of broadcast content handled 20:33:03 KHS: one of the things that was the issue at the f2f was about content aggregation - also an area where policy document could be helpful 20:34:26 action: Katie and Wendy to do some research related to policy for the multimedia guideline 20:34:30 ack jason 20:36:15 JW: problems with setting policy in guidelines are sufficiently significant that we shouldn't go there. providing informative material somewhere is a good idea. factors that contribute to policy (ex. resources) are different that factors that are taken into account for a technical specification 20:37:11 WC: not sure if we created an issue specifically related to creating an informative policy document 20:38:36 q+ 20:38:49 ack jason 20:38:49 WC: 1.2 addresses "interactive" propose that this is covered by guidelines 4.1 and 4.2 - item 5 in the proposal. would like to get input about whether this is covered or not 20:39:04 zakim, mute me 20:39:04 Yvette_Hoitink was already muted, Yvette_Hoitink 20:39:13 JW: objection to classifying something as an application and using that distinction to determine what applies 20:39:47 JW: suggest that we say something about conformance profiles or a specific type of interaction instead of classifying as an application 20:40:04 ack yvette 20:40:41 YH: seems strange to say that a specific type of content should follow other guidelines since all web content should follow all guidelines 20:40:53 -Kerstin_Goldsmith 20:41:28 WC: something like, characteristics that are interactive go with 4.1 and 4.2 and characteristics of content that is multimedia follow 1.2? 20:41:50 +Kerstin_Goldsmith 20:42:27 YH: makes it sound like certain guidelines are specifically designed for certain types of content and guidelines should apply to all web content 20:42:51 q+ 20:43:33 WC: similar to other guidelines where we refer to other parts of the guidelines 20:43:44 ack John 20:44:15 zakim, mute me 20:44:15 Michael_Cooper should now be muted 20:44:26 JS: I have a graduate student who just submitted public comments, has done a lot of work on accessibility and application development - he might be able to help. 20:44:33 + +1.973.944.aaaa - is perhaps Roberto_Castaldo? 20:45:07 -Roberto_Castaldo? 20:45:18 I'm always on line 20:45:21 bengt has joined #wai-wcag 20:46:38 +??P12 20:46:51 JS: seems that one of the problems we're running into with 1.1, 1.2 and maybe the 4.x guidelines is that 1.1 is about non-text content and 1.2 is about a specific type of non-text content and we're trying to get interactive out -- wonder if we can handle by having nontext that is (interactive, multimedia, audio, etc.) 20:46:52 zakim, ??P12 is Bengt_Farre 20:46:52 +Bengt_Farre; got it 20:47:05 zakim, I am Bengt_Farre 20:47:05 ok, bengt, I now associate you with Bengt_Farre 20:47:06 zakim, mute me 20:47:06 Yvette_Hoitink should now be muted 20:47:46 WC: wrestled with this too - started rewriting 1.1 to incorporate multimedia, but felt that was too much 20:47:53 action: john, ben and wendy to discuss 20:48:00 which holiday? 20:48:22 zakim, mute me 20:48:22 Yvette_Hoitink was already muted, Yvette_Hoitink 20:48:27 zakim, unmute me 20:48:27 Yvette_Hoitink should no longer be muted 20:48:34 Topic: Issue Summary on 2.4 20:48:51 ~52 issues summarized - a lot of work 20:49:34 summary: http://lists.w3.org/Archives/Public/w3c-wai-gl/2004JulSep/0512.html 20:50:09 3 underlying issues to discuss 20:51:12 1.) "large documents" - ex. 50,000 is a big number - ex. WCAG guidelines themselves is only 14,000 and needs some additional navigation 20:51:24 ack andi 20:51:32 ack jason 20:52:45 JW: one option would be to place an upper limit on what is considered "large" -- so we can say anything above X is too much, but it's open to tools or implementers to take documents that are less than this and provide a warning rather than an error. 20:53:35 ack john 20:53:51 JS: I'm wondering if this is actually an accessibility or a usability issue 20:54:43 YH: I think this does effect pwds disproportionately 20:55:15 .. much easier to navigate content and move within it when navigation aids are present 20:55:53 WC: there have been usability studies about how people deal with text on the web - skimming and scanning are primary modes of operation -- if that is not available, then this is an accessibility issue 20:56:22 JS: a 4 page print document isn't very long, but a 4 screen electronic document feels longer. that's nowhere near 50,000 words 20:56:41 YH: not sure how many screens are in WCAG and we can multiply by 3 and still not hit the 50,000 limit 20:57:14 -Kerstin_Goldsmith 20:57:15 JS: "long" is relative from one medium to another 20:57:50 q+ 20:58:05 q+ to say "screen is resolution depended" 20:58:33 WC: the term "screen" might be a better measure than the number of words, but screen size will depend on resoution and font size 20:58:40 q- 20:59:34 need to define a rule of thumb or best practice 21:00:14 +??P6 21:01:29 Have to leave the call for two minutes 21:01:56 -Katie_Haritos-Shea 21:02:16 action: Yvette and Kerstin to do some research about alternative ways to represent what constitues a large document 21:02:52 ack jason 21:02:53 JW: sentences rather than word could be a better measure - more language independent and representative of complexity 21:04:10 YH: underlying issue 2: make structure perceivable (was guideline 1.5) - wanted to verify that we did intent to remove these criterion - if this is what we intended, then we can close the issues 21:04:13 q+ 21:04:31 -??P6 21:04:47 I'm back in the call 21:05:06 -Bengt_Farre 21:05:11 bc doing work w/css techs, there are some associated with this criterion that no longer have a home. 21:05:21 bc e.g., border properties - highlighting that chunks go together. 21:05:26 js can go under 1.3 21:06:25 + +1.973.944.aabb - is perhaps Roberto_Castaldo? 21:06:44 no, it's not me 21:07:04 back but no message from zakim ? 21:07:39 zakim, +1.973.944.aabb is Bengt_Farre 21:07:39 sorry, bengt, I do not recognize a party named '+1.973.944.aabb' 21:07:49 wc: could be covered under 1.3, but doesn't seem to fit 21:08:12 zakim, 1.973.944.aabb is Bengt_Farre 21:08:12 sorry, bengt, I do not recognize a party named '1.973.944.aabb' 21:08:30 zakim, ?1.973.944.aabb is Bengt_Farre 21:08:30 sorry, bengt, I do not recognize a party named '?1.973.944.aabb' 21:09:05 q? 21:09:11 q- 21:09:51 JW: wider issue is that we don't include the counterpart to 1.3, which is to provide style for the structure that is there 21:12:18 action: wendy and jason to work on a proposal to look at how to deal with techniques that were associated with removed criterion (ex CSS 4.1 and 11.1) and consider whether these ideas need to be reintroduced in the guidelines 21:13:00 YH: 3) confusion about why we need 2.4 because they believe it is a usability, rather than an accessibility issue 21:14:01 YH: guideline 1.3, level1, sc1 overlaps with several of the items in 2.4 21:14:40 ack john 21:14:52 YH: 2.4 and 1.3 are closely linked - need to figure out how to decide which criterion belong in each. 21:15:08 -Roberto_Castaldo? 21:15:32 ex. you need table headers to mark structure, but also to navigate 21:15:37 I'm always here :-) 21:16:01 my line is dropping all the time and it is weird 21:16:27 js: are there structural things that are necessary to support navigation and orientation that would not fit under 1.3? 21:16:53 yh: there are some things (like a site map) that are not part of structure 21:16:57 + +1.973.944.aacc - is perhaps Roberto_Castaldo? 21:17:14 Zakim, I am Roberto_Castaldo? 21:17:14 sorry, rcastaldo, I do not see a party named 'Roberto_Castaldo?' 21:17:15 zakim, ?+1.973.944.aacc is Bengt_Farre 21:17:15 sorry, bengt, I do not recognize a party named '?+1.973.944.aacc' 21:17:44 zakim, ?+1.973.944.aacc is Roberto_Ellero 21:17:44 sorry, rellero, I do not recognize a party named '?+1.973.944.aacc' 21:17:55 zakim, ?+1.973.944.aacc is rellero 21:17:55 sorry, rellero, I do not recognize a party named '?+1.973.944.aacc' 21:18:11 rellero thats my line 21:18:16 additional navigation that is added becomes part of structure after it is added 21:18:21 ok 21:18:28 zakim, ??1.973.944.aacc is Bengt_Farre 21:18:28 sorry, bengt, I do not recognize a party named '??1.973.944.aacc' 21:18:35 01Zakim, I am Roberto_Castaldo 21:18:55 q_ 21:18:57 q+ 21:18:58 +Katie_Haritos-Shea 21:19:00 ack jason 21:20:00 zakim, 1.973.944.aacc is Bengt 21:20:00 sorry, wendy, I do not recognize a party named '1.973.944.aacc' 21:20:02 JW: in confomance,a delivery unit is something that has a URI - consequence of that is that a navigation mechanism is considered separately for each page. if you've evaluating conformance of each one, then the navigation isn't looked at as a whole 21:20:13 zakim, who's on the phone? 21:20:13 On the phone I see Mike_Barta, Michael_Cooper (muted), Yvette_Hoitink, Roberto_Ellero? (muted), Ben, Wendy, Roberto_Castaldo?, JasonWhite, John_Slatin, [IBM], Roberto_Castaldo?, 21:20:16 ... Katie_Haritos-Shea 21:21:27 ack yvette 21:21:28 yh: 1.3 and 2.4 overlap - sounds like 1.3 is about marking structure and 2.4 tells authors to supply additional structure, where 1.3 makes sure that existing structure is available to user agent 21:21:30 ack john 21:22:15 js: interesting approach, but gets weird because 2.4 comes after 1.3 - logically, you want to say, provide structure and then make it perceivable 21:22:16 zakim, Roberto_Castaldo? is roberto2 21:22:16 sorry, bengt, I do not recognize a party named 'Roberto_Castaldo?' 21:22:31 zakim, Roberto_Castaldo is roberto2 21:22:31 sorry, bengt, I do not recognize a party named 'Roberto_Castaldo' 21:22:32 -Roberto_Castaldo? 21:22:44 js: linearity of the guidelines is somewhat misleading here because they interact with one another 21:22:48 zakim, who is on the phone ? 21:22:48 On the phone I see Mike_Barta, Michael_Cooper (muted), Yvette_Hoitink, Roberto_Ellero? (muted), Ben, Wendy, JasonWhite, John_Slatin, [IBM], Roberto_Castaldo?, Katie_Haritos-Shea 21:23:21 zakim, Roberto_Castaldo? is beng 21:23:21 +beng; got it 21:23:22 + +1.973.944.aadd - is perhaps beng 21:23:26 q? 21:23:35 zakim, beng is Bengt_Farre 21:23:35 sorry, bengt, I do not recognize a party named 'beng' 21:23:41 issue: make it clear that numbered sequence of guidelines isn't meaningful 21:23:49 zakim, who is on the phone ? 21:23:49 On the phone I see Mike_Barta, Michael_Cooper (muted), Yvette_Hoitink, Roberto_Ellero? (muted), Ben, Wendy, JasonWhite, John_Slatin, [IBM], beng, Katie_Haritos-Shea, beng 21:24:11 I'm on the phone too :-) 21:24:56 wc: publishing a suite of internal drafts tomorrow - have a series of milestones to hit for another internal draft on the 8th of october 21:25:08 next public WD on 3rd of november 21:25:20 planning page includes milestones and agenda items 21:25:44 planning page: http://www.w3.org/WAI/GL/2004/07/WD-plan.html 21:25:46 ack john 21:25:52 Topic: 1.3 Feedback for gateway 21:26:03 -beng 21:26:07 js: not much feedback 21:26:22 so I am Beng :-/ 21:26:45 :-) 21:27:38 + +1.973.944.aaee - is perhaps beng 21:27:41 I am on the phone again now 21:27:59 q+ to say "doc is called Gateway Techniques, not Gateway TO techniques" 21:28:32 js: gateway to techniques or gateway techniques? 21:29:08 q- 21:29:17 wc: plan is to incorporate John's proposed text into internal WD tomorrow - any objections? 21:29:32 -- no objections raised -- 21:30:36 -Katie_Haritos-Shea 21:30:37 bye all 21:30:45 Bye! 21:30:49 -Michael_Cooper 21:31:29 next week: discussion on conformance profiles 21:31:53 -Roberto_Ellero? 21:31:54 -Mike_Barta 21:31:55 -John_Slatin 21:31:57 -Wendy 21:31:57 rcastaldo has left #wai-wcag 21:31:58 -Yvette_Hoitink 21:31:59 -beng 21:31:59 -beng 21:32:00 -Ben 21:32:02 ben - thank you for minuting 21:32:02 -[IBM] 21:32:07 sure thing 21:32:20 bye 21:32:24 -JasonWhite 21:32:25 WAI_WCAG()4:00PM has ended 21:32:25 bengt has left #wai-wcag 21:32:26 Attendees were Katie_Haritos-Shea, Michael_Cooper, Yvette_Hoitink, Wendy, Ben, Kerstin_Goldsmith, Roberto_Ellero?, Mike_Barta, JasonWhite, John_Slatin, [IBM], +1.973.944.aaaa, 21:32:28 ... Bengt_Farre, +1.973.944.aabb, +1.973.944.aacc, beng, +1.973.944.aadd, +1.973.944.aaee 21:33:16 agenda? 21:33:22 action items? 21:34:19 RRSAgent, bye 21:34:19 I see 4 open action items: 21:34:19 ACTION: Katie and Wendy to do some research related to policy for the multimedia guideline [1] 21:34:19 recorded in http://www.w3.org/2004/09/02-wai-wcag-irc#T20-34-26 21:34:19 ACTION: john, ben and wendy to discuss [2] 21:34:19 recorded in http://www.w3.org/2004/09/02-wai-wcag-irc#T20-47-53 21:34:19 ACTION: Yvette and Kerstin to do some research about alternative ways to represent what constitues a large document [3] 21:34:19 recorded in http://www.w3.org/2004/09/02-wai-wcag-irc#T21-02-16 21:34:19 ACTION: wendy and jason to work on a proposal to look at how to deal with techniques that were associated with removed criterion (ex CSS 4.1 and 11.1) and consider whether these ideas need to be reintroduced in the guidelines [4] 21:34:19 recorded in http://www.w3.org/2004/09/02-wai-wcag-irc#T21-12-18