Hi everyone

Greg can scribe

<Jan> Scribe: Greg

Publication Update

Results delayed due to illness

<Jan> http://lists.w3.org/Archives/Public/w3c-wai-au/2008JulSep/att-0103/00-part

Action items from last call

<trackbot> Sorry, couldn't find user - items

<Jan> http://lists.w3.org/Archives/Public/w3c-wai-au/2008OctDec/0002.html

<scribe> New proposed wording for Relationship to the Web Content Accessibility Guidelines (WCAG)

<Jan> http://www.w3.org/WAI/AU/2008/WD-ATAG20-20080929/WD-ATAG20-20080929#def-Acc-Auth-Practice

<Jan> ATAG 2.0 points to the WCAG 2.0 success criteria in order to define the ATAG 2.0 concept of "accessible authoring practices", which authoring tools are required to support in various ways.

<Jan> ATAG 2.0 points to the WCAG 2.0 success criteria in order to define the ATAG 2.0 concept of "accessible authoring practices", which authoring tools are required to support in various ways.

<Jan> Web content accessibility problem: An aspect of Web content that violates a WCAG 2.0 success criteria. Each success criteria has an associated Level.

<Jan> Web content accessibility problem: An aspect of Web content that violates a WCAG 2.0 success criteria. Each WCAG 2.0 success criteria has an associated Level.

<Jan> ACTION: JR Use new text in relationship with WCAG section [recorded in http://www.w3.org/2008/10/06-au-minutes.html#action01]

<trackbot> Created ACTION-25 - Use new text in relationship with WCAG section [on Jan Richards - due 2008-10-13].

<Jan> ATAG 2.0 Conformance Claims are supported by WCAG conforming examples of Web content produced by the authoring tool (e.g., samples of automatically-generated content)

Jan and Jean to come up with rationale text for Part A

<Jan> This is a W3C Public Working Draft. This draft integrates changes made

<Jan> as a result of comments received on the 10 March 2008 Public Working

<Jan> Draft and also includes changes intended to keep the document harmonized

<Jan> with WCAG 2.0. Substantial changes include:

<Jan> (1) Refocusing Part A ("Make the authoring tool user interface

<Jan> accessible") on requirements that apply most specifically to Web content

<Jan> authoring tools and away from generic accessibility guidelines. Instead,

<Jan> ATAG 2.0 will continue to require WCAG conformance for Web-based

<Jan> authoring tools and will add a requirement to follow standards and/or

<Jan> platform conventions that benefit accessibility for non-Web-based tools.

<Jan> This change will let the Working Group keep a focus on authoring tools

<Jan> and avoid the need to repeat operating system specific information that

<Jan> is already available elsewhere.

<Jan> (2) Replacing the concept of "Web Content Accessibility Benchmark" with

<Jan> a more straightforward relationship with WCAG 2.0. This has been made

<Jan> possible by the progression of WCAG 2.0 to Candidate Recommendation

<Jan> status on 30 April 2008.

<Jan> The Working Group seeks feedback on the following points for this draft:

<Jan> - Does the refocused Part A provide developers with sufficient guidance

<Jan> on what must be done to ensure accessibility of authoring tools to

<Jan> authors with disabilities?

<Jan> - Does the more direct relationship with WCAG 2.0 make the ATAG 2.0

<Jan> requirements more clear?

<Jan> - Are there any other areas in which the guidelines may be lacking?

+1

<AndrewRonksley> +1

<Tim> +1

<Jan> JT, SN: OK

Agenda Setting for the F2F

Split scan document and issue along am and pm lines

<Jan> All: Decide to put issue discussions at TPAC in the afternoon and do the document walkthrough in the morning.

Pisocky registered

http://www.w3.org/WAI/AU/2008/10f2f

<Jan> http://www.w3.org/2002/09/wbs/35125/TPAC2008/

Tracker issues discussion deferred until next week

Will continue to meet once a week until the face to face

<Jan> ACTION: All to register for TPAC and if joining remote - send approx. schedule for joining. [recorded in http://www.w3.org/2008/10/06-au-minutes.html#action02]

<trackbot> Sorry, couldn't find user - All

<Jan> Meeting next Monday

This is scribe.perl Revision: 1.133  of Date: 2008/01/18 18:48:51  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: Greg
Inferring ScribeNick: Greg

WARNING: No "Topic:" lines found.

Default Present: Jan, Greg_Pisocky, SueAnnN, AndrewR, Treviranus, Tim_Boland
Present: Jan Greg_Pisocky SueAnnN AndrewR Treviranus Tim_Boland

WARNING: Replacing previous Regrets list. (Old list: Roberto_S., Jeanne_S.)
Use 'Regrets+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Regrets+ Ann, M.

Regrets: Ann M.
Got date from IRC log name: 06 Oct 2008
Guessing minutes URL: http://www.w3.org/2008/10/06-au-minutes.html
People with action items: all jr

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report