<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=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Lucida Bright";
panose-1:2 4 6 2 5 5 5 2 3 4;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
margin-top:0in;
margin-right:0in;
margin-bottom:7.5pt;
margin-left:0in;
font-size:14.0pt;
font-family:"Cambria","serif";
font-weight:bold;}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:7.5pt;
margin-left:0in;
font-size:13.0pt;
font-family:"Cambria","serif";
font-weight:bold;}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:7.5pt;
margin-left:0in;
font-size:12.0pt;
font-family:"Cambria","serif";
font-weight:bold;}
h4
{mso-style-priority:9;
mso-style-link:"Heading 4 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
h5
{mso-style-priority:9;
mso-style-link:"Heading 5 Char";
margin-top:0in;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.3in;
page-break-after:avoid;
font-size:12.0pt;
font-family:"Cambria","serif";
font-weight:normal;}
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;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoQuote, li.MsoQuote, div.MsoQuote
{mso-style-priority:29;
mso-style-link:"Quote Char";
margin-top:0in;
margin-right:.5in;
margin-bottom:6.0pt;
margin-left:.5in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
span.QuoteChar
{mso-style-name:"Quote Char";
mso-style-priority:29;
mso-style-link:Quote;
color:black;}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Cambria","serif";
font-weight:bold;}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-family:"Cambria","serif";
font-weight:bold;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Cambria","serif";
font-weight:bold;}
span.Heading4Char
{mso-style-name:"Heading 4 Char";
mso-style-priority:9;
mso-style-link:"Heading 4";
font-family:"Cambria","serif";
font-weight:bold;
font-style:italic;}
span.Heading5Char
{mso-style-name:"Heading 5 Char";
mso-style-priority:9;
mso-style-link:"Heading 5";
font-family:"Cambria","serif";}
p.gmail-m35293832369296246gmail-m-685350968077809861gmail-, li.gmail-m35293832369296246gmail-m-685350968077809861gmail-, div.gmail-m35293832369296246gmail-m-685350968077809861gmail-
{mso-style-name:gmail-m_35293832369296246gmail-m_-685350968077809861gmail-;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle28
{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;}
/* List Definitions */
@list l0
{mso-list-id:-132;
mso-list-type:simple;
mso-list-template-ids:-497637982;}
@list l0:level1
{mso-level-tab-stop:1.25in;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;}
@list l1
{mso-list-id:-131;
mso-list-type:simple;
mso-list-template-ids:407512160;}
@list l1:level1
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
margin-left:1.0in;
text-indent:-.25in;}
@list l2
{mso-list-id:-130;
mso-list-type:simple;
mso-list-template-ids:453006228;}
@list l2:level1
{mso-level-tab-stop:.75in;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;}
@list l3
{mso-list-id:-129;
mso-list-type:simple;
mso-list-template-ids:1562834036;}
@list l3:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4
{mso-list-id:-128;
mso-list-type:simple;
mso-list-template-ids:444212142;}
@list l4:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.25in;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;
font-family:Symbol;}
@list l5
{mso-list-id:-127;
mso-list-type:simple;
mso-list-template-ids:-1143419264;}
@list l5:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
margin-left:1.0in;
text-indent:-.25in;
font-family:Symbol;}
@list l6
{mso-list-id:-126;
mso-list-type:simple;
mso-list-template-ids:756335792;}
@list l6:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.75in;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;
font-family:Symbol;}
@list l7
{mso-list-id:-125;
mso-list-type:simple;
mso-list-template-ids:980983566;}
@list l7:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l8
{mso-list-id:-120;
mso-list-type:simple;
mso-list-template-ids:2035320948;}
@list l8:level1
{mso-level-tab-stop:.25in;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;}
@list l9
{mso-list-id:-119;
mso-list-type:simple;
mso-list-template-ids:100315206;}
@list l9:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.25in;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="WordSection1">
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">Kara,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">The new Section 508 actually gives some guidance on this, in the Standards and Guidelines, section E207 Software. That was based in large part by the work done by the W3C, published as a
Working Group Note, “<a href="https://www.w3.org/TR/wcag2ict/">Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT)</a>”.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">sb<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Lucida Bright","serif";color:#1F497D">Sarah E. Bourne<br>
Director of IT Accessibility, MassIT <br>
Commonwealth of Massachusetts<br>
1 Ashburton Pl. rm 811 Boston MA 02108<br>
617-626-4502 <br>
<a href="mailto:sarah.bourne@mass.gov"><span style="color:#1F497D">sarah.bourne@mass.gov</span></a>
<br>
<a href="http://www.mass.gov/MassIT"><span style="color:#1F497D">http://www.mass.gov/MassIT</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> athen-list [mailto:athen-list-bounces@mailman13.u.washington.edu]
<b>On Behalf Of </b>Zirkle, Kara<br>
<b>Sent:</b> Tuesday, March 28, 2017 8:59 AM<br>
<b>To:</b> athen-list@u.washington.edu<br>
<b>Subject:</b> [Athen] WCAG 2.0 vs Desktop Software<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Hello all, <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Working with vendors in the procurement phase and referencing WCAG 2.0 level AA compliance I'm beginning to see some push back for desktop software. What do you consider an "acceptable" accessibility response and documentation from a vendor
in this case? <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">PS, please keep in mind the original VPAT I received was from 2014 and I've asked for an updated version, notified the vendor of the updated standards and used most of this email along with a manual accessibility report shared with the
vendor requesting a timeline for changes. The vendor is just hesitant to provide much of anything aside from an old VPAT. This is a common program used in higher education and is installed in most any of our computer labs. So to pull it and/or find an alternative
is almost impossible. We have our internal processes that I know what I need to do to complete the project and close it, but wanted to give it as an example to get other peoples thoughts on the accessibility standards and conversation with vendors around
desktop software. It seems as if keeping it as a desktop rather than moving it to a cloud allows them to have a loop hole of less accessibility standards to meet with the current way things are written. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal">Since the new Section 508 standard is now in effect and reflects similar to WCAG 2.0 we still use this as best practice. While I understand software is different from web-based applications and websites, many of the UI areas of WCAG 2.0
still apply as best practice design. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">With that said the new 508 standards are in effect, state the following specific to software:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<h4 style="mso-margin-top-alt:12.0pt;margin-right:0in;margin-bottom:6.0pt;margin-left:0in;background:#F1F1F1;vertical-align:baseline;outline:0px;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-origin:initial;background-clip:initial;box-sizing:border-box;word-wrap:break-word" id="gmail-m_35293832369296246gmail-m_-685350968077809861gmail-h-16">
<span style="font-family:"Helvetica","sans-serif";color:#333333;text-transform:uppercase">5. EXPANDED INTEROPERABILITY REQUIREMENTS<o:p></o:p></span></h4>
<p class="gmail-m35293832369296246gmail-m-685350968077809861gmail-" style="line-height:20.4pt;background:#F1F1F1;vertical-align:baseline;outline:0px;background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-origin:initial;background-clip:initial;box-sizing:border-box;overflow:visible" id="gmail-m_35293832369296246gmail-m_-685350968077809861gmail-p-20">
<span style="font-family:"Georgia","serif";color:#333333">The existing standards require ICT to be compatible with assistive technology—that is, hardware or software that increases or maintains functional capabilities of individuals with disabilities (<em><span style="font-family:"Georgia","serif";border:none windowtext 1.0pt;padding:0in">e.g.,</span></em> screen
magnifiers or refreshable braille displays). However, in the past the existing requirement resulted in ambiguity of application. For example, some agencies interpreted the provisions of existing <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.federalregister.gov_select-2Dcitation_2017_01_18_36-2DCFR-2D1194.21&d=DwMFaQ&c=lDF7oMaPKXpkYvev9V-fVahWL0QWnGCCAfCDz1Bns_w&r=rhLenV33VPpmkT7iP0-OkUlRYw9YWn3HMLHZVP2q9y8&m=puvCBfHBcmk6oOHrWyFrC4HtdT6FxAe1Yam8tVDoGEk&s=FenAb2iv4ZacZFn3uLzrZf-9KZQdmf-UvfghHf2tgSQ&e=" target="_blank"><span style="color:#3071A9;border:none windowtext 1.0pt;padding:0in;text-decoration:none">36
CFR 1194.21</span></a> (which addresses software applications and operating systems) as applicable to assistive technology itself. The ensuing confusion led, in some cases, to unnecessary delay in procurements intended to provide reasonable accommodations
to employees under Section 501, creating a hardship for both agencies and their employees with disabilities. The final rule provides more specificity about how operating systems, software development toolkits, and software applications should interact with
assistive technology. The final rule also specifically exempts assistive technology from the interoperability provisions. The Board expects the final rule to improve software interoperability with assistive technology, allowing users better access to the functionalities
that ICT products provide.<o:p></o:p></span></p>
</div>
</div>
<div style="margin-top:1.5pt">
<div id="gmail-:29y">
<p class="MsoNormal"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.federalregister.gov_documents_2017_01_18_2017-2D00395_information-2Dand-2Dcommunication-2Dtechnology-2Dict-2Dstandards-2Dand-2Dguidelines&d=DwMFaQ&c=lDF7oMaPKXpkYvev9V-fVahWL0QWnGCCAfCDz1Bns_w&r=rhLenV33VPpmkT7iP0-OkUlRYw9YWn3HMLHZVP2q9y8&m=puvCBfHBcmk6oOHrWyFrC4HtdT6FxAe1Yam8tVDoGEk&s=PF7VXOHXvI6tOHqRjYBOebHzJXKXIbQ-orIrxvxa5qk&e=" target="_blank">https://www.federalregister.gov/documents/2017/01/18/2017-00395/information-and-communication-technology-ict-standards-and-guidelines</a><span style="border:solid windowtext 1.0pt;padding:0in"><img border="0" width="100" height="100" id="_x0000_i1025" src="cid:~WRD000.jpg" alt="Image removed by sender."></span><o:p></o:p></p>
</div>
<div id="gmail-:29y">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="gmail-:29y">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="gmail-:29y">
<p class="MsoNormal">I'd love to get other folks thoughts on the accessibility standard for desktop software. <o:p></o:p></p>
</div>
<div id="gmail-:29y">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="gmail-:29y">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="gmail-:29y">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Kara Zirkle<o:p></o:p></p>
<div>
<p class="MsoNormal">Accessible Technology Specialist<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">Information Technology Services<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Hoyt Hall, 312V<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Oxford, OH 45056<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal">Phone: 513-529-9006<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Email: <a href="mailto:zirklek@miamioh.edu" target="_blank">
zirklek@miamioh.edu</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>