- From: Fred Esch <fesch@us.ibm.com>
- Date: Mon, 20 Jun 2016 09:12:21 -0400
- To: "Gunderson, Jon R" <jongund@illinois.edu>
- Cc: public-aria-test@w3.org
- Message-Id: <OFA026FB36.C3367491-ON85257FD8.0046C1D7-85257FD8.00488B14@notes.na.collabserv.c>
Hi Jon,
I wanted to make you aware of what we have for SVG testing at the moment
and what are plans were. I hope our current plans will be superseded by
automated testing.
Existing SVG testing plans
We have a couple of wiki pages of testable statements. This is the wiki
page for the non-language dependent tests. A second wiki page is the the
language dependent tests that have multiple title and/or desc elements
with lang attributes. Multiple title/desc with lang attributes are an
at risk feature and is likely to not make it in SVG 2. The note row of
the expected results table is the id of Joanie's webkit layout test.
I have a Perl script that takes the wiki markup and builds test files in
two directories and builds a JSON file with info needed for the old PF
test harness for all the tests on the wiki page. We planned on having
two test files for each test as we wanted to perform the test on an SVG
file and an HTML file with imbedded SVG.
I was going to give the zipped test files and JSON file to Michael
Cooper and he was going to import them into the PF test harness.
Automated testing
Joanie has incorporated the non-language dependent tests in webkit layout
tests. In the note row of the expected output table for each testable
statement, Joanie has put the layout test id.
It would be great if we could get the other platforms doing automated
testing. Hoping what Cynthia has will help do that. Whatever automated
testing we can set up for HTML, we would like to do for SVG as well.
Regards,
Fred Esch
Watson, IBM, W3C
Accessibility
IBM Watson Watson Release Management and Quality
Attachments
- image/gif attachment: 14838167.gif
Received on Monday, 20 June 2016 13:13:33 UTC