W3C home > Mailing lists > Public > w3c-wai-au@w3.org > April to June 2006

AUWG Teleconference Minutes May 1, 2006

From: Jan Richards <jan.richards@utoronto.ca>
Date: Mon, 01 May 2006 17:15:18 -0400
Message-ID: <44567A66.40706@utoronto.ca>
To: "List (WAI-AUWG)" <w3c-wai-au@w3.org>

Minutes: AUWG Teleconference, May 1, 2006


Jan Richards - JR - Interim Staff Contact - Acting Chair
Tim Boland - TB
Greg Pisocky - GP
Roberto Scano - RS

Action Items indicated with an AI:


1. Comments on Guidelines draft in-group checkpoint review:


(a) JR/TB's submission B.2.4:


- Recent rewording of SC1 in response to RS's comments:


Approved as modified.

(b) batch from BAF:


- A start on proposed responses by JR:


- Updated by JR:


(c) JR's submission on B.2.7 (plus B.2.8, B.3.2, B.3.4):

- Most recent:


- Checkpoints will now read as follows:


Approved as rewritten

(d) BAF's submission on A.4.1 (not completely agreed upon in the last call):


-"must"s will change to "should"s

Deferred, BAF has agreed to make the proposed changes.

(e) GP's submission on B.1.4

B.1.4 can stand as written.

(f) JR's submission on A.1.1


-response to RS's comments:


AI: JR to change references User Interface to Authoring Tool User
Interface. Recommendation made by TB to document why language is
deviating from WCAG.

AI: JR Non text objects to be changed to authoring tool interface in
order to make language consistent with WCAG.

AI: JR to write language concerning Part A.

True of success criteria 1 but not of success criteria 2.

AI: JR: Typo for non text objects....

TB: Pointed out we do not have a definition for web based interface

AI: JR: develop definition for web based interface components.

(g) BAF's submission on A.3.1

(h) JR's submission on B.1.2


AI: TB to ensure that external entities are covered as well.

Proposal is to break into 2 checkpoints. A Priority 1. And then
checkpoint B.1.3

AI: GP to work on B.1.3 to encompass full set of use cases (both
recognized and unrecognized content and markup)

B.1.3 Ensure that the tool preserves unrecognized markup. [Priority 2]
Rationale: Unrecognized markup may include recent technologies that have
been added to enhance accessibility and should be preserved during
transformations and conversions. Success Criteria: no change required
SC1: During all transformations and conversions supported by the
authoring tool, the author must be notified before any unrecognized
markup is permanently removed.

(i) JR's submission on A.0.1


AI: TB to find situation where browser accessed functionality may not be
web content (if possible).

AI: JR to harmonize Browser Interface, UI references, web based with one
all encompassing term.

There should only be one success criteria for this checkpoint. This is
meant to apply to the user interface.

2. Technique development

- JR and TB have put up an internal draft of the Techniques:


Slight changes to accomodate new wording of success criteria.

3. Publishing plans - heartbeat requirement means another publication is
probably needed soon - most likely the Techniques.

4. F2F - 12-14 June 2006, Toronto, Canada

AI: JR: Hotel page coming.

AI: New Assignments for next call:

TB: A.2.8,
GP: to contribute to B.2.2 and full review of A.1.2
JR: B.2.1,
RS: A.3.3,

Next meeting in two weeks Monday, May 15, 2006 at 3:00 pm EST
Received on Monday, 1 May 2006 21:16:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:39:53 UTC