WAI_AUWG

 

 

<Greg> http://www.w3.org/WAI/AU/2008/WD-ATAG20-20081025/WD-ATAG20-20081025

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

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

http://www.w3.org/WAI/AU/2008/WD-ATAG20-20081028/#principle-promote-integrate

<scribe> ACTION: JS to remove the note for Principle B.3. Discuss whether to keep the concepts in another location. [recorded in http://www.w3.org/2008/11/17-au-minutes.html#action01]

<trackbot> Created ACTION-45 - Remove the note for Principle B.3. Discuss whether to keep the concepts in another location. [on Jeanne Spellman - due 2008-11-24].

Authors are most likely to use the first and easiest authoring action they encounter, therefore the first and easiest action should produce the most accessible result.

<scribe> ACTION: JS to put the proposed wording for B.3.1 rationale in next week's survey [recorded in http://www.w3.org/2008/11/17-au-minutes.html#action02]

<trackbot> Created ACTION-46 - Put the proposed wording for B.3.1 rationale in next week's survey [on Jeanne Spellman - due 2008-11-24].

B.3.1.1 Accessible Options have Equal Prominence

If authors are provided with options, then accessible actions are at least as prominent as other actions.

B.3.1.1 Accessible Options have Equal Prominence: If authors are provided with options to achieve the same outcome, then options with an accessible outcome are at least as prominent as other actions.

B.3.1.1 Accessible Options have Equal Prominence: If authors are provided with options to achieve the same outcome, then those options with an accessible outcome are at least as prominent as other actions.

B.3.1.1 Accessible Options have Equal Prominence: If authors are provided with options that result in similar outcomes, then those options with an accessible outcome are at least as prominent as other actions.

B.3.1.1 Accessible Options have Equal Prominence: If authors are provided with options that result in similar outcomes, then those options with an accessible outcome are at least as prominent as other options.

GP: prominence definition is missing the ease of navigation to the options - burying levels deep in Properties dialog, for example.

JT: We should includean example of an accessible vs. inaccessible template in 3.1.1

<scribe> ACTION: JS to include new wording for 3.1.1 and 3.1.2 for this week's survey [recorded in http://www.w3.org/2008/11/17-au-minutes.html#action03]

<trackbot> Created ACTION-47 - Include new wording for 3.1.1 and 3.1.2 for this week's survey [on Jeanne Spellman - due 2008-11-24].

<Greg> ACTION: GP to write example for 3.1.1.1 [recorded in http://www.w3.org/2008/11/17-au-minutes.html#action04]

<trackbot> Created ACTION-48 - Write example for 3.1.1.1 [on Greg Pisocky - due 2008-11-24].

<scribe> ACTION: JS to draft an additional bullet for definition of Prominence to include ease of navigation [recorded in http://www.w3.org/2008/11/17-au-minutes.html#action05]

<trackbot> Created ACTION-49 - Draft an additional bullet for definition of Prominence to include ease of navigation [on Jeanne Spellman - due 2008-11-24].

B.3.1.2 Accessible Options have More Prominence: If authors are provided with options that result in similar outcomes, then those options with an accessible outcome are given greater prominence than other options.

B.3.1.2 Accessible Options have Greater Prominence: If authors are provided with options that result in similar outcomes, then those options with an accessible outcome are given greater prominence than other options.

<scribe> ACTION: JS to add new wording of B.3.1.2 to next week's survey [recorded in http://www.w3.org/2008/11/17-au-minutes.html#action06]

<trackbot> Created ACTION-50 - Add new wording of B.3.1.2 to next week's survey [on Jeanne Spellman - due 2008-11-24].

B.3.2 Integrate the accessible authoring practices into the workflow.

<Greg> B.3.2.1 Sequencing features: The application has to present all of the accessible options prior to completing the action

<scribe> ACTION: JT to draft a proposal to reword B.3.2.1 and 3.2.2 [recorded in http://www.w3.org/2008/11/17-au-minutes.html#action07]

<trackbot> Created ACTION-51 - Draft a proposal to reword B.3.2.1 and 3.2.2 [on Jutta Treviranus - due 2008-11-24].

<Greg> B.3.2.2 Sequence instuctions, the instructions for a given task must include all of the accessibility inclusion details prior to completing the sequence of instructions

next meeting on Nov 24

<Greg> Next meeting, Monday November 24, 2008

<scribe> chair: Jutta, Jeanne

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)

Succeeded: s/We should include /JT: We should include/
Found embedded ScribeOptions:  -final

*** RESTARTING DUE TO EMBEDDED OPTIONS ***

No ScribeNick specified.  Guessing ScribeNick: jeanne
Inferring Scribes: jeanne

WARNING: No "Topic:" lines found.

Default Present: jeanne, Greg_Pisocky, Sueann, Jutta
Present: Greg Jeanne Sueann Jutta
Regrets: jan tim
Got date from IRC log name: 17 Nov 2008
Guessing minutes URL: http://www.w3.org/2008/11/17-au-minutes.html
People with action items: gp js jt

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