<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 15 (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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Joe,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you for your comments, I have sent the to the ARIA Authoring Practices working group for consideration.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There is also a W3C Community Group some people may be interested in participating in call the “W3C ARIA and Assistive Technology Community Group”:<o:p></o:p></p>
<p class="MsoNormal"><a href="https://www.w3.org/community/aria-at/">https://www.w3.org/community/aria-at/</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">You do NOT need to be a member of he W3C to participate in the group and the goal of the group is to help authors understand what ARIA techniques work in the real world right now and provide information to screen reader companies where
they do not support for ARIA features or there could be improvements.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The group is lead by Matt King of Facebook and Michael Fairchild of Deque systems.<o:p></o:p></p>
<p class="MsoNormal">Matt King is also a co-chair of the ARIA Authoring Practices and the authoring practices examples and design patterns will be the basis for the test cases for investigating ARIA implementation.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It is important to note that ARIA spec only specifies what browsers must do, there are no requirements for what ATs must do with the additional information provided in the Accessibility APIs, so it is important for customers to lobby AT
companies to make sure they provide value to ARIA authoring techniques.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Jon<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> athen-list <athen-list-bounces@mailman12.u.washington.edu>
<b>On Behalf Of </b>joe@a11yeval.com<br>
<b>Sent:</b> Thursday, September 12, 2019 7:20 AM<br>
<b>To:</b> 'Access Technology Higher Education Network' <athen-list@u.washington.edu><br>
<b>Subject:</b> Re: [Athen] New version of W3C ARIA Authoring Practices available<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I think my biggest problem with the ARIA Authoring Practices is that they are now a Working Group Note which is “not intended to be a formal standard” (<a href="https://www.w3.org/2018/Process-20180201/#WGNote">https://www.w3.org/2018/Process-20180201/#WGNote</a>)
and “Publication as a Working Group Note does not imply endorsement by the W3C Membership” (<a href="https://www.w3.org/pubrules/doc/rules/?profile=FPWG-NOTE">https://www.w3.org/pubrules/doc/rules/?profile=FPWG-NOTE</a>). So I don’t see any onus for both
web browser or AT developers that requires them to adhere to the ARIA Authoring Practices which means real world support for many design patterns will be spotty or incomplete.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In addition, there are still after many revisions two design patterns that do not have working examples and sections of the document that are still incomplete. In the past, and it may still be the case, some examples did not follow the
design pattern recommendations or that included extra ARIA attributes with little or no explanation for their inclusion in the example but not the design pattern.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am all for the creation of recommended design patterns for new and complex widgets, but I feel this type of documentation needs to be created in a more efficient manner with support from web browser and AT developers to ensure they work
in the real world.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thankx,<o:p></o:p></p>
<p class="MsoNormal"> Joe Humbert<o:p></o:p></p>
<p class="MsoNormal"> Accessibility Champion<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> athen-list <<a href="mailto:athen-list-bounces@mailman12.u.washington.edu">athen-list-bounces@mailman12.u.washington.edu</a>>
<b>On Behalf Of </b>Gunderson, Jon R<br>
<b>Sent:</b> Thursday, September 5, 2019 3:33 PM<br>
<b>To:</b> Access Technology Higher Education Network <<a href="mailto:athen-list@u.washington.edu">athen-list@u.washington.edu</a>><br>
<b>Subject:</b> [Athen] New version of W3C ARIA Authoring Practices available<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">A new version of the W3C ARIA Authoring Practices was published last month.<o:p></o:p></p>
<p class="MsoNormal"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_TR_wai-2Daria-2Dpractices-2D1.1_&d=DwMFAg&c=Y6HT0gyZH_Z4ZSRJdNYJeQ&r=J9v0mCONcq6yW8Wqn227MJFNuytPEyFm-SWYS8R5nwA&m=VN-xfNA7cSdQMwATWGhgcn37PxMcncN4zF08beCWlXw&s=9EPr81pW1cAaL-RkStEGTnr3Y1CSTDa4EJN18RPp38U&e=">https://www.w3.org/TR/wai-aria-practices-1.1/</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Changes from last publication:<o:p></o:p></p>
<p class="MsoNormal"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_TR_wai-2Daria-2Dpractices-2D1.1_-23change-5Flog&d=DwMFAg&c=Y6HT0gyZH_Z4ZSRJdNYJeQ&r=J9v0mCONcq6yW8Wqn227MJFNuytPEyFm-SWYS8R5nwA&m=VN-xfNA7cSdQMwATWGhgcn37PxMcncN4zF08beCWlXw&s=MRRQr8n70vcG5NQ5dKh6KZNmXCRN2BmzKoBK0kK0lGY&e=">https://www.w3.org/TR/wai-aria-practices-1.1/#change_log</a>
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This is a useful resource for web developers and designers to understand how to use ARIA markup to create WCAG 2.1 compliant web resources and can also be used by quality assurance testers to developing testing protocols and provide feedback
to developers and designers.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Jon<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;color:black">Jon Gunderson, Ph.D., CPWA<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;color:black">Coordinator of Accessible IT Group<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;color:black">University of Illinois at Urbana/Champaign<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;color:black">1207 S. Oak Street<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;color:black">Champaign, IL 61820<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;color:black">www:
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__go.illinois.edu_jongund&d=DwMFAg&c=Y6HT0gyZH_Z4ZSRJdNYJeQ&r=J9v0mCONcq6yW8Wqn227MJFNuytPEyFm-SWYS8R5nwA&m=VN-xfNA7cSdQMwATWGhgcn37PxMcncN4zF08beCWlXw&s=RtDD3ZHitP4c0GSXfRoIIlLKBZkXHKCQNv7mn9WENqs&e=">
<span style="color:#552299">https://go.illinois.edu/jongund</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>