18:48:59 RRSAgent has joined #au 18:48:59 logging to http://www.w3.org/2012/09/17-au-irc 18:49:04 Zakim, this will be AUWG 18:49:04 ok, Jan; I see WAI_AUWG()3:00PM scheduled to start in 11 minutes 18:49:09 Meeting: WAI AU 18:49:31 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2012JulSep/0040.html 18:49:49 Chair: Jan Richards 18:49:55 Regrets: Jutta T. 19:00:03 WAI_AUWG()3:00PM has now started 19:00:09 +[IPcaller] 19:01:07 +[Microsoft] 19:01:20 jeanne has joined #au 19:01:39 zakim, IPcaller is really Jan 19:01:39 +Jan; got it 19:01:43 +Jeanne 19:01:50 +??P15 19:01:55 zakim, [Microsoft] is really Alex 19:01:55 +Alex; got it 19:02:10 zakim, ??P15 is really Jutta 19:02:10 +Jutta; got it 19:04:28 +[Microsoft] 19:05:01 zakim, [Microsoft] is really Cherie 19:05:01 +Cherie; got it 19:05:32 scribe: jeanne 19:05:36 scribe: Jeanne 19:05:40 + +1.571.765.aaaa 19:05:46 agenda? 19:05:53 zakim, aaaa is really Greg 19:05:53 +Greg; got it 19:06:00 http://lists.w3.org/Archives/Public/w3c-wai-au/2012JulSep/0040.html 19:06:13 Topic: 1. What to do with B.4.1.3 Feature Availability Information 19:07:15 JR: This came up while writing tests. 19:07:26 Greg has joined #au 19:07:30 B.4.1.3 Feature Availability Information: If the authoring tool supports production of any web content technologies for publishing for which the authoring tool does not provide support for the production of accessible web content (WCAG), then this is documented. (Level AA) Note: This success criterion concerns the presence or absence of support features, such as accessibility checkers, not... 19:07:32 ...any intrinsic property of web content technologies. 19:08:56 JR: Tools come in many formats, so you need to document in the tool that any formats that do not meet ATAG need to be documented. 19:09:09 ... this is difficult to do from a testing viewpoint 19:09:17 6. A list of the *web content technologies produced by the authoring tool that are included in the claim*. If there are any web content technologies produced by the authoring tool that are *not included* in the conformance claim, these must be listed separately. If the authoring tool produces any web content technologies by default, then these must be *included*. 19:09:32 ... and the documentation can be buried in a manual, so it would not be useful. 19:10:31 ... So if a tool produces a web content technology by default, then that must be included for ATAG conformance. 19:10:50 ... you cannot side-step the ATAG conformance. 19:11:20 GP: If the default content is NOT a web content technology, then it does not apply. 19:11:54 JR: Example: a word processing program does not produce a web content technology by default, but does have a save as HTML option 19:12:23 ... it can conform for the HTML, but does not have to file on the .doc document format 19:13:02 GP: it seems ok 19:14:38 GP: On the flip side, the default format can be accessible, even if it is not a web content technology. 19:16:49 AL: I know what a "default" is, but I can anticipate that some people might ask what the default is for that tool. Other tools may produce many different formats without a default. 19:17:55 6. A list of the *web content technologies produced by the authoring tool that are included in the claim*. If there are any web content technologies produced by the authoring tool that are *not included* in the conformance claim, these must be listed separately. If the authoring tool produces any web content technologies by default, then these must be *included*. 19:18:17 All: No objections heard... 19:18:18 JR: SO B.4.1.3 will be deleted and this will be added to B.4.1.1 19:18:38 Resolved: Add the new sentence to 6. A list of the *web content technologies produced by the authoring tool that are included in the claim*. If there are any web content technologies produced by the authoring tool that are *not included* in the conformance claim, these must be listed separately. If the authoring tool produces any web content technologies by default, then these must be... 19:18:40 ...*included*. 19:18:55 Resolved: To remove SC B.4.1.3 Feature Availability Information 19:19:09 Topic: 2. Other issues from the larger group? 19:21:17 GP: Can you recap where we are? 19:22:09 JR: We have finished Last Call and we could go into CR at any time, but we are settling our testing before we set up our exit criteria from CR. 19:23:02 GP: so how many test cases have to go through this before we are satisfied and W3C is satisfied. 19:23:21 JR: We set a test cases, a test approach and our exit criteria. 19:23:46 ... then we go and talk to those powers. 19:28:23 JS: An important part of the Exit Criteria is idenfying problem areas and what we will do about them. otherwise we have to go back to Last Call to change the document. 19:28:42 AL: then we need to be very flexible and accept tools that only do a few things 19:28:50 +Tim_Boland 19:30:10 JR: well, we need to write the exit criteria so that we are credible. 19:32:29 Tim has joined #au 19:33:55 JS: We can't just cherry pick implementations to find 2 implementations, we have to show that types of tools meet the criteria that apply to that tool . 19:34:43 -Jutta 19:34:49 JR: Those of you who are not writing test cases, please go through the document and look for the success criteria that are either hard to test, or may not have sufficient implementations. 19:35:34 We will discuss on Dept 24 19:35:48 JR: We will discuss this next week. Look for at-risk success criteria. 19:35:57 -Alex 19:36:00 -Cherie 19:36:01 End of the first part of the call 19:36:22 rrsagent, make minutes 19:36:22 I have made the request to generate http://www.w3.org/2012/09/17-au-minutes.html jeanne 19:36:29 Provide link to the test location? 19:37:01 This is the most recent: http://www.w3.org/WAI/AU/2012/ATAG20tests/ATAG2-10April2012PublicWD-Tests-rev20120730 19:37:34 There were some more tests submitted after that point... 19:38:42 e.g. from http://lists.w3.org/Archives/Public/w3c-wai-au/2012JulSep/0035.html 19:40:51 Guideline A.3.1: (For the authoring tool user interface) Provide keyboard access to authoring features - Tim Boland 19:42:21 Guideline A.4.2: (For the authoring tool user interface) Document the user interface including all accessibility features. - Jan Richards 19:43:15 GP: A.3.7.1 & 2 - Greg will take them 19:43:38 Guideline A.3.7: (For the authoring tool user interface) Ensure that previews are at least as accessible as in-market user agents. - Greg Pisocky 19:44:39 A.3.6 to Jeanne 19:44:45 Guideline A.3.6: (For the authoring tool user interface) Manage preference settings. - Jeanne Spellman 19:45:17 -Tim_Boland 19:45:19 -Jeanne 19:45:21 -Greg 19:45:24 -Jan 19:45:25 WAI_AUWG()3:00PM has ended 19:45:25 Attendees were Jan, Jeanne, Alex, Jutta, Cherie, +1.571.765.aaaa, Greg, Tim_Boland 20:05:18 RRSAgent, make minutes 20:05:18 I have made the request to generate http://www.w3.org/2012/09/17-au-minutes.html Jan 20:05:24 RRSAgent, set logs public 20:05:29 Zakim, bye 20:05:29 Zakim has left #au 20:05:35 RRSAgent, bye 20:05:35 I see no action items