19:55:06 RRSAgent has joined #au 19:55:06 logging to http://www.w3.org/2011/03/14-au-irc 19:55:12 Zakim, this will be AUWG 19:55:12 ok, Jan; I see WAI_AUWG()3:00PM scheduled to start 55 minutes ago 19:55:18 Meeting: WAI AU 19:55:39 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0086.html 19:55:57 Chair: Jan Richards 19:56:06 Regrets: Andrew R., Greg P. 19:59:33 WAI_AUWG()3:00PM has now started 19:59:40 +Jeanne 20:01:44 zakim, who is here? 20:01:44 On the phone I see Jeanne 20:01:47 On IRC I see RRSAgent, Zakim, Jan, jeanne, trackbot 20:02:18 +[Microsoft] 20:02:35 zakim, code? 20:02:35 the conference code is 2894 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), Jan 20:02:42 +??P6 20:02:52 zakim, ??P6 is really Jan 20:02:52 +Jan; got it 20:03:31 +[Microsoft.a] 20:04:04 zakim, [Microsoft.a] is really Alex 20:04:04 +Alex; got it 20:06:22 zakim, who's on the phone? 20:06:22 On the phone I see Jeanne, [Microsoft], Jan, Alex 20:06:55 zakim, [Microsoft] is really Cherie 20:06:55 +Cherie; got it 20:13:27 +[IPcaller] 20:14:39 alastairc has joined #au 20:21:18 + +1.561.200.aaaa 20:21:38 Sueann has joined #au 20:21:50 zakim, aaaa is Sueann 20:21:50 +Sueann; got it 20:21:53 yes 20:22:04 zakim, IPcaller is Alastair 20:22:04 +Alastair; got it 20:22:18 +Tim_Boland 20:22:22 http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0083.html 20:22:33 zakim, who's on the phone? 20:22:33 On the phone I see Jeanne, Cherie, Jan, Alex, Alastair, Sueann, Tim_Boland 20:23:02 Topic: ATAG2 Action re: rewording on Examples and Intents for B.1.1.2 and B.1.2.1 20:23:13 http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0081.html 20:25:06 @Automatic accessibility checking: An authoring tool allows images, videos and other multimedia files to be dragged into documents. When this happens, markup is automatically generated that contains accessibility problems. However, the authoring tool includes an "as-you-type" accessibility checker that unobtrusively highlights the problems for author attention, meeting (c). 20:25:20 Resolutuin: All accept @Automatic accessibility checking: An authoring tool allows images, videos and other multimedia files to be dragged into documents. When this happens, markup is automatically generated that contains accessibility problems. However, the authoring tool includes an "as-you-type" accessibility checker that unobtrusively highlights the problems for author attention, meeting (c). 20:25:25 Resolution: All accept @Automatic accessibility checking: An authoring tool allows images, videos and other multimedia files to be dragged into documents. When this happens, markup is automatically generated that contains accessibility problems. However, the authoring tool includes an "as-you-type" accessibility checker that unobtrusively highlights the problems for author attention, meeting (c). 20:26:00 @Manual accessibility checking: An authoring tool allows images, videos and other multimedia files to be dragged into documents. When this happens, markup is automatically generated that contains accessibility problems. Since the authoring tool includes a manual checking wizard instead of an automatic checker, a message appears in a status area of the user interface stating that the author... 20:26:01 ...should use the wizard before publishing, meeting (d). 20:26:09 Resolution: All accept @Manual accessibility checking: An authoring tool allows images, videos and other multimedia files to be dragged into documents. When this happens, markup is automatically generated that contains accessibility problems. Since the authoring tool includes a manual checking wizard instead of an automatic checker, a message appears in a status area of the user interface... 20:26:11 ...stating that the author should use the wizard before publishing, meeting (d). 20:26:25 Topic: Intent of Success Criterion B.1.2.1: 20:28:47 http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0081.html 20:28:59 Remove " as may happen" 20:29:58 @The intent of this success criterion is to encourage authoring tools to preserve accessibility information during restructuring or recoding transformations and to ensure authors are made aware when the authoring tool is unable to preserve accessibility information. This may occur when the output format does not support the same accessibility features as the input format (i.e. the example of... 20:30:00 ...a vector graphic being saved as a raster image format) or when an authoring tool has not implemented the necessary data mapping 20:30:05 . There is no negative connotation intended here. In some cases, the number of source technology possibilities is simply too large to ensure complete mappings are in place for all of them. 20:30:07 The options available partially mirror the options for Success Criterion B.1.1.2, reflecting the similarities between automatic generation and restructuring/re-coding web content transformations: 20:30:08 Option (a) is the most straightforward. It requires the authoring tool to preserve accessibility information during transformations. 20:30:10 Option (b) is to warn the author directly that accessibility information may be lost, allowing them to decide whether or not to proceed. 20:30:11 Option (c) takes into account that prompting during the transformation process may be contrary to the workflow. Instead, the authoring tool can run a checker on the output. 20:30:13 Option (d) is similar to (c) but takes into account that ATAG 2.0 allows the option of manual checking. 20:30:14 See Also: ATAG 2.0 identifies other types of transformations in which the expectation for preserving accessibility information is higher. These are optimizing transformations (Success Criterion B.1.2.2) and transformations in which non-text content is preserved (Success Criterion B.1.2.3). 20:30:24 Resolution: All accept: the intent text which change noted. 20:31:00 -Sueann 20:32:06 Sueann has joined #au 20:33:05 +Sueann 20:33:33 @Warning when text is converted to graphics: A "Save As" feature includes the ability to convert textual formats into graphics. However, if this option is selected by authors, they are warned that the output will have web content accessibility problems. They are also advised that style sheets are preferable for presentation control. If authors continue, there is a suggestion to retain the... 20:33:35 ...original text as alternative content for the graphical output. 20:33:38 @Option to cancel: A markup editor has a feature that that automatically removes any attributes or elements that do not appear in the defined DTD when content is opened for editing. Upon activation, the feature notifies authors that content will be deleted with unknown effects for end users. The author has the option to cancel the operation, in which case the content will not be opened for... 20:33:40 ...editing, meeting (b). 20:33:43 @Automatic accessibility checking: An authoring tool allows content to be copy-and-pasted from other applications, including office applications, user agent, etc. When this happens, the source content is recoded into the technology of the current document. While accessibility was considered in the design of the feature, web content accessibility problems may still occur. However, the... 20:33:45 ...authoring tool includes an "as-you-type" accessibility checker, meeting (c). 20:33:48 @Manual accessibility checking: An authoring tool allows content to be copy-and-pasted from other applications, including office applications, user agent, etc. When this happens, the source content is recoded into the technology of the current document. While accessibility was considered in the design of the feature, web content accessibility problems may still occur. Since the authoring... 20:33:52 ...tool includes a manual checking wizard instead of an automatic checker, a message appears in a status area of the user interface stating that the author should use the wizard before publishing, meeting (d). 20:34:07 Resolution: All accept these 4 examples for B.1.2.1 20:34:41 2. Link to W3C-WAI policies page from Implementing ATAG2 Related Resources for SC A.1.2.1 20:34:49 http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0068.html 20:37:01 AL: We can also be specific to Section 1194.21 20:38:01 Action The following is a non-exhaustive list of accessibility guidelines for various platforms (for additional information related to keyboard shortcuts, see Success Criterion A.3.1.3): 20:38:01 Sorry, couldn't find user - The 20:38:03 * Android: Example from Android Developer Reference 20:38:05 * BlackBerry: BlackBerry Accessibility 20:38:06 * Eclipse: Designing Accessible Plug-ins in Eclipse 20:38:08 * Gnome: GNOME Accessibility Developers Guide 20:38:09 * KDE: Developer's Information 20:38:11 * Java SE: Java SE Desktop Accessibility 20:38:12 * Lotus Notes: Lotus Notes checklist 20:38:14 * Mac OS: Accessibility Overview 20:38:15 * Microsoft Windows: Accessibility Overview 20:38:17 * iPhone OS: Accessibility Programming Guide for iPhone OS 20:38:18 * General Guides: 20:38:20 o ISO 9241-171:2008 Ergonomics of human-system interaction - Part 171: Guidance on software accessibility 20:38:21 o Software Checklist (IBM) 20:38:23 o International Policies Relating to Web Accessibility 20:38:34 http://www.w3.org/WAI/AU/2011/ED-IMPLEMENTING-ATAG20-20110308/#sc_a121-r 20:43:35 -Jeanne 20:43:53 Action JR: Update proposal at http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0066.html 20:43:53 Created ACTION-326 - Update proposal at http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0066.html [on Jan Richards - due 2011-03-21]. 20:44:29 http://www.w3.org/WAI/AU/2011/atag20-8Jul10LC-comments-updated10mar2011.html 20:44:47 +Jeanne 20:52:37 -Cherie 20:52:39 -Alex 20:52:40 -Alastair 20:52:42 -Sueann 20:52:47 -Jan 20:52:50 -Jeanne 20:59:30 RRSAgent, make minutes 20:59:30 I have made the request to generate http://www.w3.org/2011/03/14-au-minutes.html Jan 20:59:36 RRSAgent, set logs public 20:59:41 Zakim, bye 20:59:41 leaving. As of this point the attendees were Jeanne, Jan, Alex, Cherie, +1.561.200.aaaa, Sueann, Alastair, Tim_Boland 20:59:41 Zakim has left #au 20:59:43 AleMiele has joined #au 20:59:45 RRSAgent, bye 20:59:45 I see 1 open action item saved in http://www.w3.org/2011/03/14-au-actions.rdf : 20:59:45 ACTION: JR to Update proposal at http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0066.html [1] 20:59:45 recorded in http://www.w3.org/2011/03/14-au-irc#T20-43-53