21:03:03 RRSAgent has joined #au 21:03:10 Zakim has joined #au 21:03:15 zakim, this WAI_AUWG 21:03:15 I don't understand 'this WAI_AUWG', MattSEA 21:03:21 zakim, this is WAI_AUWG 21:03:21 ok, MattSEA 21:03:32 zakim, who's here? 21:03:32 On the phone I see Jan_Richards, Matt, [IBM], Greg_Pisocky 21:03:33 On IRC I see Zakim, RRSAgent, MattSEA 21:03:43 zakim, [IBM] is Kip_Harris 21:03:43 +Kip_Harris; got it 21:04:24 RRSAgent, pointer? 21:04:24 See http://www.w3.org/2004/01/12-au-irc#T21-04-24 21:05:27 +??P12 21:05:45 zakim, ??P12 is Karen_Mardahl 21:05:45 +Karen_Mardahl; got it 21:07:21 agenda+ f2f 21:07:26 zakim, take up agendum 1 21:07:26 agendum 1. "f2f" taken up [from MattSEA] 21:07:44 jr Plan is for Austin in February. 21:07:51 +Tim_Boland 21:08:13 kh Got the room and catering. What time do we start, and when should we bring in the lunch? 21:08:29 jr We start at 9, so 8:30 is when we start filtering in. 21:08:54 jr Lunch at 12, then wrap up 5-5:30 21:09:20 jr A range of hotels would be good. 2 or 3. 21:10:18 kh Internet connectivity? 21:10:34 jr We'd prefer high-speed, but if all else fails, dialup is passable. 21:11:05 jr Anybody who is in the center who would like to present is welcome. 21:11:52 agenda+ Plan for publishing new ATAG WD 21:11:57 zakim, take up agendum 2 21:11:57 agendum 2. "Plan for publishing new ATAG WD" taken up [from MattSEA] 21:12:12 jr Need to plan a draft for late January or early February. 21:13:36 mm Need to sync up latest version, and catch everyone on action items. 21:13:42 km Would like to help coordinate that. 21:13:57 jr May want to schedule an extra meeting next week at this time. Availability? 21:14:20 kh Do we have a list of action items? 21:14:46 tb Next Monday is Martin Luther King Day in the US. I can attend. 21:15:04 ACTION: mm and jr Work on a list of action items 21:15:40 jr Once we identify actions we can divide it up by participant expertise. 21:16:18 kh We think ATAG is ready for a technical review? 21:16:26 jr Yes, some work to do, but should get outside review. 21:16:49 jr Some items from Geoff Deering, who has a CMS background to offer, has thoughts to offer on the guidelines. We're still open to that input. 21:17:24 tb Plan for going to last call? 21:17:32 jr We'd like to be a Rec by end of year. 21:17:52 jr Judy has been pushing for an end of January date. 21:19:11 kh If we're going to get a draft out by end of month, we would need the techniques in by this time next week. 21:19:24 kh Is that what we're proposing? 21:20:13 jr Guideline 2 is back in, from Liddy. My piece is close. Tim had two reports on his action. 21:20:30 tb Still questions about ISO 16071 and its terms for release. 21:20:51 kh We need to know what needs to happen by when to get things out by the end of the month. 21:21:19 jr If it slips by a week or so, it's not a big deal. But we need an issues list, assembling the techniques, etc. quickly. 21:22:43 jr If Matt and I can have an issues list out by the 14th, and we can put techniques together by the 19th, I can do that. 21:23:13 kh We had an open question about whether the fee required for an ISO spec was an inhibitor to us referencing the ISO document. 21:23:20 mm I'll get an answer to that by the 14th. 21:23:50 ACTION: mm Find out about referencing fee-based documents (ISO 16071) 21:24:05 ACTION: mm and jr Issues list for ATAG by 14th 21:25:18 gp I need a little help with my piece. 21:25:24 jr Matt and I can coordinate with you. 21:25:57 km I have references to this info 21:26:07 jr Glossary issue. Karen? 21:26:34 km I matched up the glossary with ATAG and the techniques. They're identical. I think we should pull it out of ATAG 2.0 and leave it in the techniques. 21:26:56 jr How does that square with the guidelines as a normative document? 21:27:48 mm Would prefer to leave it in ATAG Rec and take out of techniques. 21:28:04 jr Agreed to remove glossary from techniques and leave it in the guidelines? 21:28:11 (agreed.) 21:28:57 km Question about the glossary. There's been a lot of changes from earlier versions. Can I assume that what is in the current draft is approved? 21:29:19 jr What's in there now is what we're suggesting. If we've lost something and you'd like to bring it back, we can take a look. 21:29:38 tb I was asked to develop a list of terms that needed definition. Have those been defined? I could resurrect that list. 21:29:53 jr Maybe we can add that in to the glossary. We'd need to do that before it goes out. 21:31:06 agenda+ proposed changes to ATAG references doc 21:31:11 zakim, take up agendum 3 21:31:11 agendum 3. "proposed changes to ATAG references doc" taken up [from MattSEA] 21:31:28 jr This addresses references to versions of WCAG. Does this work? 21:33:11 jr The doc introduces that there are 5 relative priority checkpoints, and conformance to ATAG will be with respect to a specific version of WCAG. 21:34:27 km I like it. 21:34:52 tb Question about priority 3. Some items currently don't need to be satisfied. 21:34:56 jr We're remapping them. 21:35:10 tb So all P3 items in WCAG must be satisfied, not just the ones that are in there now? 21:35:17 jr Yes. If you want to suggest new wording, ok. 21:36:54 jr In our document, we're not going to refer to any level. We're just going to look at this document. 21:37:00 tb Has the WCAG WG looked at this? 21:37:07 jr We've told them about it in a joint call. 21:37:22 jr It'll be a Note. 21:38:38 jr Tim's draft to test for ATAG conformance. It looks like a lot, I haven't had much chance to look at it. 21:39:45 tb I was just thinking about what tool vendors would have to do. Out of that came this document. Intended to stimulate discussion on how to build the testing plan for CR. 21:42:09 tb This was designed to determine what A-AA-AAA looked like, and determine an approach to a low-cost test suite for authoring tools. 21:43:43 jr Everything to do with relative priority checkpoints are necessarily a matrix. That means following WCAG as it moves along. 21:43:57 tb I intend to keep the document updated. 21:44:31 kh I thought it was a mind-expanding thing to think about. Whether there is any context for testing success criteria in other WAI documents. Are we breaking new ground? 21:44:41 tb There's a WCAG techniques TF. 21:46:41 mm UAAG test suite has several hundred tests. 21:47:24 kh So, about Tim's role-based tests, is there anything like that? Where the vendor comes up with a use-case scenario, and an author certifies that claim? 21:48:25 tb I had assumed that there was a user that knew enough about the tools, and then a tester or testers who could take that knowledge and try to verify the state of conformance. 21:48:48 jr And these could be different authors? 21:48:58 tb Yes, but they wouldn't have any a priori knowledge of the tool. 21:49:14 kh That sounds innovative to me, and interesting. 21:54:27 kh How did this work in UAAG? 21:54:47 mm UAAG was more technical. ATAG has a human element that would be worth exploring. 21:54:55 kh Would this be a TR document? 21:55:17 mm No, shouldn't be. The test suite is a support document, and shouldn't need to be released as a Note. 21:55:30 tb In CSS, errata are still being issued for CSS1 suite. 21:57:33 jr Next meeting 19 January, regular time. 21:58:01 -Tim_Boland 21:58:04 -Kip_Harris 21:58:05 -Greg_Pisocky 21:58:05 -Karen_Mardahl 21:58:14 zakim, who's here? 21:58:14 On the phone I see Jan_Richards, Matt 21:58:15 On IRC I see Zakim, RRSAgent, MattSEA 21:59:29 rrsagent, bye 21:59:29 I see 3 open action items: 21:59:29 ACTION: mm and jr Work on a list of action items [1] 21:59:29 recorded in http://www.w3.org/2004/01/12-au-irc#T21-15-04 21:59:29 ACTION: mm Find out about referencing fee-based documents (ISO 16071) [2] 21:59:29 recorded in http://www.w3.org/2004/01/12-au-irc#T21-23-50 21:59:29 ACTION: mm and jr Issues list for ATAG by 14th [3] 21:59:29 recorded in http://www.w3.org/2004/01/12-au-irc#T21-24-05