12 Dec 2002 - WCAG WG Teleconference Minutes
Present
Phone: Lee Roberts, Wendy Chisholm, Michael Cooper, Doyle Burnett, Eugenia
Slaydon, Avi Arditti, Jason White, Roberto Scano, Judy Brewer (1st 30 mins),
Ken Kipnes, Gregg Vanderheiden, Ben Caldwell, John Slatin, Cynthia Shelly,
Paul Bohman, Loretta Guarino Reid, Bengt Farre
IRC: Judy, Zakim, bengt, PatBertin, rscano, wendy
Regrets
Matt May, Andi Snow-Weaver, Katie Haritos-Shea
Action Items and Resolutions
- action WAC:finish converting dtd to XMLSchema, send to
list for discussion.
- actionWAC:schedule
first techniques-specific telecon for 2nd week of January, 10-11:30 a.m.
eastern U.S.
- action MC and WACincorporate comments on Requirements
for Techniques, publish on w3c site, clarify .
- resolved:(proposed) plan to publish
Requirements for Techniques for WCAG 2.0 on TR the 2nd week of
January.
Housekeeping
Discussion about use of the mailing list and possible changes to make it
feel more welcoming of external comments.
JW, GV, JB, and WAC invite people to comment privately to the chairs/staff
contact about concerns related to the group's progress and process.
Requirements for Techniques
Draft: Requirements
for Techniques documents
desired outputs from xml source:
- checklists,
- test files,
- techniques by conformance level,
- all encompassing human-readable printable document,
- by technology,
- technology of choice+core techniques,
- grouped by conformance level.
In discussing the requirements document, these two additional audiences
were raised:
- documentation writers needs are different than content developers
(images are used differently for documentation)
- trainers
There was concern that addressing these audiences might decrease the
technical nature of the techniques documents. Isn't that what the
guidelines/checkpoints are for?
There were several responses to this concern:
- we need to coord w/EO so that they may continue to produce
less-technical documentation of WCAG 2.0.
- trainers and doc writers need to understand the technical aspects as
well.
- the various techniques documents will be technical.
- we will link to other educational materials (as well as EO), i.e.,
there are quite a few people producing web accessibility tutorials.
- the techniques are at the level that will be implemented by tools so it
has to be precise and accurate.
- the core techniques are likely to be more comprehensive and not rely on
any one technology.
Editing issues (techniques)
complimentary xmlspy licence for editors or use tool of choice (that
validates XML)
expectation that our schema will be reused by other groups developing
guidelines and techniques i.e., I18N, DIWG, QA, etc.
housekeeping
- propose techniques-specific telecon: 10-11:30 a.m. Wednesdays.
- keep discussion on the primary WCAG WG list
- not splitting the group, creating a task force focused on
techniques
action WAC: finish converting dtd to XMLSchema, send to
list for discussion.
action WAC: schedule first techniques-specific telecon
for 2nd week of January, 10-11:30 a.m. eastern U.S.
- update schema
- bring current xml up-to-date with schema
- then begin making changes
roles of the editor:
- incorporate the changes
- help push the process along
document the editing process: the schema, the process, the tools
Timeline (techniques)
proposed timeline:
- december: finalize requirements, create the schema (absorbing the
existing dtd, convert to dtd, build to meet requirements)
- january: work on one (or several) documents, publish requirements to
TR
- february by tech plenary: a draft for review, review requirements to
see if we're meeting and if they need to change
- march: discuss draft and schema with other groups
action MC and WAC incorporate comments on Requirements
for Techniques, publish on w3c site, clarify .
resolved: (proposed) plan to publish Requirements for
Techniques for WCAG 2.0 on TR the 2nd week of January.
Misc
Roberto Scano and Bengt Farre participated in the meeting using net2phone.
It cost USD.05/minute.
$Date: 2002/12/14 01:15:06 $ Wendy
Chisholm