12:28:14 <RRSAgent> RRSAgent has joined #er
12:28:15 <RRSAgent> logging to http://www.w3.org/2013/10/02-er-irc
12:28:16 <trackbot> RRSAgent, make logs public
12:28:16 <Zakim> Zakim has joined #er
12:28:18 <trackbot> Zakim, this will be 3794
12:28:18 <Zakim> ok, trackbot; I see WAI_ERTWG()8:30AM scheduled to start in 2 minutes
12:28:19 <trackbot> Meeting: Evaluation and Repair Tools Working Group Teleconference
12:28:19 <trackbot> Date: 02 October 2013
12:31:31 <Zakim> WAI_ERTWG()8:30AM has now started
12:31:33 <Zakim> +Shadi
12:31:40 <carlos> carlos has joined #er
12:32:02 <samuelm> samuelm has joined #er
12:33:47 <Zakim> +??P1
12:33:49 <Zakim> -??P1
12:33:49 <Zakim> +??P1
12:34:56 <Zakim> +??P2
12:35:12 <samuelm> Zakim, ??P2 is me
12:35:12 <Zakim> +samuelm; got it
12:35:55 <shadi> zakim, ??p1 is carlos
12:35:55 <Zakim> +carlos; got it
12:36:14 <shadi> http://www.w3.org/WAI/ER/WD-AERT/ED-AERT
12:36:54 <shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2013Sep/0008.html
12:37:53 <shadi> [[- Organization: the table in section 3 seems mostly clear to me. I would
12:37:53 <shadi> go beyond and suggest reordering the features in section 2, and grouping
12:37:53 <shadi> them into different subsections, according to the same categories used in
12:37:53 <shadi> the table.
12:37:53 <shadi> ]]
12:39:59 <shadi> CV: just wanted to check the categories before implementing it in section 2
12:40:27 <shadi> [[- Tool audience category: I would explicitly include tool accessibility as
12:40:27 <shadi> a nother (desirable) feature. I am sure most agree on the relevance of the
12:40:27 <shadi> accessibility of evaluation tools, which should abide by general authoring
12:40:27 <shadi> tools accessibility criteria (better described in section A of ATAG 2.0
12:40:28 <shadi> <http://www.w3.org/WAI/ER/WD-AERT/ED-AERT20130906> ). But there is a more
12:40:28 <shadi> specific rationale for this point: in many companies, people with
12:40:30 <shadi> disabilities work as accessibility-specialyzed consultants, and they need
12:40:32 <shadi> authoring and evaluation tools that fit their ability profile.]]
12:42:48 <shadi> SAZ: so first point is if we agree that accessibility of the tool is a feature
12:43:10 <shadi> ...second is where to put it
12:43:19 <shadi> ...do we agree with this feature?
12:43:23 <shadi> CV: yes
12:43:32 <shadi> ...put it under "tool audience"?
12:43:49 <shadi> SAZ: that's where it most fits
12:44:05 <shadi> [[- Web testing APIs, I'm not sure if they only apply to "Test
12:44:05 <shadi> customization", or to "Subject being tested" as well. Tools that offer
12:44:05 <shadi> this kind of APIs (e.g. Selenium) are also used to bring the web
12:44:05 <shadi> application under testing to a predetermined state (to access a specific
12:44:05 <shadi> "Point of Observation"). For instance, APIs can also be used to start a
12:44:08 <shadi> session on a web site, add some products to a shopping cart, and then go
12:44:10 <shadi> to the "cart summary" page, which will be a subject under test that could
12:44:12 <shadi> have not been otherwise generated (as it does not correspond merely to
12:44:14 <shadi> e.g. a predefined URI).]]
12:53:03 <shadi> [[- Repair: I agree that automatic repair should be discouraged (basically,
12:53:03 <shadi> if user agents cannot provide an accessible representation or control,
12:53:03 <shadi> there is no reason that makes us think other software such as an
12:53:03 <shadi> accessibility evaluation tool is going to be smart enough to "mend" that).
12:53:03 <shadi> However, that should not preclude accessibility evaluation tools from
12:53:04 <shadi> automatically suggesting potential fixes. These fixes can even depend on
12:53:08 <shadi> the input of the evaluator, yet they are provided with some guidance
12:53:10 <shadi> nonetheless. Think, e.g. about the "quick fix" functionalities usually
12:53:12 <shadi> integrated in IDEs, which guide developers on how to fix a code problem,
12:53:14 <shadi> while still leaving the final choice in the hands of the developer.]]
13:28:46 <Zakim> -Shadi
13:28:48 <Zakim> -carlos
13:28:48 <Zakim> -samuelm
13:28:49 <Zakim> WAI_ERTWG()8:30AM has ended
13:28:49 <Zakim> Attendees were Shadi, samuelm, carlos
13:30:05 <shadi> trackbot, end meeting
13:30:05 <trackbot> Zakim, list attendees
13:30:05 <Zakim> sorry, trackbot, I don't know what conference this is
13:30:13 <trackbot> RRSAgent, please draft minutes
13:30:13 <RRSAgent> I have made the request to generate http://www.w3.org/2013/10/02-er-minutes.html trackbot
13:30:14 <trackbot> RRSAgent, bye
13:30:14 <RRSAgent> I see no action items