IRC log of au on 2009-06-22

Timestamps are in UTC.

19:56:10 [RRSAgent]
RRSAgent has joined #au
19:56:11 [RRSAgent]
logging to http://www.w3.org/2009/06/22-au-irc
19:56:17 [Jan]
Zakim, this will be AUWG
19:56:17 [Zakim]
ok, Jan; I see WAI_AUWG()3:00PM scheduled to start 56 minutes ago
19:56:22 [Jan]
Meeting: WAI AU
19:57:09 [Jan]
Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0075.html
19:57:16 [Zakim]
WAI_AUWG()3:00PM has now started
19:57:22 [Jan]
Chair: Jan Richards
19:57:23 [Zakim]
+AnnM
19:57:34 [Jan]
Regrets: Jutta Treviranus
19:58:01 [AnnM]
sure thing.
19:58:37 [Andrew]
Andrew has joined #au
19:58:39 [Zakim]
+Jeanne
19:58:46 [jeanne]
jeanne has joined #au
20:00:10 [jeanne]
zakim, who's here?
20:00:10 [Zakim]
On the phone I see AnnM, Jeanne
20:00:11 [Zakim]
On IRC I see jeanne, Andrew, RRSAgent, Zakim, Jan, AnnM, trackbot
20:00:49 [Zakim]
+??P9
20:01:03 [Jan]
zakim, ??P9 is really Jan
20:01:03 [Zakim]
+Jan; got it
20:01:32 [Zakim]
+??P11
20:02:36 [Jan]
zakim, ??P11 is really AndrewR
20:02:36 [Zakim]
+AndrewR; got it
20:08:05 [Zakim]
+Greg_Pisocky
20:09:39 [Greg]
Greg has joined #au
20:09:44 [Zakim]
+ +1.949.542.aaaa
20:10:16 [Jan]
zakim, aaaa is really SueannN
20:10:16 [Zakim]
+SueannN; got it
20:11:16 [Jan]
http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/att-0077/20090622.html
20:11:48 [Zakim]
+Tim_Boland
20:12:01 [Jan]
http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/att-0077/20090622.html
20:13:12 [Jan]
Scribe: Jan
20:14:28 [Jan]
Topic: Top to bottom review
20:16:38 [Jan]
The Introduction includes both normative and informative sections, as noted. This section is informative.
20:17:01 [Jan]
Action TB: Will look into whether it is ok to mix informative and normative in Introduction section
20:17:02 [trackbot]
Sorry, couldn't find user - TB
20:18:48 [Jan]
All: Approve "addressed by"
20:19:29 [Jan]
All: Approve remove ", with the assumption that many authors will not be familiar with the specific needs of end users with disabilities"
20:20:19 [Jan]
All: Approve "Examples of authoring tools:" handle
20:21:00 [Jan]
All: Approve remove ""conventional" "
20:22:09 [Jan]
All: Approve remove "Any ATAG 2.0 guideline that require authors to modify web content in some way, always assumes that the person has author permission"
20:23:09 [Jan]
All: Approve add "Web-based and non-web-based: ATAG 2.0 applies equally to authoring tools of web content that are web-based, non-web-based or a combination (e.g., a non-web-based markup editor with a web-based help system, a web-based content management system with a non-web-based file uploader client)."
20:23:51 [Jan]
All" Approve "debugging tools for web content "
20:25:47 [Jan]
JR: Just give thought to: "Real-time publishing: ATAG 2.0 applies to authoring tools with workflows that involve real-time publishing of web content (e.g., some collaborative tools). For these authoring tools, conformance to Part B of ATAG 2.0 may involve some combination of real-time accessibility supports and additional accessibility supports available after the real-time authoring session...
20:25:49 [Jan]
...(e.g., the ability to add captions for audio that was initially published in real-time). For more information, see the Techniques - Appendix E: Real-time content production."
20:27:39 [Jan]
All: Approve "Text Editors: ATAG 2.0 is not intended to apply to simple text editors that can be used to edit source content, but that include no support for the production of any particular web content technology. In contrast, ATAG 2.0 can apply to more sophisticated source content editors that support the production of specific web content technologies (e.g., with syntax checking, markup...
20:27:41 [Jan]
...prediction, etc.). "
20:29:36 [Jan]
All: Remove: "sufficient techniques and advisory"
20:34:02 [Jan]
All: Approve: Add "As of publishing, WCAG 2.0 is the most recent W3C Recommendation for web content accessibility. ATAG 2.0, therefore, makes reference to WCAG 2.0 in order to set the success criteria for judging the accessibility of web-based authoring tool user interfaces (in Part A) and for judging the accessibility of web content produced by authoring tools"
20:35:13 [Zakim]
-Tim_Boland
20:36:55 [Jan]
All: Approve "Scope of Authoring Tool User Interface"
20:38:06 [Jan]
All: Approve "This includes views of the web content being edited, and features that are independent of the web content being edited, such as menus, button bars, status bars, user preferences, documentation, etc."
20:39:52 [Jan]
All: Approve "Reflected Content Accessibility Problems: The authoring tool is responsible for ensuring that the web content being edited is accessible to authors with disabilities (e.g., ensuring that an image label in the web content can be programmatically determined). However, where an authoring tool user interface accessibility problem is caused directly by a web content accessibility...
20:39:54 [Jan]
...problem in the web content being edited (e.g., if an image in the content lacks a label), then this would not be considered a deficiency in the accessibility of the authoring tool user interface."
20:40:42 [Jan]
All: approve: Previews: Preview features are exempt from having to meet the other requirements in Part A, if they meet Guideline A.3.7. Previews are treated differently than editing views because authors, including those with disabilities, will not be well-served if preview features diverge too much from the actual functionality of user agents.
20:41:27 [Jan]
All: Remove "along with their user agents"
20:42:27 [Jan]
All: Change to "Rationale: Some authors need access to the editing view presentation because this may be used to convey both status information added by the authoring tool (e.g., underlining misspelled words) and, within content renderings, information about the end user experience of the web content being edited."
20:44:22 [Jan]
All: Approve: "A.2.2.2 Access to Text Presentation (Minimum): If an editing view (e.g., WYSIWYG view) renders any of the following presentation properties for text, then the properties can be programmatically determined:"
20:44:59 [Jan]
All: Chnage to: Rationale: Some authors need to set their own display settings in a way that differs from the presentation that they want to define for the published web content.
20:46:11 [Jan]
All: Approve change to: A.2.3.1 Independence of Display: The author(s) have the global option to specify display settings for editing views that take precedence over web content renderings without affecting the web content to be published. (Level A)
20:47:11 [Jan]
All: Approve: Rationale: Some authors with limited mobility or visual disabilities are not able to use a mouse, and instead require full keyboard access.
20:49:47 [Jan]
All: Approve: A.3.1.4 Customize Keyboard Access: The author(s) can customize keyboard access to the authoring tool. (Level AAA)
20:51:17 [Jan]
All: Approve "The search can be" wording
20:53:34 [Zakim]
-Greg_Pisocky
20:53:36 [Zakim]
-AnnM
20:53:40 [Zakim]
-Jeanne
20:53:41 [Zakim]
-Jan
20:53:45 [Zakim]
-SueannN
20:53:53 [Zakim]
-AndrewR
20:53:54 [Zakim]
WAI_AUWG()3:00PM has ended
20:53:55 [Zakim]
Attendees were AnnM, Jeanne, Jan, AndrewR, Greg_Pisocky, +1.949.542.aaaa, SueannN, Tim_Boland
20:54:40 [jeanne]
rrsagent, make minutes
20:54:40 [RRSAgent]
I have made the request to generate http://www.w3.org/2009/06/22-au-minutes.html jeanne
20:58:42 [jeanne]
rrsagent, make logs public
20:58:49 [jeanne]
rrsagent, make minutes
20:58:49 [RRSAgent]
I have made the request to generate http://www.w3.org/2009/06/22-au-minutes.html jeanne
21:29:49 [jeanne]
rrsagent, bye
21:29:49 [RRSAgent]
I see 1 open action item saved in http://www.w3.org/2009/06/22-au-actions.rdf :
21:29:49 [RRSAgent]
ACTION: TB to Will look into whether it is ok to mix informative and normative in Introduction section [1]
21:29:49 [RRSAgent]
recorded in http://www.w3.org/2009/06/22-au-irc#T20-17-01