See also: IRC log
Hi Jeanne
<jeanne> I'm going to call nback in
I'll do some minuting
<Jan> http://lists.w3.org/Archives/Public/w3c-wai-au/2010JulSep/0070.html
<Jan> Scribe: gpisocky
Discussion of Next Steps in View of Comments Received
Originally our intent was to use F2F for candidate recommendation. However, there have been substantive reviews. Shall the group attempt to proceed with last call or work on a better working draft?
<Jan> http://lists.w3.org/Archives/Public/public-atag2-comments/2010Sep/
Jan has issued a draft agenda
Day 1 8:30 - 5:30 and day 2 8:30 to 5:00 pm eastern time
Adobe Offices in McLean, 8201 Greensboro Dr., Suite 1000 (10th florr) McLean, VA 22102
<jeanne> http://www.w3.org/WAI/AU/2010/09f2f.html
<Jan> http://lists.w3.org/Archives/Public/w3c-wai-au/2010JulSep/0069.html
Issues that can be addressed prior to the F2F
1st link are the proposals, and the second link is the last call comments (use newer link) representing the table of all comments
<Jan> Resolution: Use "editing-view" instead of "editing view" to avoid confusion with editing a view.
<Jan> Reflected web content accessibility problems: The authoring tool is responsible for ensuring that editing-views display the web content being edited in a way that is accessible to authors with disabilities (e.g., ensuring that text alternatives in the content can be programmatically determined). However, where an accessibility problem is caused directly by the content being edited (e.g., if...
<Jan> ...an image in the content lacks a text alternative), then this would not be considered a deficiency in the accessibility of the user interface.
<Jan> Resolution: Accept (2) Part A: Applicability Note #2: Rewording without change in normative meaning (addresses: GG1, AC1)
<Jan> Applicability after the end of an authoring session: Authoring tools are responsible for the accessibility of content that they automatically generate after the end of an author's authoring session. For example, if the developer changes the site-wide templates of a content management system, these would be required to meet the accessibility requirements for automatically-generated content....
<Jan> ...Authoring tools are not responsible for changes to the accessibility of content that the author has specified, whether it is author-generated or automatically-generated by another system that the author has specified (e.g., a third-party feed).
<Jan> Resolution: Accept (3) Part B: Applicability Note #2: Rewording without change in normative meaning (addresses: MS1)
<Jan> Resolution: Accept (4) Part B: Applicability Note #3: Rewording without change in normative meaning (addresses: GG2)
<Jan> It is important to note that, while the requirements for meeting these two sets of user needs are separated for clarity within the guidelines, the accelerating trend toward user-produced content means that in reality they are deeply inter-connected. For example, when a user participates in an online forum they frequently author web content that is then incorporated with other content...
<Jan> ...authored by other users. Accessibility problems in either the authoring user interface or the web content produced by the other forum users would reduce the overall accessibility of the forum.
<Jan> Resolution: Accept: (5) Proposal: http://lists.w3.org/Archives/Public/w3c-wai-au/2010JulSep/0065.html
<Jan> Resolution: Move "Claimants are encouraged to claim conformance to the most recent version of the Authoring Tool Accessibility Guidelines Recommendation." into the text under Conformance Claims (Optional).
<Jan> Resolution: Accept (7) Use () instead of [] for repeated "[For authoring tool user interface]" in Part A. (addresses: GG4)
<Jan> Resolution: Accept (8) Rewording without change in normative meaning (addresses: UAWG2, MS5) A.2.1.1 Recognized Alternative Content: If content is rendered in editing-views, recognized alternative content can be programmatically determined.
<Jan> (9) Rewording without change in normative meaning (addresses: JC1) and move to A.3.6.X (addresses: MS7) A.2.3.1 Independence of Display: Authors can set their own display settings for editing views without affecting the web content to be published.
<Jan> Resolution: Accept (9) Rewording without change in normative meaning (addresses: JC1) and move to A.3.6.X (addresses: MS7) A.2.3.1 Independence of Display: Authors can set their own display settings for editing views without affecting the web content to be published.
<Jan> Resolution:To add "accessible documentation" to each of A.4.2.1 and A.4.2.2
<Jan> Resolution: Accept (11) Remove this informative (and outdated) line from B.1.3 (addresses: WCAGWG16) If accessibility information is required from authors during the automatic generation process, see Guideline B.2.1.
<Jan> Resolution: Accept (12) Fix typo (addresses: WCAGWG18) B.2.3.1: Typo refers to Guideline B.2.2 should be, "as required by SC B.2.2.1."
<Jan> Resolution: Accept (13) Rewording without change in normative - Changing the handle for "B.2.4.2 Automated suggestions" (addresses: GG6, MS34) B.2.4.2 Conditions for automated suggestions:
<Jan> Resolution: (14) Reword but doesn't change normative meaning: (addresses: MS38) B.3.2.2 Reactivate Option: If authors can turn off an accessible content support feature, then they can turn the feature back on. (Level A)
<Jan> Resolution: Accept (15) In A.3.5.1 change the "bi-directional" handle to "Two-way." (addresses: WCAGWG24)
<Jan> Resolution: Accept (16) Rewording without change in normative meaning (addresses: MS43) A.3.6.1 Save Settings: Any authoring tool display settings and control settings can be saved between authoring sessions.
<Jan> Resolution: Accept (17)Typo: Should be B.1.3.2 Accessible Auto-Generated Content (WCAG Level AA)
<Jan> (18) Rewording without change in normative meaning (addresses: WCAGWG28) A.3.2.4 Content Edits Saved (Extended): The authoring tool can be set to automatically save all content edits made by authors.
<Jan> Resolution: Accept: (18) Rewording without change in normative meaning (addresses: WCAGWG28) A.3.2.4 Content Edits Saved (Extended): The authoring tool can be set to automatically save all content edits made by authors.
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: gpisocky Inferring ScribeNick: gpisocky Default Present: Jan, Jeanne, Greg_Pisocky, +1.561.582.aaaa, Sueann, Tim_Boland Present: Jan Jeanne Greg_Pisocky +1.561.582.aaaa Sueann Tim_Boland Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2010JulSep/0070.html Got date from IRC log name: 13 Sep 2010 Guessing minutes URL: http://www.w3.org/2010/09/13-au-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]