13:54:41 RRSAgent has joined #wcag-act 13:54:42 logging to http://www.w3.org/2017/03/15-wcag-act-irc 13:54:43 RRSAgent, make logs public 13:54:43 Zakim has joined #wcag-act 13:54:45 Zakim, this will be 13:54:45 I don't understand 'this will be', trackbot 13:54:46 Meeting: Accessibility Conformance Testing Teleconference 13:54:47 Date: 15 March 2017 13:55:59 agenda? 13:56:15 agenda+ Develop list to advertise ACT Framework FPWD 13:56:24 agenda+ Early comments received from AG WG on the ACT Framework Survey https://www.w3.org/2002/09/wbs/93339/ACTFrameworkFPWD/results 13:56:33 agenda+ Test case repository discussion 13:56:42 agenda+ Rule repository discussion 14:03:10 maryjom_ has joined #wcag-act 14:03:24 present+ 14:03:58 Charu has joined #wcag-act 14:07:07 MoeKraft has joined #wcag-act 14:07:53 scribe: shadi 14:07:54 present+ 14:08:06 present+ MoeKraft 14:09:49 zakim, take up next 14:09:49 agendum 1. "Develop list to advertise ACT Framework FPWD" taken up [from Wilco] 14:10:02 present+ Charu 14:10:23 WF: preparing for FPWD, and want to announce broadly to get feedback 14:11:05 SAZ: WAI announcements sent to WAI IG 14:11:17 ...are there other lists like on QA? 14:13:25 ...maybe people are involved in QA beyond a11y? 14:13:37 ...not sure how active OpenAjax Alliance is? 14:14:43 WF: will set up a wiki page with the lists and who will forward announcement to these lists 14:16:17 MK: another automation group 14:16:29 https://www.w3.org/WAI/GL/task-forces/conformance-testing/wiki/List_of_related_groups 14:17:57 public-test-infra@w3.org 14:18:09 https://spec-ops.github.io/atta-api/ 14:21:23 zakim, take up next 14:21:23 agendum 2. "Early comments received from AG WG on the ACT Framework Survey https://www.w3.org/2002/09/wbs/93339/ACTFrameworkFPWD/results" taken up [from Wilco] 14:22:24 WF: comment on relying too much on CSS selectors 14:23:30 https://w3c.github.io/wcag-act/act-framework.html#test-proc-selector 14:23:31 SAZ: maybe people not finding test cases 14:28:07 CP: seems specific to CSS Selectors 14:28:48 WF: not explicitly saying we can use different syntax, although example shows that 14:29:05 ...maybe can make sentence explicit 14:29:50 SAZ: maybe also add a second example with a different type of selector? 14:30:39 WF: could do 14:33:08 WF: next comment on wording 14:33:20 "This framework is intended to provide a central point where accessibility experts can agree on how accessibility requirements should be tested so as to avoid conflicting results of accessibility tests. It is intended for both manual accessibility tests as well as for automated testing done through accessibility test tools (ATTs)." 14:33:59 CP: like approach 14:39:31 This framework is intended to provide a consistent interpretation of how to test for accessibility requirements so as to avoid conflicting results of accessibility tests. It is intended for both manual accessibility tests as well as for automated testing done through accessibility test tools (ATTs). 14:39:55 +1 14:40:06 +1 14:40:44 +1 14:40:58 WF: wonder if name is throwing people off? 14:41:16 ...are created expectations that we can't meet? 14:41:22 SAZ: loaded word 14:45:19 WF: can we make changes? 14:45:25 SAZ: better not during review 14:45:39 ...but make pull requests and get back to the commenters 14:45:49 MK: will add pull request 14:45:55 zakim, take up next 14:45:55 agendum 3. "Test case repository discussion" taken up [from Wilco] 14:46:44 WF: missing Alistair for this 14:46:49 zakim, close agendum 3 14:46:49 agendum 3, Test case repository discussion, closed 14:46:50 I see 1 item remaining on the agenda: 14:46:50 4. Rule repository discussion [from Wilco] 14:46:52 zakim, take up next 14:46:52 agendum 4. "Rule repository discussion" taken up [from Wilco] 14:47:54 https://auto-wcag.github.io/auto-wcag/ 14:48:42 CP: rule repository different from auto-WCAG plain english rules? 14:48:55 WF: no, about moving them to W3C space 14:52:40 SAZ: looks really great! 14:53:21 ...one question is how we validate such test rules to ensure they are inline with WCAG interpretation 14:53:34 ...other question is about test cases associated with thes rules 14:53:48 WF: just started to write test cases 14:54:02 CP: some have commented that this is an important part 14:56:43 SAZ: also heard focus should be on test cases not on the procedures 14:56:59 ...for example if someone has a different way to achieve the same results 14:59:31 WF: concerned about tools becoming black boxes again 14:59:57 SAZ: criteria should be test cases not test procedures 15:00:16 ...but I think we need to keep test procedures for other uses cases 15:00:29 ...like someone trying to build a tool from scratch 15:01:37 trackbot, end meeting 15:01:37 Zakim, list attendees 15:01:37 As of this point the attendees have been shadi, Wilco, MoeKraft, Charu 15:01:45 RRSAgent, please draft minutes 15:01:45 I have made the request to generate http://www.w3.org/2017/03/15-wcag-act-minutes.html trackbot 15:01:46 RRSAgent, bye 15:01:46 I see no action items