- From: Fred Esch <fesch@us.ibm.com>
- Date: Mon, 21 Dec 2015 10:01:45 -0500
- To: Michael Cooper <cooper@w3.org>
- Cc: <public-svg-a11y@w3.org>
- Message-Id: <201512211513.tBLFD4xb018477@d01av01.pok.ibm.com>
Michael,
As far as I can tell, 99% of the SVG accessibility tests will come from the
SVG Accessibility API Mappings document. From looking at the mapping
table, only one element (text) has a platform specific result. Unless more
platform specific results pop up, I can handle that post csv file creation.
It seems like the easiest way to handle this singular case is by
duplicating the row and adding the specific platform/result. For all other
tests, would you prefer an empty column in a csv or a value like "all".
This will be auto filled so whatever works easiest for you will work for
me. I may add which section the test is about. I think there is only
three sections that the vast majority of tests come from:
5.1.1 Excluding Elements from the Accessibility Tree
5.1.2 Including Elements in the Accessibility Tree
10.1 Name and Description
There is one more section on views that could be referenced that will apply
to a very small number of tests and I think view handling may still be TBD
in the SVG WG. If views are not TBD and we are missing view tests - please
feel free to add the tests. If anyone knows of another section that should
be referenced on the tests, please let me know.
The WAI-ARIA Graphics Module only includes two roles and no properties or
attributes. So we can add tests for the two roles, which if it useful could
have it's doc/section pointer edited by hand if need be.
I can extract over 100 tests from the wiki markup on our test assertions
page, so I would like to make as much as possible automated and minimize
work either you or I need to do as a post csv creation step.
Currently I create two csv files for tests. One for native SVG test files
and one for HTML test files. In the csv files I only save the filename not
the path (I put the svg files in a different directory than the HTML
files). I don't know what the organization of the files will be on the
server and what their path will be. Is this OK that I only put the filename
is the csv and will let you add the relative path? Or do you want to
provide me a path string which I can prepend to the filename in the script?
SVG Accessibility Task Force Folks,
FYI, Michael's test harness is very similar to what I would have made, so I
am not going to create our own.
Several folks are going to review testable statements or help fill in
missing/TODO tests. If you notice a category of tests that I have
forgotten, please let me know or add them in - Rich mentioned that we were
needed to test role = none and role = presentation on Friday so I am adding
those. Everyone should feel free to review tests, correct mistakes and fill
it TODOs. Doug said he will do the filter related (fe*) TODOs.
If you are checking testable statements for accuracy, please go ahead and
correct errors. Also, let folks know what you have reviewed so other folks
can prioritize their reviews. If you find errors, please fix them, if there
is something systematic and you think it will be a PITA you can let me know
and I will fix them. If you find gray areas please post them on list and
bring them up on our first meeting in January.
January 8 is our next scheduled meeting. Look for a straw poll on a new
date and time for the meetings...
Happy holidays
to all,
Fred Esch
Watson, IBM, W3C
Accessibility
IBM Watson Watson Release Management and Quality
From: Michael Cooper <cooper@w3.org>
To: Fred Esch/Arlington/IBM@IBMUS, cooper@w3c.org
Date: 12/18/2015 05:41 PM
Subject: Re: testing db
Minimally speaking, test cases require a testable statement and test file
reference. Expect results need a platform to which they apply (unless
they're platform independent) and the result itself. All the rest of what I
sent you is optional, but helpful. Michael
On 18/12/2015 5:36 PM, Fred Esch wrote:
Hi Michael,
Happy holidays. I am automatically generating test files for testable
statement on our wiki. I could automatically generate the info for
the test cases as well. I assume the test cases are actually rows in
a DB and we can simply have you import the lot of them. Please let me
know which columns are required and which columns are optional. I
believe almost all of our tests will have the same expected result on
all platforms and the ones that don't could be identified and edited.
All the tests that we can do this way are stuff that will appear (or
not) in the accessibility tree.
The task force may work the SVG team on testing tabindex and
interactivity, but those tests would be handled in a different
manner.
Regards,
Fred Esch
Watson, IBM, W3C
Accessibility
IBM Watson Release Management and
Watson Quality
--1__
BBF5B1DFDFA22D8f9e8a93df938690918c0ABBF5B1DFDFA22D
Content-Transfer-Encoding: quoted-printable
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline
<html><body bgcolor="#FFFFFF"><p>Michael,<br><br>As far as I can tell, 99% of the SVG accessibility tests will come from the SVG Accessibility API Mappings document. From looking at the mapping table, only one element (text) has a platform specific result. Unless more platform specific results pop up, I can handle that post csv file creation. It seems like the easiest way to handle this singular case is by duplicating the row and adding the specific platform/result. For all other tests, would you prefer <b>an empty column</b> in a csv or a value like "<b>all</b>". This will be auto filled so whatever works easiest for you will work for me. I may add which section the test is about. I think there is only three sections that the vast majority of tests come from:
<ul type="disc"><li><a href="https://rawgit.com/w3c/aria/master/svg-aam/svg-aam.html#exclude_elements">5.1.1 Excluding Elements from the Accessibility Tree</a><li><a href="https://rawgit.com/w3c/aria/master/svg-aam/svg-aam.html#include_elements">5.1.2 Including Elements in the Accessibility Tree</a><li><a href="https://rawgit.com/w3c/aria/master/svg-aam/svg-aam.html#mapping_additional_nd">10.1 Name and Description</a></ul><br>There is one more section on views that could be referenced that will apply to a very small number of tests and I think view handling may still be TBD in the SVG WG. If views are not TBD and we are missing view tests - please feel free to add the tests. If anyone knows of another section that should be referenced on the tests, please let me know.<br><br>The<a href="http://www.w3.org/TR/2015/WD-graphics-aria-1.0-20151203/"> WAI-ARIA Graphics Module</a> only includes two roles and no properties or attributes. So we can add tests for the two roles, which if it useful could have it's doc/section pointer edited by hand if need be.<br><br>I can extract over 100 tests from the wiki markup on our <a href="https://www.w3.org/wiki/SVG_Accessibility/Testing/Test_Assertions#No_role_not_included_in_accessibility_tree_testable_statements">test assertions page</a>, so I would like to make as much as possible automated and minimize work either you or I need to do as a post csv creation step.<br><br>Currently I create two csv files for tests. One for native SVG test files and one for HTML test files. In the csv files I only save the filename not the path (I put the svg files in a different directory than the HTML files). I don't know what the organization of the files will be on the server and what their path will be. Is this OK that I only put the filename is the csv and will let you add the relative path? Or do you want to provide me a path string which I can prepend to the filename in the script?<br><br>SVG Accessibility Task Force Folks,<br><br>FYI, Michael's test harness is very similar to what I would have made, so I am not going to create our own. <br><br>Several folks are going to review testable statements or help fill in missing/TODO tests. If you notice a category of tests that I have forgotten, please let me know or add them in - Rich mentioned that we were needed to test role = none and role = presentation on Friday so I am adding those. Everyone should feel free to review tests, correct mistakes and fill it TODOs. Doug said he will do the filter related (fe*) TODOs.<br><br>If you are checking testable statements for accuracy, please go ahead and correct errors. Also, let folks know what you have reviewed so other folks can prioritize their reviews. If you find errors, please fix them, if there is something systematic and you think it will be a PITA you can let me know and I will fix them. If you find gray areas please post them on list and bring them up on our first meeting in January.<br><br>January 8 is our next scheduled meeting. Look for a straw poll on a new date and time for the meetings...<br><br>
<table border="0" cellspacing="0" cellpadding="0"><tr valign="top"><td width="473" colspan="2" valign="middle"><div align="center"><font size="4" face="Verdana">Happy holidays to all, <br><br>Fred Esch <br>Watson, IBM, W3C Accessibility</font></div></td></tr>
<tr valign="top"><td width="130" valign="middle"><img src="cid:1__=0ABBF5B1DFDFA22D8f9e8a93df938690918c0AB@" width="163" height="23" alt="IBM Watson" align="bottom"></td><td width="342" valign="middle"><font size="4" face="Verdana">Watson Release Management and Quality </font></td></tr></table><br><br><img width="16" height="16" src="cid:2__=0ABBF5B1DFDFA22D8f9e8a93df938690918c0AB@" border="0" alt="Inactive hide details for Michael Cooper ---12/18/2015 05:41:37 PM---Minimally speaking, test cases require a testable statemen"><font color="#424282">Michael Cooper ---12/18/2015 05:41:37 PM---Minimally speaking, test cases require a testable statement and test file reference. Expect results</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Michael Cooper <cooper@w3.org></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">Fred Esch/Arlington/IBM@IBMUS, cooper@w3c.org</font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">12/18/2015 05:41 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: testing db</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><font size="4">Minimally speaking, test cases require a testable statement and test file reference. Expect results need a platform to which they apply (unless they're platform independent) and the result itself. All the rest of what I sent you is optional, but helpful. Michael<br></font><br><font size="4">On 18/12/2015 5:36 PM, Fred Esch wrote:</font><ul><ul><font size="4">Hi Michael,<br><br>Happy holidays. I am automatically generating test files for testable statement on our wiki. I could automatically generate the info for the test cases as well. I assume the test cases are actually rows in a DB and we can simply have you import the lot of them. Please let me know which columns are required and which columns are optional. I believe almost all of our tests will have the same expected result on all platforms and the ones that don't could be identified and edited. All the tests that we can do this way are stuff that will appear (or not) in the accessibility tree.<br><br>The task force may work the SVG team on testing tabindex and interactivity, but those tests would be handled in a different manner.<br><br></font><table border="0" cellspacing="0" cellpadding="0"><tr valign="top"><td width="404" colspan="2" valign="middle"><div align="center"><font size="5" face="Verdana">Regards, <br><br>Fred Esch <br>Watson, IBM, W3C Accessibility</font></div></td></tr>
<tr valign="top"><td width="130" valign="middle"><img src="cid:1__=0ABBF5B1DFDFA22D8f9e8a93df938690918c0AB@" width="163" height="23" alt="IBM
Watson" align="bottom"></td><td width="274" valign="middle"><font size="5" face="Verdana">Watson Release Management and Quality </font></td></tr></table><font size="4"><br></font></ul></ul>
<p><BR>
</body></html>
--1__
BBF5B1DFDFA22D8f9e8a93df938690918c0ABBF5B1DFDFA22D--
--0__
BBF5B1DFDFA22D8f9e8a93df938690918c0ABBF5B1DFDFA22D
Content-type: image/gif;
name="0A360514.gif"
Content-Disposition: inline; filename="0A360514.gif"
Content-ID: <1__
BBF5B1DFDFA22D8f9e8a93df938690918c0AB@>
Content-Transfer-Encoding: base64
iVBORw0KGgoAAAANSUhEUgAAAKMAAAAXCAMAAABQ6Q/RAAADAFBMVEXIx8cxLS5MSUrW1dXx8fE/
Ozzj4+N2c3SRj49oZWaEgYKsq6uenZ26ubmbm5v29vZ7e3tTU1M7OzsfHx/FxcX39/eamppmZmaR
j5AgICCqqqrR0dFaV1gAAAAjHyD///8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAADe7fL7AAADE0lEQVR4nM2WiW7kIAyGTbhz9O6eCL//U6bYGJJOst2dlaqppUm4
+fhtnAH8+gb7sroZxodWGZfA5UxP52+Ic2qVEbLDxujTLXnOTHydSDxNdC7DR+NvYQK02PLQYBDn
z5dRw04GAPibKIBec2GKuZjyrtbosVZr72J397Xyc+suPshsiOUBvRb4xavlzYoA2tI+XEQTFDfT
rkCFiFLIec8Y82jQ0dIhjOU5lmWGa254owKe/J5xPDBqdYHLphZBm08Zi5/nOnEsEUmHwiG6cx3X
Z6k8ID5c6kgHHC4YlblkJHcNlotO7Xp0RVP6lLFIPtTmsuDQDn+FGT4YTy3OXcTFEy85VUYonQMQ
WHWopSIdR83aTYRs5bBD9cz+VjBjyI3RbVEkSu7ed/XF8r18ExXF25ZJiWnk/RhD1S1JlFT5mLGc
B0KYNJG5rtEkLhjPGUVz32Lh2iw+k68WnhqJjeZTldqBr27dFkCz2mlyooxcac0zJUyWM8YKFnn8
KLofdFy7brvwXLctZs+6KScOTrSr6uft2y4SmJqa+tUcxPeKY/iEcc4+W8qNfYUrdSTtYvnRrfE1
rgk1QOqBs207ideoc2gLJGFMtEQ6YQy53OvwA1DifmM86PhQKxSZ66+uI/o6zdVcMmwtRHrBiGbm
XWysp2FTjbERHHUEPXAgtDRxrY5Vfsvph6PebGnFvmcswSnp2PcDcECPdYzkz2M8ziBH9rtl8c/3
Gh/X9TtuOhphWyToedNUzEp0boyZ8zQNnHLrXIhLy5jplBHVINnHmKj+415Lamt+QAdWDkphmcC5
mh8lodvqNsOqDyHw5GjamHjKGLKEj66LuK7i5XfmsVbwdX1+leL9vTiLIiTy8qFFjHwygjQA7j46
sUc/oxpoY4w9YzRW+RbsZeJ135mnJ9ErCuv8T4yqCGH6zYoGOyOXDowSqJ5yRtq6jzq2/z2IL7+l
H58eaWxMiULLlRjUOCU2+kfKNkkDuam8KJP6eqPB0+eIU7PexswpjQdG5AAJEOL1X+vPt/7/cuLg
UP7L/QtHfANvSEKvsxvttAAAAABJRU5ErkJggg=
--0__
BBF5B1DFDFA22D8f9e8a93df938690918c0ABBF5B1DFDFA22D
Content-type: image/gif;
name="graycol.gif"
Content-Disposition: inline; filename="graycol.gif"
Content-ID: <2__
BBF5B1DFDFA22D8f9e8a93df938690918c0AB@>
Content-Transfer-Encoding: base64
R0lGODlhEAAQAKECAMzMzAAAAP///wAAACH5BAEAAAIALAAAAAAQABAAAAIXlI+py+0PopwxUbpu
ZRfKZ2zgSJbmSRYAIf4fT3B0aW1pemVkIGJ5IFVsZWFkIFNtYXJ0U2F2ZXIhAAA7
--0__
BBF5B1DFDFA22D8f9e8a93df938690918c0ABBF5B1DFDFA22D--
Received on Monday, 21 December 2015 15:13:39 UTC