16:49:55 RRSAgent has joined #au 16:49:55 logging to http://www.w3.org/2013/06/17-au-irc 16:50:02 Zakim, this will be AUWG 16:50:02 ok, Jan; I see WAI_AUWG()1:00PM scheduled to start in 10 minutes 16:50:20 Meeting: WAI AU 16:50:46 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2013AprJun/0081.html 16:50:57 Chair: Jan Richards 16:51:10 Regrets: Jutta T., Tim B. 16:52:56 jeanne has joined #au 16:57:04 Tom-Babinszki has joined #au 16:58:29 WAI_AUWG()1:00PM has now started 16:58:36 + +1.847.917.aaaa 16:58:48 +Jeanne 16:59:14 zakim, aaaa is Tom 16:59:14 +Tom; got it 16:59:48 http://www.w3.org/WAI/AU/2013/ATAG2ImplementationReport.html 17:00:19 AlastairC has joined #au 17:00:25 +[IPcaller] 17:00:50 zakim, [IPcaller] is really Jan 17:00:50 +Jan; got it 17:02:45 + +1.571.765.aabb 17:03:05 zakim, aabb is really Greg 17:03:05 +Greg; got it 17:03:24 +[IPcaller] 17:03:31 +[Microsoft] 17:03:37 zakim, [IPcaller] is really Alastair 17:03:37 +Alastair; got it 17:03:49 zakim, [Microsoft] is really Alex 17:03:49 +Alex; got it 17:03:57 zakim, who's here? 17:03:57 On the phone I see Tom, Jeanne, Jan, Greg, Alastair, Alex 17:03:58 On IRC I see AlastairC, Tom-Babinszki, jeanne, RRSAgent, Zakim, Jan, trackbot 17:05:24 Scribe: AlastairC 17:06:11 +[Microsoft] 17:06:47 zakim, [Microsoft] is really Cherie 17:06:47 +Cherie; got it 17:07:04 Topic: 1. Re-chartering update (Jeanne) 17:07:31 JS: No news due to AC meeting 17:07:32 Jeanne: No new news, but many people were in Tokyo last week, so that's expected. 17:07:54 Topic: 2. Current SURVEY: 17:08:02 https://www.w3.org/2002/09/wbs/35520/20130610/results 17:08:36 https://www.w3.org/2002/09/wbs/35520/20130610/results#xq10 17:09:53 https://www.w3.org/2002/09/wbs/35520/20130523/results#xq10 17:10:14 B.4.1.2 Option to Reactivate Features: The authoring tool does not include the option to permanently turn off its accessible content support features. (Level A 17:10:16 Or 17:10:17 B.4.1.2 Option to Reactivate Features: The authoring tool does not include the option to turn off its accessible content support features or features which have been turned off can be restored at all times. (Level A 17:12:13 Jan: Not thrilled about the 'restored', doesn't match terms elsewhere. 17:12:21 Jan's proposal from email of 13 June B.4.1.2 Option to Reactivate Features: The authoring tool does not include the option to turn off its accessible content support features or those features can be turned back on. (Level A) 17:15:47 Greg: I liked the term 'restored', but Jan's version is fine. 17:16:24 B.4.1.2 Option to Reactivate Features: The authoring tool does not include the option to turn off its accessible content support features or features which have been turned off can be restored at all times. 17:16:35 AL: Turn on/off makes sense 17:16:42 B.4.1.2 Option to Reactivate Features: The authoring tool does not include the option to turn off its accessible content support features or features which have been turned off can be turned back on. 17:17:07 Greg: That's acceptable to me. 17:17:33 AC: OK 17:17:41 TB: OK 17:18:03 Resolution: Change B.4.1.2 to "B.4.1.2 Option to Reactivate Features: The authoring tool does not include the option to turn off its accessible content support features or features which have been turned off can be turned back on. " 17:18:26 Topic: B.2.4.4 Proposal 17:18:31 https://www.w3.org/2002/09/wbs/35520/20130610/results#xq11 17:19:21 jeanne: Trying to save the original intent of B 2.2.4, originally for the authoring tool all the templates would be accessible. Found a lot of problems with the language. 17:19:57 jeanne: Current language discussed in meeting last week, unlikely an authoring tool that didn't provide accessible template would then provide a warning of that. 17:20:37 jeanne: "All templates meet the WCAG 2.0 success criteria at A and AA that can be applied to each template before the template receives authored content." 17:21:11 jeanne: Template should meet at level A and AA. Can't say that a template meets 17:21:16 WCAG 17:21:39 Jan: Have wording for this in section A 17:22:01 http://www.w3.org/WAI/AU/ATAG20/#def-Accessible-Template 17:23:39 AC: Difficult to find implementation, for us easier to fix the templates 17:24:36 AL: For tools with big eco system, difficult to setup such a system. 17:25:40 AC: In defacto...content author picks templates... 17:26:19 AC: When a website is setup.... defacto provides some accessible templates... 17:26:51 JR: So it sounds like defacto would be an implementation? 17:27:20 AC: Initial setup is by developers, checked at that stage, content authors only have access to accessible templates. 17:29:23 B.2.4.1 Accessible Template Options (WCAG): If the authoring tool provides templates, then there are accessible template (WCAG) options for a range of template uses. (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria) 17:29:34 B.2.4.2 Identify Template Accessibility (Minimum): If the authoring tool includes a template selection mechanism and provides any non-accessible template (WCAG) options, then the templates are provided such that the template selection mechanism can display distinctions between the accessible and non-accessible options. (Level AA) 17:29:46 B.2.4.3 Author-Created Templates: If the authoring tool includes a template selection mechanism and allows authors to create new non-accessible templates (WCAG), then authors can enable the template selection mechanism to display distinctions between accessible and non-accessible templates that they create. (Level AA) 17:34:49 AC: Defacto templates are generally tested to AA 17:36:44 AC: exmaple interface from defacto - choosing template http://alastairc.ac/images/examples/defacto-choose-template.png 17:37:35 Jan: Given that this is AAA (not mainstream tools?) is there an issue with including it? 17:39:16 Draft B.2.4.4 Accessible Template Options (Enhanced): If the authoring tool provides templates, then all of the templates are accessible templates at WCAG 2.0 Level AA. 17:40:00 jeanne: Not sure we can say that, in terms of WCAG AA? 17:40:35 all the templates meet the WCAG 2.0 level A and level AA success criteria 17:40:39 http://www.w3.org/WAI/AU/ATAG20/#def-Accessible-Web-Content 17:41:20 Draft B.2.4.4 Accessible Template Options (Enhanced): If the authoring tool provides templates, then all of the templates are accessible templates to WCAG 2.0 Level AA. 17:41:45 Jan: I think it's ok, due to definition of template. We don't use the word 'conform'. 17:41:51 Draft B.2.4.4 Accessible Template Options (Enhanced): If the authoring tool provides templates, then all of the templates are accessible templates to WCAG 2.0 Level AA. (Level AAA) 17:42:11 AC: ok 17:42:22 jeanne: yes, this would be removed if we can't find examples 17:42:30 JR: And this will go on the at risk list to be removed 17:42:41 AL: ok 17:43:24 Resolution: All agree to reword B.2.4.4 as follows B.2.4.4 Accessible Template Options (Enhanced): If the authoring tool provides templates, then all of the templates are accessible templates to WCAG 2.0 Level AA. (Level AAA) AND this SC will be placed on the at-risk list for REMOVAL (not rewording) if implementations cannot be found 17:43:52 Topic: 3. Implementation report (Jan) 17:45:23 http://lists.w3.org/Archives/Public/w3c-wai-au/2013AprJun/att-0082/ATAG2ImplementationReport20130614.html 17:46:38 AlastairC has joined #au 17:46:49 A.3.6.4 Multiple Sets: If the authoring tool includes display and/or control settings, then the authoring tool provides the option of saving and reloading multiple configurations of settings. 17:47:43 Jan: Had Dreamweaver as an implementation, but it's just partial. The display settings let you change default font size etc. Those are not something you have multiple sets for. 17:48:05 No other implementations, should we let this go? 17:49:53 AC: For browser-based tools ...best to rely on browser 17:49:58 -Alastair 17:50:20 +[IPcaller] 17:50:38 zakim, IPcaller is Alastair 17:50:38 +Alastair; got it 17:50:39 AC: Browser based ones we rely on the browser settings, should we apply the same to the system? 17:51:31 JS: I would prefer it in the platform 17:51:36 AC: i.e. things like Dreamweaver allow system-level user settings to work in the interface. 17:51:53 JR: I will go ahead and propose removing A.3.6.4 Multiple Sets 17:52:27 B.2.5.2 Pre-Authored Content Accessibility Status: If the authoring tool provides a repository of pre-authored content, then each of the content objects has a recorded accessibility status. (Level AAA) 17:52:35 Jan: similar issue to what we were talking about with the tempaltes. 17:53:07 B.2.5.1 Pre-Authored Content Selection Mechanism: If authors are provided with a selection mechanism for pre-authored content other than templates (e.g., clip art gallery, widget repository, design themes), then both of the following are true: (Level AA) 17:53:09 (a) Indicate: The selection mechanism indicates the accessibility status of the pre-authored content (if known); and 17:53:10 (b) Prominence: Any accessible (WCAG) options are at least as prominent as other pre-authored content options. 17:55:03 Jan: I couldn't find anything like this, e.g. clip art gallery with Word. You can search by text & captions. Oddly, when inserted they add URI rather than caption. But that's still not indicating the accessibility. 17:57:04 AC: we run under the assumption that included templates (pre-authored things) are accessible, rather than saving whether it is or not. 17:57:41 Jan: We could fix the gating on that, but doesn't help for finding implementation. Anyone know of any? 17:59:29 jeanne: What about video libraries? E.g. ones with captions. 18:00:55 Jan: Has to be from developer of authoring tool though 18:01:10 -Greg 18:01:36 -Tom 18:01:37 -Jan 18:01:38 -Jeanne 18:01:38 -Alastair 18:01:43 -Alex 18:01:46 -Cherie 18:01:48 WAI_AUWG()1:00PM has ended 18:01:48 Attendees were +1.847.917.aaaa, Jeanne, Tom, Jan, +1.571.765.aabb, Greg, Alastair, Alex, Cherie 18:01:48 Meeting as usual on June 24 18:02:14 RRSAgent, make minutes 18:02:14 I have made the request to generate http://www.w3.org/2013/06/17-au-minutes.html Jan 18:02:21 RRSAgent, set logs public 18:02:30 Zakim, bye 18:02:30 Zakim has left #au 18:02:36 RRSAgent, bye 18:02:36 I see no action items