15:06:41 RRSAgent has joined #svg-a11y 15:06:41 logging to http://www.w3.org/2015/12/18-svg-a11y-irc 15:06:52 RRSAgent, start telcon 15:06:52 I'm logging. I don't understand 'start telcon', shepazu. Try /msg RRSAgent help 15:07:10 RRSAgent, start meeting 15:07:10 I'm logging. I don't understand 'start meeting', richardschwerdtfeger. Try /msg RRSAgent help 15:07:17 trackbot, start telcon 15:07:19 RRSAgent, make logs ab 15:07:21 Zakim, this will be 15:07:21 I don't understand 'this will be', trackbot 15:07:22 Meeting: SVG Accessibility Task Force Teleconference 15:07:22 Date: 18 December 2015 15:08:27 chair: fred 15:09:07 present+ fred 15:09:14 present+ AmeliaBR 15:11:19 scribe: Rich 15:11:27 Topic: House Keeping 15:11:37 ARIA test harness training at 1 pm 15:11:38 https://mit.webex.com/mit/j.php?MTID=m7db77677168c3b593472b7bd18a744e2 15:11:40 +1-617-324-0000 US Toll Number 15:11:41 Access code: 646 468 175 15:11:46 fred: there is an aria test harness training session at 1pm today 15:12:54 fred: In January Michael is going ot activate a tracker for the task force 15:13:30 fred: close out old defects in the the old tracker that are not valide. 15:14:10 s/valide/valid/ 15:15:23 Rich: I will set up doodle pole on new testing time 15:15:44 Doug: I will look into starting an automated test harness project 15:16:42 Topic: Fred’s updates on testing 15:17:05 https://www.w3.org/wiki/SVG_Accessibility/Testing 15:17:09 fred: I wrote a perl script to create the actual test files from the testable statements in the wiki 15:17:38 fred: the test skips over the to do in the testable statement and creates a test file with a svg wrapper. 15:17:46 fred: the orca browser does not complain 15:18:14 fred: it puts in meta data for what is being tested. It captures what the test file is. the name, etc. 15:18:30 fred: the point is the meta data can be used to set up the test 15:18:50 fred: charles and leonie have had to use inspect to do the testing 15:19:22 fred: I am building a seprate test that sucks in the json database files and through the use of radio buttons choose a suite of tests based on the svg or html wrapper 15:19:45 fred: the other radio buttons will say whether you are testing the role or name 15:19:51 fred: it runs 21-29 tests 15:20:21 fred: you click on the button and it shows a separate window to look in the accessibility tree. The element you are testing always has the id of test 15:20:32 fred: youl will alway be able to find the test manually 15:20:48 fred: in the diagram it will show what the test is that is being made 15:21:03 fred: I am going to put a button with pass or fail. 15:21:19 fred: you can screenscrape the results and pass them on to michael cooper to record the results. 15:21:43 fred: I should have a sample of a debugging test interface that you can put on your own personal web server. 15:22:06 fred: anyone have any questions? 15:22:13 rich: I think we need to see it. 15:22:36 rich: if magically web driver gets updated quick enough then we could use it 15:23:42 fred: the next steps in testing. We have 3, 4, or 5 things. 15:24:03 fred: we need to look and see if the tests on the wiki are sufficient and whether they are valid. 15:24:20 fred: then we need to look at the test driver is coming out Tuesday 15:24:32 amelia: do you have a place where the tests are available on line? 15:24:54 fred: I will will send everything out on Tuesday. 15:25:33 rich: you are going to need hundreds of tests. 15:26:08 fred: i did not all of svg 15:26:47 fred: the default role mappings are in there 15:27:41 rich: did you do all the name computation work? 15:27:51 fred: I think so but I need confirmation. 15:28:49 fred: i did label and aria-labelledy as well as all the attributes 15:29:10 fred: you can actually run the test, yeah 15:29:33 doug: should we have a telecon with the SVG working group 15:29:40 doug: we need to see where we overlap 15:29:50 doug: a lot of the older tests were manual 15:29:59 doug: some of the tests are automated 15:30:10 doug: SVG was hand done 15:30:32 doug: there are some autorun 15:30:37 scribe: Rich 15:30:47 rich: we need to coordinate testing 15:31:49 rich: how close are they to being done in SVG2? Do they have consensus? 15:32:11 doug: I think it will be more like Q2 15:32:30 RRSAgent, make log public 15:34:21 Doug: there is a face to face in Sydney in February 15:49:39 doug: We need a joint task force meeting with the main svg working group to get particular test going 15:50:17 doug: In addition to the types of tests that were already done I don’t knwo that we have a sort of a comprehensive list of things we need to test in SVG 15:50:50 doug: All the things that we need to test in svg (high level) 15:51:22 fred: I will make a different page 15:51:57 doug: I will make the current page test assertions. The testing page will be a high level testing page. 15:54:40 rich: we need to test error conditions like an element with role=“none” and tabindex=“0” 15:55:18 fred: that should not be an issue 15:56:54 https://www.w3.org/wiki/SVG_Accessibility/Testing https://www.w3.org/wiki/SVG_Accessibility/Testing/Test_Assertions 15:57:05 https://www.w3.org/wiki/SVG_Accessibility/Testing and https://www.w3.org/wiki/SVG_Accessibility/Testing/Test_Assertions 15:58:49 fred: track and view don’t have a test 16:00:51 if given then for id="test" NOAC 16:00:52 fred: animate transform is an example of something that is not mapped 16:01:18 fred: we need an example of every filter element to make sure it is not mapped. 16:02:19 doug: I can walk through the filters easily 16:02:33 fred: for evey todo here we need to populate it 16:03:28 Doug: the next meeting is January 8 16:03:36 RRSAgent, make minutes 16:03:36 I have made the request to generate http://www.w3.org/2015/12/18-svg-a11y-minutes.html richardschwerdtfeger 16:03:45 chair: Fred 16:03:53 RRSAgent, make minutes 16:03:53 I have made the request to generate http://www.w3.org/2015/12/18-svg-a11y-minutes.html richardschwerdtfeger