W3C

- DRAFT -

WAI AU

18 Jan 2010

Agenda

See also: IRC log

Attendees

Present
Jeanne, +0208123aaaa, Jan, +0208123aabb, AnnM, Tim_Boland, Jutta, Greg_Pisocky
Regrets
Andrwe_R., SueAnn_N._(partial)
Chair
Jutta Treviranus
Scribe
Greg

Contents


 

 

<Jan> Scribe: Greg

Ourstanding reviews, MSFT, CNIB, Adobe

Pushlist Jeanne tracking on an spreadsheet. Has grown to approximately 70 contacts

Jeanne would like to take time next week to go through the gap analysis

<Jan> JS: Next week - push list gap analysis

Next face to face meeting MSFT would like to host in Redmond in April

Potentially week of April 19, April 26 what works?

AI Jeanne create a survey question to determine best dates for 2 day face to face

Action Jeanne create a survey question to determine best dates for 2 day face to face

<trackbot> Created ACTION-226 - Create a survey question to determine best dates for 2 day face to face [on Jeanne Spellman - due 2010-01-25].

Survey Results

Proposed

A.3.1.1 Keyboard Access (Minimum): All functionality of the *authoring tool* is operable through a *keyboard interface*, except for *freehand drawing*. (Level A)

5 accepted proposals, 1 recommend change

TB would like to verify some of the terms used in this proposal

Jeanne prefers the term "enhanced freehand drawing"

Objections to putting the note but highlighting the term "enhanced freehand drawing" to indicate ongoing search for a more acceptable term?

No objections

<Jan> ACTION: JR to add the proposal on "A.3.1.1 Keyboard Access (Minimum): All functionality of the *authoring tool* is operable through a *keyboard interface*, except for *freehand drawing*" - highlighting "freehand drawing" as a tentative term [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action01]

<trackbot> Created ACTION-227 - Add the proposal on "A.3.1.1 Keyboard Access (Minimum): All functionality of the *authoring tool* is operable through a *keyboard interface*, except for *freehand drawing*" - highlighting "freehand drawing" as a tentative term [on Jan Richards - due 2010-01-25].

No more comments on item 1. On to item 2 rationale for B.2.5

Proposed

Providing accessible templates and other pre-authored content (e.g., clip art, synchronized media, widgets, etc.) has numerous benefits, including: immediately improving the accessibility of content being edited, reducing the effort required of authors, and demonstrating the importance of accessibility.

6 accepts, and 1 tentative accept,

<Jan> JR: Providing accessible templates and other pre-authored content (e.g., clip art, synchronized media, widgets, etc.) can have several benefits, including: immediately improving the accessibility of content being edited, reducing the effort required of authors, and demonstrating the importance of accessibility.

<Jan> ACTION: JR add in the new ratioanle for B.2.5: "Providing accessible templates and other pre-authored content (e.g., clip art, synchronized media, widgets, etc.) can have several benefits, including: immediately improving the accessibility of content being edited, reducing the effort required of authors, and demonstrating the importance of accessibility" [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action02]

<trackbot> Created ACTION-228 - Add in the new ratioanle for B.2.5: "Providing accessible templates and other pre-authored content (e.g., clip art, synchronized media, widgets, etc.) can have several benefits, including: immediately improving the accessibility of content being edited, reducing the effort required of authors, and demonstrating the importance of accessibility" [on Jan Richards - due 2010-01-25].

Next Action, proceed to review comments or go through Jan's actions re: Cynthia's comments?

JRs action items

<Jan> http://lists.w3.org/Archives/Public/w3c-wai-au/2010JanMar/0011.html

Decided to pursue Jan's action items re: Cynthia's comments

JR to Add "Remember" sections in context as proposed text...

Jan: Readers seem to overlook the note indicating this is NOT about automated checking

Any objections to keeping the notes where they are, or should they be improved?

<Jan> Resolution: Keep the notes where they are - no "Remember" section

Notes should stay put. Perhaps adjust the style to make them more prominent, noticeable

Action Investigate ways notes can be more prominent, visible Jan and Jeanne

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

<Jan> ACTION: JS, JR investigate formatting the notes for visibility [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action03]

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

<Jan> ACTION: JR to Link "Check" to a definition in SCB.2.2.1 [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action04]

<trackbot> Created ACTION-229 - Link "Check" to a definition in SCB.2.2.1 [on Jan Richards - due 2010-01-25].

<Jan> Note: While automated checking or more advanced implementations of

<Jan> semi-automated checking are possible for many types of web content

<Jan> accessibility problems, manual checking is the minimum requirement to

<Jan> meet success criteria B.2.2.1, B.2.2.4 and B.2.2.10. In manual checking,

<Jan> the authoring tool provides authors with instructions for detecting

<Jan> problems, which authors must carry out by themselves without further

<Jan> automated assistance. For more information on checking, see Implementing

<Jan> ATAG 2.0 - Appendix B: Levels of Checking Automation.

<Jan> ACTION: JR to Add in this note text: "Note: While automated checking or more advanced implementations of semi-automated checking are possible for many types of web content accessibility problems, manual checking is the minimum requirement to meet success criteria B.2.2.1, B.2.2.4 and B.2.2.10. In manual checking, the authoring tool provides authors with instructions for detecting problems,... [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action05]

<trackbot> Created ACTION-230 - Add in this note text: "Note: While automated checking or more advanced implementations of semi-automated checking are possible for many types of web content accessibility problems, manual checking is the minimum requirement to meet success criteria B.2.2.1, B.2.2.4 and B.2.2.10. In manual checking, the authoring tool provides authors with instructions for detecting problems,... [on Jan Richards - due 2010-01-25].

<Jan> ...which authors must carry out by themselves without further automated assistance. For more information on checking, see Implementing ATAG 2.0 - Appendix B: Levels of Checking Automation."

JR to Take A.3.6 back to drawing board

<Jan> JR: Should we keep A.3.6

<Jan> JT: Question is are there settings related to authoring tools

<Jan> TB: I think we identified settings related to authoring tools

<Jan> Resolution: The WG decides to keep A.3.6

<Jan> ACTION: JR use proposed text for A.3.6.1 "Save Settings: Authoring tool *display settings* and *control settings* are saved between sessions. (Level AA) + Define "control settings" as: Settings that relate to how the author controls the authoring tool, for example using the keyboard or mouse. [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action06]

<trackbot> Created ACTION-231 - Use proposed text for A.3.6.1 "Save Settings: Authoring tool *display settings* and *control settings* are saved between sessions. (Level AA) + Define "control settings" as: Settings that relate to how the author controls the authoring tool, for example using the keyboard or mouse. [on Jan Richards - due 2010-01-25].

<Jan> ACTION: JR to Use proposed text for "A.3.6.2 Multiple Sets: The author(s) can save and reload multiple sets of any authoring tool *display settings* and *control settings*.(Level AAA)" [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action07]

<trackbot> Created ACTION-232 - Use proposed text for "A.3.6.2 Multiple Sets: The author(s) can save and reload multiple sets of any authoring tool *display settings* and *control settings*.(Level AAA)" [on Jan Richards - due 2010-01-25].

<Jan> JR: Proposed: A.3.6.X Respect Platform Settings: The authoring tool respects platform *display settings* and *control settings*. (Level AA) Note: As per Guideline A.2.3, the author's display settings must still be independent of the web content being edited.

<Jan> ACTION: JR to add "A.3.6.X Respect Platform Settings: The authoring tool respects platform *display settings* and *control settings*. (Level AA) Note: As per Guideline A.2.3, the author's display settings must still be independent of the web content being edited." [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action08]

<trackbot> Created ACTION-233 - Add "A.3.6.X Respect Platform Settings: The authoring tool respects platform *display settings* and *control settings*. (Level AA) Note: As per Guideline A.2.3, the author's display settings must still be independent of the web content being edited." [on Jan Richards - due 2010-01-25].

JR to reword proposal with applicability instead of responsibility.

<Jan> JR: Proposed: "Applicability after the *End of an Authoring Sessions*: For *author-generated content*, the requirements of *Part B* apply only during *authoring sessions*. For example, if the *author* includes a third-party feed in their *web content*, the *authoring tool* is not required to provide *checking* for *web content accessibility problems* in that feed after the *end of the...

<Jan> ...authoring session*. In contrast, for *automatically-generated content*, Part B continues to apply after the *end of an authoring session*. For example, if the site-wide templates of a content management system are updated, these would be required to meet the accessibility requirements for *automatically generated content*."

<Jan> ACTION: JR to add in text : ""Applicability after the *End of an Authoring Sessions*: For *author-generated content*, the requirements of *Part B* apply only during *authoring sessions*. For example, if the *author* includes a third-party feed in their *web content*, the *authoring tool* is not required to provide *checking* for *web content accessibility problems* in that feed after the... [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action09]

<trackbot> Created ACTION-234 - Add in text : ""Applicability after the *End of an Authoring Sessions*: For *author-generated content*, the requirements of *Part B* apply only during *authoring sessions*. For example, if the *author* includes a third-party feed in their *web content*, the *authoring tool* is not required to provide *checking* for *web content accessibility problems* in that feed after the... [on Jan Richards - due 2010-01-25].

<Jan> ...*end of the authoring session*. In contrast, for *automatically-generated content*, Part B continues to apply after the *end of an authoring session*. For example, if the site-wide templates of a content management system are updated, these would be required to meet the accessibility requirements for *automatically generated content*."

JR to Write some intent text for B.1.1.1 to explain that instead of accessibility supported uses we took the decision support approach in B.2.1

<Jan> http://lists.w3.org/Archives/Public/w3c-wai-au/2010JanMar/0011.html

<Jan> Resolution: THe WG agrees that the "user supported" requirement in WCAG2 needs to be addressed in ATAG 2.0

<Jan> Resolution: THe WG agrees that the "user supported" requirement in WCAG2 needs to be addressed in the "Relationship to WCAG 2.0" section

<Jan> Resolution: The WG agrees to exempt authoring tools from needing to document "accessibility supported uses of technology" for any references to WCAG2 because it is the installer/author who determines the environment (language, dialect, author group, end user group, etc.) of the authoring tool

<Jan> Resolution: JR, Jeanne will take the final wording to CG

<Jan> ACTION: JR clarify in the "accessibility supported" piece that the onus is on the installer/author [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action10]

<trackbot> Created ACTION-235 - Clarify in the "accessibility supported" piece that the onus is on the installer/author [on Jan Richards - due 2010-01-25].

Cynthia's comments (cont)

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

B.2.2.4 Help Authors Locate....

<Jan> ACTION: JR to Clarify B.2.2.4 comment response [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action11]

<trackbot> Created ACTION-236 - Clarify B.2.2.4 comment response [on Jan Richards - due 2010-01-25].

Summary of Action Items

[NEW] ACTION: JR add in the new ratioanle for B.2.5: "Providing accessible templates and other pre-authored content (e.g., clip art, synchronized media, widgets, etc.) can have several benefits, including: immediately improving the accessibility of content being edited, reducing the effort required of authors, and demonstrating the importance of accessibility" [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action02]
[NEW] ACTION: JR clarify in the "accessibility supported" piece that the onus is on the installer/author [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action10]
[NEW] ACTION: JR to add "A.3.6.X Respect Platform Settings: The authoring tool respects platform *display settings* and *control settings*. (Level AA) Note: As per Guideline A.2.3, the author's display settings must still be independent of the web content being edited." [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action08]
[NEW] ACTION: JR to add in text : ""Applicability after the *End of an Authoring Sessions*: For *author-generated content*, the requirements of *Part B* apply only during *authoring sessions*. For example, if the *author* includes a third-party feed in their *web content*, the *authoring tool* is not required to provide *checking* for *web content accessibility problems* in that feed after the... [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action09]
[NEW] ACTION: JR to Add in this note text: "Note: While automated checking or more advanced implementations of semi-automated checking are possible for many types of web content accessibility problems, manual checking is the minimum requirement to meet success criteria B.2.2.1, B.2.2.4 and B.2.2.10. In manual checking, the authoring tool provides authors with instructions for detecting problems,... [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action05]
[NEW] ACTION: JR to add the proposal on "A.3.1.1 Keyboard Access (Minimum): All functionality of the *authoring tool* is operable through a *keyboard interface*, except for *freehand drawing*" - highlighting "freehand drawing" as a tentative term [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action01]
[NEW] ACTION: JR to Clarify B.2.2.4 comment response [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action11]
[NEW] ACTION: JR to Link "Check" to a definition in SCB.2.2.1 [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action04]
[NEW] ACTION: JR to Use proposed text for "A.3.6.2 Multiple Sets: The author(s) can save and reload multiple sets of any authoring tool *display settings* and *control settings*.(Level AAA)" [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action07]
[NEW] ACTION: JR use proposed text for A.3.6.1 "Save Settings: Authoring tool *display settings* and *control settings* are saved between sessions. (Level AA) + Define "control settings" as: Settings that relate to how the author controls the authoring tool, for example using the keyboard or mouse. [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action06]
[NEW] ACTION: JS, JR investigate formatting the notes for visibility [recorded in http://www.w3.org/2010/01/18-au-minutes.html#action03]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2010/01/18 21:44:43 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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, Jan, +0208123aabb, AnnM, Tim_Boland, Jutta, Greg_Pisocky
Present: Jeanne +0208123aaaa Jan +0208123aabb AnnM Tim_Boland Jutta Greg_Pisocky
Regrets: Andrwe_R. SueAnn_N._(partial)
Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2010JanMar/0019.html
Got date from IRC log name: 18 Jan 2010
Guessing minutes URL: http://www.w3.org/2010/01/18-au-minutes.html
People with action items: a.3.6.1 aa are as authoring between control define display for jr js level proposed relate save saved sessions. settings text that tool use

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


[End of scribe.perl diagnostic output]