See also: IRC log
<Jan> Scribe: SueAnn
<Jan> http://lists.w3.org/Archives/Public/w3c-wai-au/2009OctDec/0055.html
<Jan> GP: Thinks Adobe comments can be delivered by Dec 21
<Jan> SN: More IBM comments coming - will be posting by tomorrow
<Jan> TB: No comments so far
<Jan> JR: Needs to follow up on comments from around here + Reed from Microsoft says he has sonme
<Jan> http://www.w3.org/2009/12/07-au-minutes.html#ActionSummary
GP: Thought this was close,
<Jan> http://lists.w3.org/Archives/Public/w3c-wai-au/2009OctDec/0050.html
thought this was closed
GP will run the language by Adobe one more time
Jan requested everyone review A.3.1.5 Keyboard language, Message 50
<Jan> http://lists.w3.org/Archives/Public/w3c-wai-au/2009OctDec/0058.html
Applicability Notes - "image label" should be text alternative -
<Jan> ACTION: JR to Change: "image label" to "text alternative" [recorded in http://www.w3.org/2009/12/14-au-minutes.html#action01]
<trackbot> Created ACTION-212 - Change: "image label" to "text alternative" [on Jan Richards - due 2009-12-21].
A.3.1.2 - JR has a recommendation, but defer for a while
<Jan> ACTION: JR to Change A.3.1.3 "No Keyboard Traps" [recorded in http://www.w3.org/2009/12/14-au-minutes.html#action02]
<trackbot> Created ACTION-213 - Change A.3.1.3 "No Keyboard Traps" [on Jan Richards - due 2009-12-21].
<Jan> http://jan.atrc.utoronto.ca/public/atag/MASTER-20091130.html
<Jan> http://jan.atrc.utoronto.ca/public/atag/MASTER-20091130.html#sc_a315
Jan reviewed UAWG 2 working to see if there was something there that would model what's needed for key keyboard shortcuts.
Jean recommends the UAAG 2.0 working 4.1.8 Important Command Functions: Important command functions (e.g.
related to navigation, display, content, information management, etc.)
are available using a single or sequence of keystrokes or key
combinations. (Level AA)
<Jan> ACTION: JR to re: A.3.1.5 Keyboard Shortcuts - current wording is OK - but needs justification (perhaps more intent) [recorded in http://www.w3.org/2009/12/14-au-minutes.html#action03]
<trackbot> Created ACTION-214 - Re: A.3.1.5 Keyboard Shortcuts - current wording is OK - but needs justification (perhaps more intent) [on Jan Richards - due 2009-12-21].
<Jan> JR: Plus they have this requirement which is quite useful:
<Jan> 4.1.12 Present Direct Commands in User Interface: The user has the
<Jan> option to have any direct commands (e.g. keyboard shortcuts) in the user
<Jan> agent user interface be presented with their associated user interface
<Jan> controls (e.g. "Ctrl+S" displayed on the "Save" menu item and toolbar
<Jan> button). (Level AA)
<Jan> http://www.w3.org/WAI/UA/2009/ED-UAAG20-20091105/#principle-operable
<Jan> SN: OK at AAA
<Jan> GP: OK
<Jan> JS: Would like to see it in
<Jan> ACTION: JR to To propose a way to bring a req like UAAG2 4.1.12 Present Direct Commands in User Interface into ATAG2 at Level AAA [recorded in http://www.w3.org/2009/12/14-au-minutes.html#action04]
<trackbot> Created ACTION-215 - Propose a way to bring a req like UAAG2 4.1.12 Present Direct Commands in User Interface into ATAG2 at Level AAA [on Jan Richards - due 2009-12-21].
<Jan> A.3.1.6 Drawing Keyboard Access (Enhanced): Any drawing functionality of the authoring tool is operable through a keyboard interface. (Level AAA) [Implementing A.3.1.6]
<Jan> Note 1: It is possible to implement keyboard access directly (e.g., keyboard-driven manipulation of drawing objects) or indirectly (e.g., keyboard editing of drawing object property values).
<Jan> Note 2: This success criterion should not be interpreted as discouraging mouse input or other input methods in addition to keyboard operation.
Jan does not feel we should be requiring one method over the other
JS agrees
<Jan> ACTION: JR to Propose rewording of A.3.1.6 to include both direct and indirect authoring. [recorded in http://www.w3.org/2009/12/14-au-minutes.html#action05]
<trackbot> Created ACTION-216 - Propose rewording of A.3.1.6 to include both direct and indirect authoring. [on Jan Richards - due 2009-12-21].
Comment: A.3.2.1 Data Saved
>
> Note: For web-based authoring tools, this applies to any web content
> that has already been submitted to the server by the user agent.
>
> I wonder if it would make sense to have a AAA SC that provides for
> automatically submitting content in such a system?
JS Agrees
GP Ok
<Jan> ACTION: JR to Propose wording for a "Data Saved (Extended) Level AAA" [recorded in http://www.w3.org/2009/12/14-au-minutes.html#action06]
<trackbot> Created ACTION-217 - Propose wording for a "Data Saved (Extended) Level AAA" [on Jan Richards - due 2009-12-21].
SN Ok
Comment: A.3.5.1 Text Search: The author(s) can perform text searches of web
> content in which all of the following are true: (Level AA)
>
> (a) Search All Editable: The search can be within any information that
> is text and that the authoring tool can modify (e.g., text content, text
> alternatives for non-text content, metadata, markup elements and
> attributes, etc.); and
>
> Does "The search can be" mean "The search MUST be" or "The search MAY be"?
<Jan> ACTION: JR to Reword A.3.5.1 to "Any information that is text and that the authoring tool can modify is searchable." [recorded in http://www.w3.org/2009/12/14-au-minutes.html#action07]
<trackbot> Created ACTION-218 - Reword A.3.5.1 to "Any information that is text and that the authoring tool can modify is searchable." [on Jan Richards - due 2009-12-21].
SN Agree
Comment: > Note: If the current editing view is not able to display the results of
> a search then the authoring tool may switch to a different editing view
> to display the results (e.g., to a source content editing view to
> display search results within markup tags).
>
> I would hope that the authoring tool won't do this automatically, as
> that could be quite unexpected and jarring. Perhaps this should say
> that the authoring tool could provide a mechanism for the author to switch?
<jeanne> Note: If the current editing view is not able to display the results of
<jeanne> > a search then the authoring tool may switch to a different editing view
<jeanne> > to display the results (e.g., to a source content editing view to
<jeanne> > display search results within markup tags).
<jeanne> Note: If the current editing view is not able to display the results of
<jeanne> a search then the authoring tool may switch to a different editing view
<jeanne> to display the results (e.g., to a source content editing view to
<jeanne> display search results within markup tags).
<jeanne> then the authoring tool may provide a mechanism to switch to a different editing view...
Jan - Ok
<Jan> ACTION: JR to In A.3.5.1 Note to insert "then the authoring tool may provide a mechanism to switch to a different editing view..." NAD to add example of a switch mechanism such as listing the editing view that will open in the search results list [recorded in http://www.w3.org/2009/12/14-au-minutes.html#action08]
<trackbot> Created ACTION-219 - In A.3.5.1 Note to insert "then the authoring tool may provide a mechanism to switch to a different editing view..." NAD to add example of a switch mechanism such as listing the editing view that will open in the search results list [on Jan Richards - due 2009-12-21].
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: SueAnn Inferring ScribeNick: Sueann Default Present: Jeanne, Jan, Greg_Pisocky, SueAnn, +1.410.723.aaaa Present: +1.410.723.aaaa Greg_Pisocky Jan Jeanne SueAnn Tim_Boland(partial) Regrets: Jutta T. Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2009OctDec/0055.html Got date from IRC log name: 14 Dec 2009 Guessing minutes URL: http://www.w3.org/2009/12/14-au-minutes.html People with action items: jr WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]