18:55:37 RRSAgent has joined #au 18:55:37 logging to http://www.w3.org/2013/04/08-au-irc 18:55:42 Zakim, this will be AUWG 18:55:42 ok, Jan; I see WAI_AUWG()3:00PM scheduled to start in 5 minutes 18:55:48 Meeting: WAI AU 18:56:04 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2013AprJun/0000.html 18:56:18 Chair: Jutta Treviranus 18:57:01 Regrets: Alex L., Sueanne L. 18:58:19 Greg__Adobe_ has joined #au 18:59:40 WAI_AUWG()3:00PM has now started 18:59:47 +Greg 19:01:41 +[IPcaller] 19:02:06 zakim, [IPcaller] is really Jan 19:02:06 +Jan; got it 19:02:35 jeanne has joined #au 19:03:18 +Jeanne 19:03:27 AlastairC has joined #au 19:05:05 +[Microsoft] 19:05:40 zakim, [Microsoft] is really Cherie 19:05:40 +Cherie; got it 19:05:59 +[IPcaller] 19:06:30 zakim, [IPcaller] is really Alastair 19:06:30 +Alastair; got it 19:09:53 http://groups.drupal.org/node/164389 19:14:08 Chair: Jan Richards 19:14:15 Another useful drupal resource if checking drupal: http://groups.drupal.org/node/85199 19:14:21 scribe: jeanne 19:14:40 Topic: 1. Re-chartering update (Jeanne) 19:14:55 JS: I have submitted the charter request 19:15:11 JS: Met with Judy last week and she had a few things she wanted explained 19:15:31 JS: New draft will circulate to the group next week 19:15:42 JS: June 30 is the deadline 19:16:46 JS: If rechartering is delayed, we can't publish 19:17:44 Topic: Where are we on CR? 19:17:49 JS: We are getting close 19:18:15 JS: We still need to write Status (JS), Announcements (JS), test doc for publishing (JS)... 19:18:35 JS: Need to get CR Exit Criteria written and approved. 19:19:10 JS: We have been working on it...Judy has it... 19:19:20 JS: I will meet Judy tomorrow about it 19:19:34 JS: I've never actually done one 19:19:53 JS: Then hopefully a call with Jan, Jutta, Judy this week 19:20:05 JS: If we can get agreement we will bring to the group... 19:20:12 JS: Then we publish and are into CR 19:20:33 JS; Then we need to write up all the instructions for outside testers 19:20:45 +Tim_Boland 19:20:47 JS: I have outlines of pages 19:21:22 JS: We really want to have them ready when the CR announcements go out 19:22:12 Topic: 2. Implementation report (Jan) 19:22:28 DRAFT Implementation report: 19:22:30 http://lists.w3.org/Archives/Public/w3c-wai-au/2013JanMar/att-0062/ATAG2-20120410PublicWD-ImplementationReport-rev20130321.html 19:22:39 JR: We sent the draft implementation report a couple weeks ago. People were asked to send in edits. 19:22:44 ... none received yet. 19:23:00 ... Greg let me know that he is ready to start working on it. 19:24:34 ... the other column codes. @none = no known implementations, @Several, @Many 19:25:05 ... The Other column also lists products that we think would cover this SC. 19:31:38 JS: We should also look at the At Risk items and strategize how we are going to deal with them. 19:32:57 JR: the way that we are writing the exit criteria, is that we are not going to try to find implemenations for WCAG AAA items. 19:32:59 3. Each success criterion that depends for its level on WCAG 2.0 will be positively implemented by at least two implementations at Level AA. 19:33:01 ◦ Implementations up to WCAG Level AAA will be recorded, but are not required. This level has value as it may be met by tools developed to serve specialized markets; however, WCAG 2.0 recommends against requiring WCAG 2.0 Level AAA as a general policy for entire sites, so it is unlikely that most tool developers will attempt to implement to this level. 19:35:17 JR: We still have to find implemenatations for our own AAA success criteria, but we are proposing to not have to find implementations for the success criteria dependent on WCAG AAA. 19:37:21 A.1.2.1 and A.1.2.2 need to follow accessibility guidelines - we need more. We have 1 each 19:38:21 A.3.6.3 Apply platform settings - apply platform settings. 19:38:47 +[IPcaller] 19:41:52 B.1.1.1 COntent auto-generation after authoring sessions 19:42:53 AC: I don't think DeFacto does this. 19:43:20 JS: I think this would be an example of a CMS or LMS where the author's text is included in a template. 19:44:10 JR: Also Facebook, where the author content may be redesigned in a new template and presented with different code surrounding the author content. 19:44:44 AC: CMS would collect small or large pieces from the author and manipulates it later. 19:45:50 action: Jeanne will look at Moodle to see if it meets B.1.1.1 19:45:50 Created ACTION-387 - Will look at Moodle to see if it meets B.1.1.1 [on Jeanne F Spellman - due 2013-04-15]. 19:48:54 B.1.2.2 Copy-Paste - this should not be hard to find, but we need concrete examples. 19:49:38 AC: I would think Markdown Editors should do this. Wiki style markup. 19:50:18 JR: Do they have a way to optimize that code, like remove white spaces? 19:50:58 ... another example would be a video tool that optimaizes the video quality, and make sure that it saves the video track. 19:51:57 ... in Powerpoint, it does an optimization cropping all the images. DOes that keep the alterntaive information when it is optimized. 19:52:03 zakim, who is making noise? 19:52:16 jeanne, listening for 10 seconds I heard sound from the following: Alastair (70%), Greg (19%), Jan (85%) 19:52:52 AC: Acrobat has an optimization tool that optimizes a PDF. 19:53:27 ... Youtube optimizes automatically. We would have to check if it deletes the option track. 19:54:45 B.2.2.1 Accessible Option Prominance - does the tool allow a choice between accessible or inaccessible, and is the accessible option equally prominant, measured by number of clicks. 19:55:05 JS: Would templates count here? 19:55:31 JR: Not every tool will allow inaccessible content to be created. It makes it harder to find an example. 19:56:34 B.2.2.2 Setting Accessibility Properties 19:56:50 AC: Maybe, I think we align horizonatally based on class 19:57:15 JR: Other tools have have a great deal of flexibility will likely hit this. 19:57:37 B.2.3.2 Repair of text alternatives during authoring 19:57:56 JR: This is only relevent to tools the pre-fill alternative content. 19:59:19 action: jeanne to check on the possible new flag in HTML for content that is automatically generated. 19:59:19 Created ACTION-388 - Check on the possible new flag in HTML for content that is automatically generated. [on Jeanne F Spellman - due 2013-04-15]. 20:00:05 AC: DeFacto will remember alt text and suggest it the next time it is used. 20:00:29 JR: Does it do it for any other accessibility properties, like longdesc? 20:00:49 AC: I don't think we have implemented longdesc yet. 20:00:59 ... I think Wordpress does this. 20:01:34 -Tim_Boland 20:01:39 Next meeting: Accessible templates 20:01:45 rrsagent, make minutes 20:01:45 I have made the request to generate http://www.w3.org/2013/04/08-au-minutes.html jeanne 20:01:46 -Cherie 20:01:47 -Greg 20:01:48 -Alastair 20:01:56 -[IPcaller] 20:01:59 -Jan 20:02:00 -Jeanne 20:02:02 WAI_AUWG()3:00PM has ended 20:02:02 Attendees were Greg, Jan, Jeanne, Cherie, Alastair, Tim_Boland, [IPcaller] 20:02:03 zakim, bye 20:02:03 Zakim has left #au 20:02:09 rrsagent, make minutes 20:02:09 I have made the request to generate http://www.w3.org/2013/04/08-au-minutes.html jeanne 20:02:10 AlastairC has left #au 20:02:25 rrsagent, make logs public