W3C

- DRAFT -

SVG Accessibility Task Force Teleconference
18 Dec 2015

See also: IRC log

Attendees

Present
fred, AmeliaBR
Regrets
Chair
fred
Scribe
Rich

Contents


<shepazu> trackbot, start telcon

<scribe> scribe: Rich

House Keeping

<fesch> ARIA test harness training at 1 pm

<fesch> https://mit.webex.com/mit/j.php?MTID=m7db77677168c3b593472b7bd18a744e2

<fesch> +1-617-324-0000 US Toll Number

<fesch> Access code: 646 468 175

fred: there is an aria test harness training session at 1pm today
... In January Michael is going ot activate a tracker for the task force
... close out old defects in the the old tracker that are not valid.

Rich: I will set up doodle pole on new testing time

Doug: I will look into starting an automated test harness project

Fred’s updates on testing

<fesch> https://www.w3.org/wiki/SVG_Accessibility/Testing

fred: I wrote a perl script to create the actual test files from the testable statements in the wiki
... the test skips over the to do in the testable statement and creates a test file with a svg wrapper.
... the orca browser does not complain
... it puts in meta data for what is being tested. It captures what the test file is. the name, etc.
... the point is the meta data can be used to set up the test
... charles and leonie have had to use inspect to do the testing
... 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
... the other radio buttons will say whether you are testing the role or name
... it runs 21-29 tests
... 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
... youl will alway be able to find the test manually
... in the diagram it will show what the test is that is being made
... I am going to put a button with pass or fail.
... you can screenscrape the results and pass them on to michael cooper to record the results.
... I should have a sample of a debugging test interface that you can put on your own personal web server.
... anyone have any questions?

rich: I think we need to see it.
... if magically web driver gets updated quick enough then we could use it

fred: the next steps in testing. We have 3, 4, or 5 things.
... we need to look and see if the tests on the wiki are sufficient and whether they are valid.
... then we need to look at the test driver is coming out Tuesday

amelia: do you have a place where the tests are available on line?

fred: I will will send everything out on Tuesday.

rich: you are going to need hundreds of tests.

fred: i did not all of svg
... the default role mappings are in there

rich: did you do all the name computation work?

fred: I think so but I need confirmation.
... i did label and aria-labelledy as well as all the attributes
... you can actually run the test, yeah

doug: should we have a telecon with the SVG working group
... we need to see where we overlap
... a lot of the older tests were manual
... some of the tests are automated
... SVG was hand done
... there are some autorun

<scribe> scribe: Rich

rich: we need to coordinate testing
... how close are they to being done in SVG2? Do they have consensus?

doug: I think it will be more like Q2
... there is a face to face in Sydney in February
... We need a joint task force meeting with the main svg working group to get particular test going
... 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
... All the things that we need to test in svg (high level)

fred: I will make a different page

doug: I will make the current page test assertions. The testing page will be a high level testing page.

rich: we need to test error conditions like an element with role=“none” and tabindex=“0”

fred: that should not be an issue

<shepazu> https://www.w3.org/wiki/SVG_Accessibility/Testing https://www.w3.org/wiki/SVG_Accessibility/Testing/Test_Assertions

<shepazu> https://www.w3.org/wiki/SVG_Accessibility/Testing and https://www.w3.org/wiki/SVG_Accessibility/Testing/Test_Assertions

fred: track and view don’t have a test

<fesch> if given <rect width="100" height="100"><animateTransform id="test" attributeName="transform" type="scale" from="2" to="3" repeatCount="3" dur="4s" fill="freeze"/></rect> then for id="test" NOAC

fred: animate transform is an example of something that is not mapped
... we need an example of every filter element to make sure it is not mapped.

doug: I can walk through the filters easily

fred: for evey todo here we need to populate it

Doug: the next meeting is January 8

<scribe> chair: Fred

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2015/12/18 16:03:59 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/valide/valid/
No ScribeNick specified.  Guessing ScribeNick: richardschwerdtfeger
Found Scribe: Rich
Found Scribe: Rich
Present: fred AmeliaBR

WARNING: Fewer than 3 people found for Present list!

Found Date: 18 Dec 2015
Guessing minutes URL: http://www.w3.org/2015/12/18-svg-a11y-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]