AU Teleconference (Monday, February 18, 2002)

Telephone: +1.617.761.6200
Conference number: 2894

Agenda:

Setting the Feb. 25, 26 Face to Face Meeting Agenda (with the IMS accessibility working group-AWG). We are hoping to have joint discussions interspersed with break out to work on drafting techniques. Information about the IMS initiative can be found at http://www.imsproject.org/. Proposed agenda items for the joint section include:

Attendees:

JR: Jan Richards
JT: Jutta Treviranus
JB: Judy Brewer
PJ: Phill Jenkins
HS: Heather Swayne
CMN: Charles

Regrets:

None

Action Items:

Minutes:

JT: Reports 12 hour difference between send and receive to the list

PJ: 45mins for him

JT: Background on IMS-AWG - see URL in agenda. They are working on E-Learning Guidelines and Harmonization of Accessibility with Metadata, LIP, Learning Objects, etc.

JT: Due to shared membership, we decided to meet together in Nice.

JB: How many IMS people.

JT: Andy Heath, Cathleen or Madelaine, Martin Cooper, Chetz Colwell, Liddy, Reidy, WebCT person

JB: We should have a meeting doc.

CMN: Look in Meetings/

JB: Will create meeting doc during this call.

JT: Has sent to the list some proposed agenda items.

JT: Might be a good time to look at Content Management techniques (with respect to Courseware).

JT: Transformable content becoming a big topic in e-learning. This requires user prefs - that can have acceesibility rolled in (LIP-learner information package). How does it relate to W3C.

PJ: Seems to be done at delivery time, not authoring time. At server end, not client end.

JT: But at the authoring end, the content needs to be authored so that transformability is possible.

PJ: How will this work? Will the developers report?

JT: XML support: entire chapter devoted to XML, but the AU document doesn't talk much about XML support. IMS request more strongly worded XML recommendations in AU.

JT: EO advocating conformance to ATAG: IMS has all the courseware tools as mewmbers. This could be an advocacy vehicle.

PJ: He will be making his action report as well.

JB: Has come up with the meeting page template.

PJ: Likes the EO related item. Perhaps Tuesday.

JB: Last thing on Tuesday.

JT: We can also get some best practice reports from

PJ: What about smartforce (large content group)?

JT: They are in IMS, but not the AWG. They are in the Harmonization.

JT: So start with presentation by courseware.

PJ: Let's do a walkthrough of ATAG with respect to Courseware.

JT: We also need to look at interactive pieces.

JR: It would be helpful to do the ATAG walkthrough

JB: How long to present? An hour?

JT: It might be brief to avoid proprietary.

PJ: Can share accessibility features for IBM learning tools

JB: Who will be there?

JT: Blackboard, WebCT, E-college, IBM WebConferences

JB: Then the walkthrough.

JT: A discussion of how ATAG will apply to IMS.

JB: What about MicroSoft products.

HS: We have and educational dept. - will investigate

JB: How long? Until break and then on to lunch?

JT: OK, now what about authoring transformable content, XML support

JT: Right after lunch - things that have came up in the morning.

JT/JB: Coordination on Tuesday afternoon

JT: Only other joint item is supporting transformable content

JB: Other goals?

PJ: ATAG-508 mapping?

JB: That might fall under EO stuff at the end of Tuesday?

HS: Joint marketting effort to developers would be important.

JB: Maybe we can add more effort to marketting to end user

JR/JT: Techniques

PJ: Eval/correction tools - some tools got it wrong.

JB: Working on proposal to move eval/corr forward.

PJ: PageScreener for ex. asks user to remove all colour

JB: Another work item will be to get better QA control over implementation.

PJ: Do we need to resurrcet AERT?

JB: WCAG 2.0 will have this built in.

JB: There is an existing tools for transformation, eval and repair doc. EO will be redoing this document. Scheduled for Q2 this year. This seems to span AU as well.

JB: So the agenda item would be potential updating pof AU parts of AERT document

JB/JT: [detailed scheduling discussion]

JR: I will update the meeting page