<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1><pre>I have been requested to forward on the following important information regarding accessibility issues with the canvas element. If you have an interest in this area, or have some suggestions on how to overcome some of the known issues, then please consider actively following this W3C discussion, or better yet volunteer to be part of the Task Force.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Thanks!<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>JF<o:p></o:p></pre><pre>*********************<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>update on ACTION-132 Report on canvas accessibility[1]<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>The Protocols and formats working group discussed the issues of canvas<o:p></o:p></pre><pre>accessibility in their HTML caucus meeting last Friday (17/07/09).<o:p></o:p></pre><pre>It has been decided to form a task force to work on specifying additions to<o:p></o:p></pre><pre>the CANVAS API, that will result in canvas content being natively<o:p></o:p></pre><pre>accessible.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>The task force is open to participation by any interested parties, the PF<o:p></o:p></pre><pre>will host public bi-weekly teleconferences dedicated to the topic of canvas<o:p></o:p></pre><pre>accessibility.<o:p></o:p></pre><pre>The initial duration of the task force will be at least 3 months, but more<o:p></o:p></pre><pre>likely 6 months, as I am sure that it is appreciated by all, the provision<o:p></o:p></pre><pre>of a canvas API that could be considered to output accessible content is no<o:p></o:p></pre><pre>simple undertaking.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>We have approached and are continuing to reach out to browsers vendors and<o:p></o:p></pre><pre>other individuals and companies who can bring their expertise to bear on<o:p></o:p></pre><pre>what is considered to be a critical accessibility issue in HTML5.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>The first meeting is expected to take place in the 1st or 2nd week of<o:p></o:p></pre><pre>august, all discussion related to the canvas accessibility task force will<o:p></o:p></pre><pre>be on the public html wg or wai-xtech lists.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>notification and agenda for the first teleconference will be published when<o:p></o:p></pre><pre>the date has been confirmed.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>[1]<a
href="http://www.w3.org/html/wg/tracker/actions/132">http://www.w3.org/html/wg/tracker/actions/132</a><o:p></o:p></pre><pre>-- <o:p></o:p></pre><pre>with regards<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Steve Faulkner<o:p></o:p></pre><pre>Technical Director - TPG Europe<o:p></o:p></pre><pre>Director - Web Accessibility Tools Consortium<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><a
href="http://www.paciellogroup.com">www.paciellogroup.com</a> | <a
href="http://www.wat-c.org">www.wat-c.org</a><o:p></o:p></pre><pre>Web Accessibility Toolbar -<o:p></o:p></pre><pre><a
href="http://www.paciellogroup.com/resources/wat-ie-about.html">http://www.paciellogroup.com/resources/wat-ie-about.html</a><o:p></o:p></pre>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>