SVG accessibility task force Agenda Tuesday 1 pm Eastern February 9, 2016

Meeting info
This is a Tuesday 1pm Boston time meeting
Join WebEx meeting Meeting number: 645 955 799
irc: #svg-a11y
Meeting password:		 ping on IRC

Join by phone
+1-617-324-0000 US Toll Number
Access code: 645 955 799

Issue and Action Tracker https://www.w3.org/WAI/PF/svg-a11y-tf/track/
minutes from last meeting
https://lists.w3.org/Archives/Public/public-svg-a11y/2016Jan/0018.html
FYI from last two weeks - two weeks ago we cleaned up Rich's actions, last
week we did not have a meeting

Topics
   Overdue actions
   Actions review

   Amelia clarified textPath should be treated like tspan in the AAM
   Issue-1005 Conflicting ARIA semantics must be consistent with ARIA spec.
   with exceptions
   Issue-1006 multiple title and desc elements
   Issue-1007 trimming whitespace from accessible names and accessible
   descriptions
   Issue-1008: Recursive use aria-labelledby/describedby in text
   alternative computation
   Global ARIA attributes and SVG (May be related to Issue-1005)
        This can be a complicated topic since it involves several documents
and working groups. I am hearing questions like - what if an SVG element
has aria-* on it then will it appear in the accessibility tree since aria
properties are part of the API? And requests like, please make a test case
where the SVG has an aria-flowto in it. I am reluctant to make a test case
where I don't know what should happen and where I can't find in a document
where it says what should happen.

If you have additional items for the agenda, please let me know.

                                                              
     Regards,                                                 
                                                              
    Fred Esch                                                 
 Watson, IBM, W3C                                             
  Accessibility                                               
                                                              
 IBM Watson       Watson Release Management and Quality       
                                                              



--1__
BBF5C3DFF3B4858f9e8a93df938690918c0ABBF5C3DFF3B485
Content-Transfer-Encoding: quoted-printable
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline

<html><body><p><b>Meeting info</b><br>This is a Tuesday 1pm Boston time meeting<br>Join WebEx meeting Meeting number: 645 955 799<br>irc: #svg-a11y<br>Meeting password:                 ping on IRC<br><br>Join by phone<br>+1-617-324-0000 US Toll Number<br>Access code: 645 955 799<br><br>Issue and Action Tracker <a href="https://www.w3.org/WAI/PF/svg-a11y-tf/track/"><u><font color="#0000FF">https://www.w3.org/WAI/PF/svg-a11y-tf/track/</font></u></a><br>minutes from last meeting<tt><font size="4">&nbsp;</font></tt><a href="https://lists.w3.org/Archives/Public/public-svg-a11y/2016Jan/0018.html"><u><font color="#0000FF">https://lists.w3.org/Archives/Public/public-svg-a11y/2016Jan/0018.html</font></u></a><br>FYI from last two weeks - two weeks ago we cleaned up Rich's actions, last week we did not have a meeting<br><br><b>Topics</b> 
<ol type="1"><li>Overdue actions
<li>Actions review<br>
<li>Amelia clarified textPath should be treated like tspan in the AAM 
<li><a href="https://www.w3.org/WAI/PF/svg-a11y-tf/track/issues/1005">Issue-1005</a> Conflicting ARIA semantics must be consistent with ARIA spec. with exceptions
<li><a href="https://www.w3.org/WAI/PF/svg-a11y-tf/track/issues/1006">Issue-1006</a> multiple title and desc elements
<li><a href="https://www.w3.org/WAI/PF/svg-a11y-tf/track/issues/1007">Issue-1007</a> trimming whitespace from accessible names and accessible descriptions
<li><a href="https://www.w3.org/WAI/PF/svg-a11y-tf/track/issues/1008">Issue-1008</a>: Recursive use aria-labelledby/describedby in text alternative computation
<li>Global ARIA attributes and SVG (May be related to Issue-1005)</ol><font size="4">        </font>This can be a complicated topic since it involves several documents and working groups. I am hearing questions like<font size="4"> - </font><i><font size="4">what if an SVG element has aria-* on it then will it appear in the accessibility tree since aria properties are part of the API?</font></i><font size="4"> And requests like, </font><i><font size="4">please make a test case where the SVG has an aria-flowto in it</font></i><i><font size="4">. </font></i>I am reluctant to make a test case where I don't know what should happen and where I can't find in a document where it says what should happen.<br><br>If you have additional items for the agenda, please let me know.<br><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">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__=0ABBF5C3DFF3B4858f9e8a93df938690918c0AB@" 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>
</body></html>

--1__
BBF5C3DFF3B4858f9e8a93df938690918c0ABBF5C3DFF3B485--


--0__
BBF5C3DFF3B4858f9e8a93df938690918c0ABBF5C3DFF3B485
Content-type: image/gif; 
	name="51963923.gif"
Content-Disposition: inline; filename="51963923.gif"
Content-ID: <1__
BBF5C3DFF3B4858f9e8a93df938690918c0AB@>
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__
BBF5C3DFF3B4858f9e8a93df938690918c0ABBF5C3DFF3B485--

Received on Friday, 5 February 2016 18:14:00 UTC