<scribe> Scribe: Jan

https://www.w3.org/2002/09/wbs/35520/atag20120229/results

A.3.2.3 Conditional Proposal

https://www.w3.org/2002/09/wbs/35520/atag20120229/results#xq5

A.3.2.3 Static Pointing Device Targets: If authoring tool user interface components that accept input also move, then authors can pause the movement. (Level A)

A.3.2.3 Static Pointing Device Targets: If authoring tool user interface components accept input and move, then authors can pause the movement. (Level A)

A.3.2.3 Static Input Components: If authoring tool user interface components accept input and move, then authors can pause the movement. (Level A)

Tim: Should be consistent as possible and well defined

JT: Any concerns?

Resolution: All accept: "A.3.2.3 Static Input Components: If authoring tool user interface components accept input and move, then authors can pause the movement. (Level A) "

B.1.1.1 Conditional Proposal

http://www.w3.org/WAI/AU/2012/ED-ATAG20-20120229/#sc_b411

B.4.1.1 Features Active by Default: All accessible content support features are turned on by default.

If the authoring tool provides the functionality of generating web content automatically after the end of an authoring session, authors can specify that the content be accessible web content (WCAG).

A.3.2.3 handles the fact that that is default option

B.1.1.1 Content Auto-Generation After Authoring Sessions (WCAG): If the authoring tool provides the functionality of generating web content automatically after the end of an authoring session, authors can specify that the content be accessible web content (WCAG).

(just adding handle)

Resolution: For A351All accept "If the authoring tool provides an editing-view of text-based content then editing-views enable text search, such that all of the following are true:"

B.1.1.1 Content Auto-Generation After Authoring Sessions (WCAG): If the authoring tool provides the functionality of generating web content automatically after the end of an authoring session, authors can specify that the content be accessible web content (WCAG). Resolution: All accept:

Resolution: All accept "If the authoring tool provides the functionality of generating web content automatically during an authoring session, then one of the following is true:"

A.1.2.1

JT: minor grammatical: If the authoring tool contains non-web-based user interfaces, then the non-web-based authoring tool user interfaces follow user interface accessibility guidelines for the platform. (Level A)

<scribe> ACTION: JR to Add note to clarify " I assume this would not cover keyboard commands based on the parent software? e.g. browser based keyboard controls would not need to be customized, only tool-specific controls." [recorded in http://www.w3.org/2012/03/05-au-minutes.html#action01]

<trackbot> Created ACTION-373 - Add note to clarify " I assume this would not cover keyboard commands based on the parent software? e.g. browser based keyboard controls would not need to be customized, only tool-specific controls." [on Jan Richards - due 2012-03-12].

Another small one: "A.4.1.2 Settings Change Confirmation: If the authoring tool provides mechanisms for changing the user interface, then those mechanisms can reverse the changes, or the authoring tool requires author confirmation to proceed."

Another small one: "B.3.1.3 Help Authors Locate: If the authoring tool provides checks that require authors to decide whether a potential web content accessibility problem is correctly identified (i.e., manual checking and semi-automated checking), then the relevant content is identified to the authors. (Level A) "

JT: Seemsd we have closure on these issues...
... Which is wonderful
... Further issues

2. Last Call publishing planning

JS: Next step is last call vote...

GP: If vote in favour? Not in favour?

JS: If not in favour: We keep working

JR: Should we make the changes and then have a survey vote?

JS: Explains that last call phase is the start of call for implementations
... Only after we have shown real-world implementation can we move ahead to Recommendation

'RRSAgent, make minutes

This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: Jan
Inferring ScribeNick: Jan
Default Present: Alex, Jan, Jeanne, Jutta, Tim_Boland, Greg, Cherie
Present: Alex Jan Jeanne Jutta Tim_Boland Greg Cherie
Regrets: Andrew_R. Greg_P.
Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2012JanMar/0036.html
Got date from IRC log name: 05 Mar 2012
Guessing minutes URL: http://www.w3.org/2012/03/05-au-minutes.html
People with action items: jr

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