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

Notes from ATAG Meeting 04/03/2006

From: Jan Richards <jan.richards@utoronto.ca>
Date: Mon, 3 Apr 2006 17:37:54 -0400
Message-ID: <1144100274.443195b21d5ce@webmail.utoronto.ca>
To: w3c-wai-au@w3.org
ATAG Notes, April 3, 2006

4:00 EST

Attendees:

Tim Boland
Greg Pisocky
Jan Richards
Jutta Treviranus

Action Items indicated with an AI:

Face to Face:

No dates in May that are possible at NIST.
Looking at Toronto, tentatively week of June 12, 2006. Possibly 12 - 14. OK for
JT, JR, GP and TB.

------

A.1.4 Ensure changes to the display settings of editing views do not
affect the content being edited.

All: APPROVED

Rationale: Authors may require settings to render and control the content during
editing that differ from the presentation defined for the published
content (e.g. providing a high contrast setting to edit content that is
not intended to be high contrast)

All: APPROVED

SC1: The author must be able to configure the display settings of editing
views without affecting the Web content being edited. 

All: APPROVED

Technique A.1.4-1.3 [Advisory]:
Allowing the author to specify a preferred style sheet that will override the
"published" style of the document in the editing view.

All: APPROVED

---------------

JR's B.2.7 proposals:

[action 1] Moving checkpoint B.2.7 to Section B.3 (I think it fits under
"integration") and rewording it as: "Document features of the tool that
support the production of accessible content." 

[action 2] Changing the success criterion to specifically reference the
features related to section B.2, for example: SC 1. All features of the
tool that play a role in satisfying the success criteria for checkpoints
B.2.1, B.2.2, B.2.3, B.2.5, B.2.6 and B.2.9 must be documented in the
help system. (note the wording parallels A.3.3) 

[action 3] Moving B.2.8 to Section B.3 (I think it fits under
"promoting") and rewording it as: "Ensure that any authoring practices
demonstrated in *repair instructions* or documentation are accessible"
(note that repair instructions, a term used in B.2.3, is separated from
help system-type documentation. 

[action 4] Reword B.3.2 and its success criteria to follow the new
pattern in [actions 1 and 2]: "Ensure that features of the tool that
support the production of accessible content are always clearly
available to the author." 

[action 5] Reword B.3.4 and it's success criteria to follow the new
pattern in [actions 1 and 2]: "Ensure that features of the tool that
support the production of accessible content are configurable." 

Action JR: Rework B.3.4: Accessibility options must be turned on by default, but
you may opt out. If you do opt out, you are warned of the consequences, and you
are always allowed to opt-in. Opt-in is always available. (Rough sentence)

All: All, revisit all of this and determine if the proposal is a good one.

-------------------------

Wrap Up:

Agreed to go in a random order, to ensure equal attention and quality of
replies. A.4.1. for BF. B.2.6. and B.2.7 

AI: GP B.1.3

AI: JR TBA...

Next meeting to begin at 3 pm ( 2 hour duration). 

TB: WCAG has been approved for last call working draft, though it has
not yet been published. 

Meeting adjourned:

5:00 pm EST

 

 

 

 

 

 

 

 

 
Greg Pisocky
Business Development Manager
Accessibility Specialist
Adobe Systems Incorporated
8201 Greensboro Dr., Suite 1000
McLean, VA 22102 USA
703.883.2810 phone 703-883-2850 fax
 
 

----- End forwarded message -----


Received on Monday, 3 April 2006 21:38:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 22 September 2008 15:53:06 GMT