JT: Jutta Treviranus
JR: Jan Richards
MM: Matt May
KM: Karen Mardahl
KH: Kip Harris
GP: Greg Pisocky
TB: Tim Boland
LN: Liddy Nevile
TC: Tom Croucher
PJ: Phill Jenkins
ACTION: MM or JR: Add TB's item to agenda.
ACTION: JR to ping wendy to remind WCAG of the upcoming call
ACTION: TB: Write paragraph proposing discussion of structure on joint call.
ACTION: JT: Will send out checkpoint wording and rationale so that the rest
of the group can help with the success criteria.
ACTION: MM: Guaranteed to be out this week. Perhaps by tomorrow.
ACTION: JR and MM: Will make a correctly numbered version of the techniques.
ACTION: JT - start discussion on list.
KM: Is a technical writer and technology watcher for ???.
TC: Is a researcher with ??? university. Has a research interest in accessibility. Working on techniques gateway for WCAG.
KH: Works with Phill at IBM Accessibility Centre. Developer on Homepage Reader. Will be coming in to replace Phill.
JT: Who can make it? Jan, Jutta, Phill and Kip, Tim, Liddy, Karen, Greg, Tom.
JT:
1. WCAG needs to push the use of accessible tools (meeting ATAG)
2. How ATAG will reference WCAG. (message sent Sept. 26 from Wendy C.)
3. Scope of the two documents (how the two might overlap - content that authors)
4. How do both groups handle non-W3C technologies.
JT: What else?
TB: What about synchronizing document structure and organization?
ACTION: MM or JR: Add TB's item to agenda.
PJ: How tightly bound are we to WCAG requirements for testing etc.? Relates back to "which one should tool do vs. which one should the tool prompt the user to"
TC: Makes point about using list of test cases being prepared by WCAG.
JR: Clarifies that the AUWG test suite is to check tools not documents.
TB: We need better coordination with WCAG.
TC: WCAG is going to produce techniques for several formats, including HTML and XHTML
ACTION: JR to ping wendy to remind WCAG of the upcoming call
jr Should get some AU positions down before call on Friday. Tim, could you write a short paragraph about synchronizing structure of documents?
tb Yes.
ACTION: TB: Write paragraph proposing discussion of structure on joint call.
jr How closely should we collaborate? Task force of members of each WG?
pj I propose that. Primarily a WCAG effort, we just want to make sure it will work with tools.
jr Different user interface metaphors, and integration with look and feel. WCAG wouldn't have any interest in that.
pj How you evaluate a tool would involve not just the content, but how it notifies the user of errors.
jr Also going to need to trigger on that properly.
pj We should have a test suite of what should trigger a message.
jr We need a checklist to go into the ATAG suite: does it look weird, etc.
jr Should we have a group to grab items from the WCAG group and bring it into ATAG?
tb Would be good to use what resources are out there.mm I've been tracking UAAG test suite work and WCAG techniques task force. We should be working with WCAG to see that as much of their suite is reusable.
jr Send comments to list?
jr People who can meet on Friday: Jan, Jutta, Phill, Kip, Tim, Greg, Liddy, Matt.
jr UAWG is proposing a workshop. Looking at a new direction. Some talk of inviting AU along.
mm UA proposed the workshop, lots of other groups are interested in discussing future direction, whether there is a better design for the documents, etc.
pj Whether AT vendors should be participating?
mm Yes, that's another question. Should have a proposal floated soon.
WC and JT: Have an action to look at 4.2, a new checkpoint added during F2F in Seattle. There was discussion on last conf. call. Kynn, Wendy and Jutta working on it privately. Please send any suggestions. "Success Criteria" are the problem.
ACTION: JT: Will send out checkpoint wording and rationale so that the rest of the group can help with the success criteria.
JT: When will the new internal draft be out.
ACTION: MM: Guaranteed to be out this week. Perhaps by tomorrow.
JR: Thinks we should lose the "evaluation techniques"
JT: But we need an evaluation policy.
JR: Agreed.
LN: OK.
TB: Reserves judgement.
JR: We also need to update numbering etc.+ making it less ATAG specific
JT: Techniques more dependent on WCAG.
JT: This the major work-item for the next while.
JT: Next call, we will make a work plan.
ACTION: JR and MM: Will make a correctly numbered version of the techniques.
PJ: Actually there is an ISO standard underway for software accessibility - ISO16071 - on ISO.org there is a purchasable paper
PJ: Wants to look into this. Older version may have been very weak.
JT: If it is adequate we would point to that?
PJ: Yes if it's ok. - Phill can get us access to that.
JT: Gives background to why we need this.
TB: Where? When?
JT: January, Orlando in conjunction with ATIA.
TC, TB: Cannes Tech Pleanary - Already in PF, wants to join WCAG - Tech pleanry week 1st - 5th of March - WG meetings M,T and R,F
Would suit LN, JR,
MM: We are too late - it closed on Oct. 10.
ACTION: JT - start discussion on list.