I am online

<scribe> ACTION: Greg and Jeanne details for face to face [recorded in http://www.w3.org/2009/04/27-au-minutes.html#action01]

<trackbot> Created ACTION-141 - And Jeanne details for face to face [on Greg Pisocky - due 2009-05-04].

<Jan> scribe: Greg

Face to face dates June 15 and 16, 2009 Adobe offices in McLean VA

Goal is to come out of f 2 f with last call draft

<Jan> http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0023.html

Today's Agenda:

<scribe> Agenda:

1. TB's comments with JR's proposals:

http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0014.html

2. GPs issue re: examples of tools

http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0018.html

http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0022.html

3. External comments on public draft:

http://lists.w3.org/Archives/Public/public-atag2-comments/2009Mar/0000.html

Jutta asks are there documents needed to accompany the last call draft in order to be prepared to issue it as the outcome of the face to face meeting

Jan indicates Guidelines is the only document that is normative

<jeanne> ACTION: JS to research any necessary preparation for Last Call draft to be completed before the F2F. [recorded in http://www.w3.org/2009/04/27-au-minutes.html#action02]

<trackbot> Created ACTION-142 - Research any necessary preparation for Last Call draft to be completed before the F2F. [on Jeanne Spellman - due 2009-05-04].

Authoring Tool examples

<Jan> http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0018.html

Item 2 will be first in today's agenda 2. GPs issue re: examples of tools

[16:11] http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0018.html

[16:11] http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0022.html

<Jan> Current wording: http://www.w3.org/TR/ATAG20/#intro-def-au

<Jan> http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0022.html

<Jan> Old:The definition applies to all or part of the following types of applications:

<Jan> •WYSIWYG editors, plain text editors (embedded and stand-alone)

<Jan> •conversion tools, software that can output Web content technologies (e.g., "Save as HTML")

<Jan> •blogging tools, wikis, online forums, emailers that produce Web-content

<Jan> •multimedia authoring tools

<Jan> •scripting tools, widget development environment

<Jan> •content management systems, courseware tools, content aggregators

<Jan> •site management tools

<Jan> •others

<Jan> NEW: Notes on the Definition:

<Jan> 1. ATAG 2.0 applies to a wide variety of *Web content* generating

<Jan> applications, such as:

<Jan> - "conventional" webpage authoring tools (e.g., WYSIWYG HTML editors)

<Jan> - software for directly editing source code (e.g., text editors)

<Jan> - software for *converting* to *Web content technologies* (e.g., "Save

<Jan> as HTML" features in office suites)

<Jan> - integrated development environments (e.g., for DHTML)

<Jan> - software that generates Web content on the basis of templates,

<Jan> scripts, command-line input or wizard processes

<Jan> - software for rapidly updating portions of webpages (e.g., blogging,

<Jan> wikis, online forums)

<Jan> - software for generating/managing entire sites (e.g., content

<Jan> management systems, courseware tools, content aggregators)

<Jan> - email clients that send messages in Web content technologies

<Jan> - multimedia authoring tools

<Jan> GP: I like it , casts a sufficient net...covers all categories likely to encounter

<Jan> - integrated development environments (e.g., for Web Application development)

Jutta looking to inlcude the phrase "include but is not limited to"

<Jan> JT: "applications, such as" => "including, but not limited to:"

<jeanne> +1

+1

<Jan> 1. ATAG 2.0 applies to a wide variety of *Web content* generating

<Jan> applications, including, but not limited to:

<Jan> - "conventional" webpage authoring tools (e.g., WYSIWYG HTML editors)

<Jan> - software for directly editing source code (e.g., text editors)

<Jan> - software for *converting* to *Web content technologies* (e.g., "Save

<Jan> as HTML" features in office suites)

<Jan> - integrated development environments (e.g., for Web Application development)

<Jan> - software that generates Web content on the basis of templates,

<Jan> scripts, command-line input or wizard processes

<Jan> - software for rapidly updating portions of webpages (e.g., blogging,

<Jan> wikis, online forums)

<Jan> - software for generating/managing entire sites (e.g., content

<Jan> management systems, courseware tools, content aggregators)

<Jan> - email clients that send messages in Web content technologies

<Jan> - multimedia authoring tools

<jeanne> ACTION: JS to update the definition of authoring tool from the introduction with the edits above. [recorded in http://www.w3.org/2009/04/27-au-minutes.html#action03]

<trackbot> Created ACTION-143 - Update the definition of authoring tool from the introduction with the edits above. [on Jeanne Spellman - due 2009-05-04].

<Jan> Here are the other two notes:

<Jan> 2. Any guidelines that require *authors* to modify content in some way

<Jan> always assumes that the person has *author permission*.

<Jan> 3. Applications that are used to create content in real time (e.g.,

<Jan> chats, collaboration tools, whiteboards, etc.) should attempt to conform

<Jan> at least to Part A. In addition, many of the guidelines in Part B may

<Jan> also apply, especially if the application has an archiving feature. For

<Jan> more information, see the Techniques: Appendix E: Real-time content

<Jan> production.

Changes from TB,JR

<Jan> http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0014.html

Item 2 TB went through the document to verify the definitions

<Jan> > 2.1.4:

<Jan> > available programmatically

<Jan> CURRENT:

<Jan> image label present in the content is available programmatically

<Jan> PROPOSED:

<Jan> image label present in the content is available via a *platform

<Jan> accessibility architecture*

<Jan> All: No objections

<Jan> > A.2.2.1:

<Jan> > functional purpose

<Jan> CURRENT:

<Jan> the functional purpose for the modification

<Jan> PROPOSED:

<Jan> a description of the purpose of the modification

<Jan> All: No objections

<Jan> > A.2.2.2:

<Jan> > WYSIWYG (need to spell out?)

<Jan> PROPOSED: New term:

<Jan> WYSIWYG

<Jan> This is an acronym for "What You See Is What You Get". A WYSIWYG user

<Jan> interface displays (to authors) the content being edited in a way that

<Jan> is very similar to how it will appear to end users.

<Jan> All: No objections

<Jan> > keyboard trap

<Jan> PROPOSED: New term:

<Jan> keyboard trap

<Jan> A user interface phenomenon in which the keyboard may be used to move

<Jan> focus to, but not from, a control or group of controls.

<Jan> A user interface situation in which the keyboard may be used to move focus to, but not from, a control or group of controls.

<jeanne> +1

<Jan> All: No objections

<Jan> > A.3.2.3:

<Jan> > moving target

<Jan> > selectable component

<Jan> CURRENT:

<Jan> If the user interface includes any moving targets for authors' actions

<Jan> (e.g.,a selectable component of an animation), then authors can stop

<Jan> that movement.

<Jan> PROPOSED:

<Jan> If a user interface component that accepts mouse input is capable of

<Jan> movement (e.g., animated vector graphic), provide authors with the

<Jan> option to stop the movement.

<Jan> All: No objections.

<Jan> > A.3.3.1:

<Jan> > static view

<Jan> > time-based content

<Jan> > fixed state

<Jan> CURRENT:

<Jan> If an editing view renders content (e.g., WYSIWYG) then the author has

<Jan> the global option of a static view in which time-based content appears

<Jan> in a fixed state.

<Jan> PROPOSED:

<Jan> If an editing view renders time-based content (e.g., animations),

<Jan> provide authors with the global option of rendering only the initial

<Jan> state of time-based content.

<Jan> All: No objections

<Jan> > A.3.4.4:

<Jan> > Doesn't above, below, preceding, etc. depend on navigation order?

<Jan> OPEN ISSUE: Is this really unclear?

<Jan> A.3.4.4 Navigate Tree Structures: If an editing view displays a structured element set, authors can, with a simple action, move the editing focus from any element to other elements in the set with any of the following relationships (if they exist) (Level AA):

<Jan> •(a) Parent: the element immediately above,

<Jan> •(b) Child: the first element immediately below,

<Jan> •(c) Previous Sibling: the element immediately preceding at the same level, and

<Jan> •(d) Next Sibling: the element immediately following at the same level.

<Jan> All: Group is ok with current wording

<Jan> > accessibility option-setting "wizard"

<Jan> CURRENT:

<Jan> ...an accessibility option-setting "wizard" to configure options related

<Jan> to Part A

<Jan> PROPOSED:

<Jan> ..."wizard"-type feature that helps them to configure any

<Jan> accessibility-related preference settings related to Part A

<Jan> A.3.6.3 Options Wizard: Authors are provided with an accessibility option-setting "wizard" to configure options related to Part A. (Level AAA)

<Jan> JT: INteractive dialog

<Jan> A.3.6.3 Interactive Options Assistance: An interactive dialog helps helps with configure options related to Part A. (Level AAA)

<Jan> A.3.6.3 Interactive Options Assistance: An interactive mechanism helps authors configure options related to Part A. (Level AAA)

<Jan> All: No objections

<Jan> A.3.6.3 Options Assistance: An interactive mechanism helps authors configure options related to Part A. (Level AAA)

<Jan> All: No objections

<Jan> > A.3.7.1:

<Jan> > help system

<Jan> CURRENT:

<Jan> If a preview is provided, then it is possible to return from the preview

<Jan> using a simple action which is documented in the help system.

<Jan> PROPOSED:

<Jan> If a *preview* is provided, provide a *documented* keyboard accessible

<Jan> mechanism for returning to an *editing view* from the preview.

<Jan> All: No objections

<jeanne> +1

<Jan> > A.4.1.1:

<Jan> > irreversible

<Jan> CURRENT:

<Jan> reversible actions

<Jan> Authoring actions that, by their nature, can be completely undone so

<Jan> that the system returns to the state it was in before the action.

<Jan> Actions that are not reversible may include certain save and delete

<Jan> actions as well as actions made in a collaborative environment that

<Jan> another author has begun to work with.

<Jan> PROPOSED:

<Jan> reversible actions

<Jan> Authoring actions that, by their nature, can be completely undone so

<Jan> that the system returns to the state it was in before the action.

<Jan> *Irreversible actions* are actions that cannot be reversed and may

<Jan> include certain save and delete actions as well as actions made in a

<Jan> collaborative environment that another author has begun to work with.

<Jan> All: No objections

<Jan> > third-party feed

<Jan> CURRENT:

<Jan> third-party feed

<Jan> PROPOSED:

<Jan> an RSS feed from a third-party

<Jan> All: No objections

<Jan> JT: Actually...

<Jan> Responsibility After Authoring Sessions: Authoring tools are not responsible for accessibility problems that result from carrying out instructions made by the author during authoring sessions (e.g., the content of a third-party feed specified by the author), but they are responsible if the changes are automatically generated (e.g., the developer makes site wide changes to a CMS).

<Jan> JT: Let's use "third-pary content"

<Jan> ACTION: Jan to Track down our text re: passing through content authored on other tools [recorded in http://www.w3.org/2009/04/27-au-minutes.html#action04]

<trackbot> Created ACTION-144 - Track down our text re: passing through content authored on other tools [on Jan Richards - due 2009-05-04].

Next meeting May 11, 2009

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: Greg
Inferring ScribeNick: Greg
Default Present: Jeanne, +0208123aaaa, AnnM, Andrew, +1.703.678.aabb, Jan, GregP, Tim_Boland, JuttaT, [IPcaller]
Present: Jeanne +0208123aaaa AnnM Andrew +1.703.678.aabb Jan GregP Tim_Boland JuttaT [IPcaller]
Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0023.html
Got date from IRC log name: 27 Apr 2009
Guessing minutes URL: http://www.w3.org/2009/04/27-au-minutes.html
People with action items: details face for greg jan jeanne js

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