Tracker cleanup

<JR> http://www.w3.org/WAI/AU/tracker/issues/

<JR> http://www.w3.org/WAI/AU/tracker/actions/

<JR> http://www.w3.org/WAI/AU/2008/WD-ATAG20-20081028/

<JR> ACTION: TB to Look at authoring tool definition wrt to conformance section. [recorded in http://www.w3.org/2008/11/10-au-minutes.html#action01]

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

<JR> http://www.w3.org/WAI/AU/2008/WD-ATAG20-20081028/#intro-rel-wcag

<JR> http://www.w3.org/WAI/AU/2008/WD-ATAG20-20081028/#intro-conf-levels

<JR> Scribe: Greg

B.2.2 Checking

<JR> JR's proposal http://lists.w3.org/Archives/Public/w3c-wai-au/2008OctDec/0039.html

<JR> http://www.w3.org/WAI/AU/2008/WD-ATAG20-20081025/WD-ATAG20-20081025#gl-checking

<JR> B.2.2.32 Help Authors Locate: For any checks that require author judgment to determine whether a potential accessibility problem is correctly identified (i.e., manual checking and semi-automated checking), the relevant content is identified (e.g., displaying the surrounding text, "Is a sign lanuage interpretation provided?") (Level A)

<JR> B.2.2.4 Help Authors Decide: For any checks that require author judgment to determine whether a potential accessibility problem is correctly identified (i.e., manual checking and semi-automated checking), instructions are provided to help authors to decide. (Level A)

<JR> B.2.2.3 Support Decision-Making: Assist authors to determine whether

<JR> potential accessibility problems are correctly identified (Level A):

<JR> - For automated checks: nothing further is required.

<JR> - For semi-automated checks: potential problems are identified (e.g.,

<JR> by highlighting, by line number) and author instructions explain how

<JR> to decide if a problem exists (e.g., "when an image needs a long

<JR> description").

<JR> - For manual checks: author instructions explain how to locate

<JR> potential problems (e.g., "Check each IMG element") and further author

<JR> instructions explain how to decide if a problem exists.

<JR> rem: "- For automated checks: nothing further is required."

<JR> B.2.2.5 Display Status: Provide authors with the option of viewing the

<JR> accessibility status of content being edited, prior to publishing

<JR> (e.g., list remaining accessibility problems). (Level AA)

<JR> - For automated checks: display identified problems.

<JR> - For semi-automated checks: display potential problems that were

<JR> confirmed by authors.

<JR> - For manual checks: display potential problems that were confirmed by

<JR> authors.

Guideline B.2.4 Assist authors to manage, edit, and reuse equivalent alternatives for non-text objects.

<JR> Old:

<JR> B.2.4.1 Accept, Modify, Reject: Authors have the opportunity to accept, modify, or reject any authoring tool-supplied equivalent alternative, prior to insertion. (Level A)

<JR> B.2.4.2 Edit Existing: If the authoring tool is capable of adding equivalent alternatives for a type of non-text objects then authors can edit the equivalent alternatives. (Level A)

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

<JR> B.2.4.1 Existing alternatives: If the authoring tool suggests existing

<JR> alternatives for author-selected non-text objects (e.g., previous

<JR> author entry, description from an image database description), provide

<JR> authors with the opportunity to accept, modify, or reject the

<JR> alternatives, prior to insertion. (Level A)

<JR> Applicability Note:

<JR> - This guideline does not apply to non-text objects that are

<JR> automatically added by the authoring tool. These are covered by

<JR> Guideline B.1.3.

<JR> JR: Don't just hide it from the author

<JR> GP: That's good

<JR> Note: Equivalent alternatives should not be automatically generated from unreliable sources (e.g., file names should not be used as text alternatives)@@.

<JR> B.2.4.2 Automatically generated alternatives: If the authoring tool

<JR> has the option of automatically generating alternatives for

<JR> author-selected non-text objects, both of the following must be true

<JR> (Level A):

<JR> - only alternatives that result from audio and/or video analysis of

<JR> the actual objects is acceptable (e.g., speech recognition). Use of

<JR> unreliable information (e.g., the file name, arbitrary numbering) is

<JR> not acceptable.

<JR> - authors are provided with the opportunity to accept, modify, or

<JR> reject the alternatives, prior to insertion.

<JR> ACTION: JR to Follow up with Jeanne on starting a weekly survey [recorded in http://www.w3.org/2008/11/10-au-minutes.html#action02]

<trackbot> Created ACTION-44 - Follow up with Jeanne on starting a weekly survey [on Jan Richards - due 2008-11-17].

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

WARNING: 1 scribe lines found (out of 113 total lines.)
Are you sure you specified a correct ScribeNick?

Default Present: Greg_Pisocky, Jan, Sueann, TimB, +044208123aabb, AnneM
Present: Greg_Pisocky Jan Sueann TimB +044208123aabb AnneM

WARNING: Replacing previous Regrets list. (Old list: Jutta, T.)
Use 'Regrets+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Regrets+ Andrew, R

Regrets: Andrew R
Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2008OctDec/0041.html

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 10 Nov 2008
Guessing minutes URL: http://www.w3.org/2008/11/10-au-minutes.html
People with action items: jr tb