IRC log of au on 2011-03-14

Timestamps are in UTC.

19:55:06 [RRSAgent]
RRSAgent has joined #au
19:55:06 [RRSAgent]
logging to http://www.w3.org/2011/03/14-au-irc
19:55:12 [Jan]
Zakim, this will be AUWG
19:55:12 [Zakim]
ok, Jan; I see WAI_AUWG()3:00PM scheduled to start 55 minutes ago
19:55:18 [Jan]
Meeting: WAI AU
19:55:39 [Jan]
Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0086.html
19:55:57 [Jan]
Chair: Jan Richards
19:56:06 [Jan]
Regrets: Andrew R., Greg P.
19:59:33 [Zakim]
WAI_AUWG()3:00PM has now started
19:59:40 [Zakim]
+Jeanne
20:01:44 [jeanne]
zakim, who is here?
20:01:44 [Zakim]
On the phone I see Jeanne
20:01:47 [Zakim]
On IRC I see RRSAgent, Zakim, Jan, jeanne, trackbot
20:02:18 [Zakim]
+[Microsoft]
20:02:35 [Jan]
zakim, code?
20:02:35 [Zakim]
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 [Zakim]
+??P6
20:02:52 [Jan]
zakim, ??P6 is really Jan
20:02:52 [Zakim]
+Jan; got it
20:03:31 [Zakim]
+[Microsoft.a]
20:04:04 [Jan]
zakim, [Microsoft.a] is really Alex
20:04:04 [Zakim]
+Alex; got it
20:06:22 [Jan]
zakim, who's on the phone?
20:06:22 [Zakim]
On the phone I see Jeanne, [Microsoft], Jan, Alex
20:06:55 [Jan]
zakim, [Microsoft] is really Cherie
20:06:55 [Zakim]
+Cherie; got it
20:13:27 [Zakim]
+[IPcaller]
20:14:39 [alastairc]
alastairc has joined #au
20:21:18 [Zakim]
+ +1.561.200.aaaa
20:21:38 [Sueann]
Sueann has joined #au
20:21:50 [jeanne]
zakim, aaaa is Sueann
20:21:50 [Zakim]
+Sueann; got it
20:21:53 [Sueann]
yes
20:22:04 [jeanne]
zakim, IPcaller is Alastair
20:22:04 [Zakim]
+Alastair; got it
20:22:18 [Zakim]
+Tim_Boland
20:22:22 [Jan]
http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0083.html
20:22:33 [Jan]
zakim, who's on the phone?
20:22:33 [Zakim]
On the phone I see Jeanne, Cherie, Jan, Alex, Alastair, Sueann, Tim_Boland
20:23:02 [Jan]
Topic: ATAG2 Action re: rewording on Examples and Intents for B.1.1.2 and B.1.2.1
20:23:13 [Jan]
http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0081.html
20:25:06 [Jan]
@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 [Jan]
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 [Jan]
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 [Jan]
@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 [Jan]
...should use the wizard before publishing, meeting (d).
20:26:09 [Jan]
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 [Jan]
...stating that the author should use the wizard before publishing, meeting (d).
20:26:25 [Jan]
Topic: Intent of Success Criterion B.1.2.1:
20:28:47 [Jan]
http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0081.html
20:28:59 [Jan]
Remove " as may happen"
20:29:58 [Jan]
@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 [Jan]
...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 [Jan]
. 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 [Jan]
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 [Jan]
Option (a) is the most straightforward. It requires the authoring tool to preserve accessibility information during transformations.
20:30:10 [Jan]
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 [Jan]
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 [Jan]
Option (d) is similar to (c) but takes into account that ATAG 2.0 allows the option of manual checking.
20:30:14 [Jan]
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 [Jan]
Resolution: All accept: the intent text which change noted.
20:31:00 [Zakim]
-Sueann
20:32:06 [Sueann]
Sueann has joined #au
20:33:05 [Zakim]
+Sueann
20:33:33 [Jan]
@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 [Jan]
...original text as alternative content for the graphical output.
20:33:38 [Jan]
@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 [Jan]
...editing, meeting (b).
20:33:43 [Jan]
@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 [Jan]
...authoring tool includes an "as-you-type" accessibility checker, meeting (c).
20:33:48 [Jan]
@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 [Jan]
...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 [Jan]
Resolution: All accept these 4 examples for B.1.2.1
20:34:41 [Jan]
2. Link to W3C-WAI policies page from Implementing ATAG2 Related Resources for SC A.1.2.1
20:34:49 [Jan]
http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0068.html
20:37:01 [Jan]
AL: We can also be specific to Section 1194.21
20:38:01 [Jan]
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 [trackbot]
Sorry, couldn't find user - The
20:38:03 [Jan]
* Android: Example from Android Developer Reference
20:38:05 [Jan]
* BlackBerry: BlackBerry Accessibility
20:38:06 [Jan]
* Eclipse: Designing Accessible Plug-ins in Eclipse
20:38:08 [Jan]
* Gnome: GNOME Accessibility Developers Guide
20:38:09 [Jan]
* KDE: Developer's Information
20:38:11 [Jan]
* Java SE: Java SE Desktop Accessibility
20:38:12 [Jan]
* Lotus Notes: Lotus Notes checklist
20:38:14 [Jan]
* Mac OS: Accessibility Overview
20:38:15 [Jan]
* Microsoft Windows: Accessibility Overview
20:38:17 [Jan]
* iPhone OS: Accessibility Programming Guide for iPhone OS
20:38:18 [Jan]
* General Guides:
20:38:20 [Jan]
o ISO 9241-171:2008 Ergonomics of human-system interaction - Part 171: Guidance on software accessibility
20:38:21 [Jan]
o Software Checklist (IBM)
20:38:23 [Jan]
o International Policies Relating to Web Accessibility
20:38:34 [alastairc]
http://www.w3.org/WAI/AU/2011/ED-IMPLEMENTING-ATAG20-20110308/#sc_a121-r
20:43:35 [Zakim]
-Jeanne
20:43:53 [Jan]
Action JR: Update proposal at http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0066.html
20:43:53 [trackbot]
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 [Jan]
http://www.w3.org/WAI/AU/2011/atag20-8Jul10LC-comments-updated10mar2011.html
20:44:47 [Zakim]
+Jeanne
20:52:37 [Zakim]
-Cherie
20:52:39 [Zakim]
-Alex
20:52:40 [Zakim]
-Alastair
20:52:42 [Zakim]
-Sueann
20:52:47 [Zakim]
-Jan
20:52:50 [Zakim]
-Jeanne
20:59:30 [Jan]
RRSAgent, make minutes
20:59:30 [RRSAgent]
I have made the request to generate http://www.w3.org/2011/03/14-au-minutes.html Jan
20:59:36 [Jan]
RRSAgent, set logs public
20:59:41 [Jan]
Zakim, bye
20:59:41 [Zakim]
leaving. As of this point the attendees were Jeanne, Jan, Alex, Cherie, +1.561.200.aaaa, Sueann, Alastair, Tim_Boland
20:59:41 [Zakim]
Zakim has left #au
20:59:43 [AleMiele]
AleMiele has joined #au
20:59:45 [Jan]
RRSAgent, bye
20:59:45 [RRSAgent]
I see 1 open action item saved in http://www.w3.org/2011/03/14-au-actions.rdf :
20:59:45 [RRSAgent]
ACTION: JR to Update proposal at http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0066.html [1]
20:59:45 [RRSAgent]
recorded in http://www.w3.org/2011/03/14-au-irc#T20-43-53