12:27:49 <RRSAgent> RRSAgent has joined #er
12:27:49 <RRSAgent> logging to http://www.w3.org/2013/05/15-er-irc
12:27:51 <trackbot> RRSAgent, make logs public
12:27:51 <Zakim> Zakim has joined #er
12:27:53 <trackbot> Zakim, this will be 3794
12:27:53 <Zakim> ok, trackbot; I see WAI_ERTWG()8:30AM scheduled to start in 3 minutes
12:27:54 <trackbot> Meeting: Evaluation and Repair Tools Working Group Teleconference
12:27:54 <trackbot> Date: 15 May 2013
12:29:40 <Zakim> WAI_ERTWG()8:30AM has now started
12:29:46 <Zakim> +[IPcaller]
12:29:53 <shadi> zakim, ipcaller is me
12:29:53 <Zakim> +shadi; got it
12:30:11 <shadi> regrets: Christophe, Kostas
12:32:05 <Sinarmaya_> Sinarmaya_ has joined #er
12:33:20 <Zakim> +Yehya
12:33:51 <shadi> zakim, yahya is really PhilipA
12:33:51 <Zakim> sorry, shadi, I do not recognize a party named 'yahya'
12:33:57 <shadi> zakim, yehya is really PhilipA
12:33:57 <Zakim> +PhilipA; got it
12:34:03 <Zakim> +PhilipA.a
12:34:26 <carlos> carlos has joined #er
12:34:31 <shadi> zakim, PhilipA.a is carlos
12:34:31 <Zakim> +carlos; got it
12:37:57 <Zakim> + +1.662.341.aaaa
12:38:14 <shadi> zakim, aaaa is Sinarmaya_
12:38:14 <Zakim> +Sinarmaya_; got it
12:38:50 <shadi> http://www.w3.org/WAI/ER/WD-AERT/ED-requirements
12:42:20 <Sinarmaya_> Sinarmaya_ has joined #er
12:42:30 <shadi> Topic: Table of Contents
12:42:52 <shadi> SAZ: looks ok, good to have the additional info as appendecies
12:42:59 <shadi> ...may not be able to get to them
12:43:24 <shadi> Topic: Objectives of the document
12:44:50 <shadi> CV: no width restriction in TR format is an issue
12:44:50 <shadi> ...can this be changed?
12:44:56 <shadi> SAZ: not sure, need to double-check
12:45:07 <shadi> CV: ok, will leave for now
12:46:46 <shadi> SAZ: item #4 should be #3?
12:47:19 <shadi> Support developers of accessibility evaluation tools to understand the different types of techniques in WCAG 2.0 and types of web accessibility tests: automatic, semiautomatic and manual -> Support developers of accessibility evaluation tools to understand how to use failures and techniques in WCAG 2.0 to address the different types of web accessibility tests: automatic, semiautomatic and manual
12:49:45 <shadi> ER: the first one is more clear
12:49:50 <shadi> CV: mixing up the concepts - who does the tests etc
12:50:04 <shadi> ER: first wording has two parts
12:50:16 <shadi> ...second is one thing that depends on the other
12:55:32 <shadi> Support developers of accessibility evaluation tools to understand the different types of techniques in WCAG 2.0 and types of web accessibility tests: automatic, semiautomatic and manual -> Support developers of accessibility evaluation tools to understand the different types of web accessibility tests: automatic, semiautomatic and manual
12:56:46 <shadi> (and how these relate to WCAG 2.0 success criteria, techniques, and failures)
12:57:45 <shadi> (and how these relate to WCAG 2.0 success criteria, sufficient techniques, advisory techniques, and common failures)
12:58:50 <shadi> (and to use WCAG 2.0 success criteria, sufficient techniques, advisory techniques, and common failures for web accessibility testing)
12:59:26 <shadi> #3 Support developers of accessibility evaluation tools to understand the different types of web accessibility tests: automatic, semiautomatic and manual
13:00:07 <shadi> #4 Support developers of accessibility evaluation tools to understand how to use WCAG 2.0 success criteria, sufficient techniques, advisory techniques, and common failures for web accessibility testing)
13:01:08 <shadi> In addition, the document may provide additional information on ...
13:02:50 <shadi> SAZ: put list under "Typical features of an evaluation tool" as a sub-list to objective #1
13:03:50 <shadi> #1 Describe to web developers typical features of web accessibility evaluation tools. Examples of such features include:
13:04:50 <shadi> CV: too much information
13:04:51 <shadi> SAZ: make "typical features" a link?
13:05:21 <shadi> #1 Describe to web developers typical features of web accessibility evaluation tools. Examples of such features are listed in [section ...].
13:05:45 <shadi> ER: agree
13:06:17 <shadi> "and briefly describe possible implementation issues of these features. These issues may include additional information like licensing schemes, etc."?
13:06:30 <shadi> s/ER/EGyR/G
13:12:27 <shadi> SAZ: concerns about expectations
13:12:50 <shadi> CV: will try to tone down "implementation"
13:13:01 <shadi> SAZ: also concerned about "licensening discussion"
13:13:10 <shadi> CV: can remove it from here
13:13:59 <shadi> EgyR: licensing can be relevant to implementation but not sure the document can address all the different complex situations that can exist
13:16:45 <Sinarmaya_> Sinarmaya_ has joined #er
13:17:03 <shadi> Topic: Next Steps
13:17:31 <shadi> #1. inform the WAI Coordination Group (CG)
13:18:05 <shadi> #2. ask for EOWG feedback on requirements document
13:18:15 <shadi> #3. start working on main document
13:18:29 <shadi> #4. identify a good title for the document
13:18:50 <shadi> #5. announce the work and recruit new participants
13:21:20 <shadi> Topic: Next Meeting
13:21:29 <shadi> SAZ: no meeting next week
13:21:52 <shadi> ...meet again in 2 weeks
13:21:58 <Zakim> -Sinarmaya_
13:21:59 <shadi> trackbot, end meeting
13:21:59 <trackbot> Zakim, list attendees
13:21:59 <Zakim> As of this point the attendees have been shadi, PhilipA, carlos, +1.662.341.aaaa, Sinarmaya_
13:22:01 <Zakim> -PhilipA
13:22:02 <Zakim> -carlos
13:22:05 <Sinarmaya_> Sinarmaya_ has left #er
13:22:07 <trackbot> RRSAgent, please draft minutes
13:22:07 <RRSAgent> I have made the request to generate http://www.w3.org/2013/05/15-er-minutes.html trackbot
13:22:08 <trackbot> RRSAgent, bye
13:22:08 <RRSAgent> I see no action items