<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi all,</div>
<div style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I had a couple of folks reach out to me with questions about Overlays/Widgets wanting more information about why we cannot trust these options to provide true web accessibility. Here is more information for your review.</div>
<div style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<ol>
<li><b><a href="https://www.youtube.com/watch?v=R12Z1Sp-u4U&t=17s" title="https://www.youtube.com/watch?v=R12Z1Sp-u4U&t=17s">3 Minute YouTube video of Haben Girma warning us about the danger of quick-fix solutions</a>.</b> (Posted May 5th, 2021)</li><li style="display:block"><br>
</li><li><a href="https://overlayfactsheet.com/" title="https://overlayfactsheet.com/"><b>Overlayfactsheet.com</b></a></li><li style="display:block"><br>
</li><li><a href="https://www.levelaccess.com/do-accessibility-overlays-and-widgets-provide-full-and-equal-access%E2%80%8B-as-required-under-the-adas-general-rule/" target="_blank" rel="noopener noreferrer" data-auth="NotApplicable" title="https://www.levelaccess.com/do-accessibility-overlays-and-widgets-provide-full-and-equal-access%E2%80%8B-as-required-under-the-adas-general-rule/" data-linkindex="2" style="margin:0px;outline:0px;background-color:rgb(255, 255, 255)"><b>Do
Accessibility Overlays and Widgets Provide 'Full and Equal Access' as Required Under the ADA's General Rule?</b></a><span style="background-color:rgb(255, 255, 255);display:inline !important"><span> </span>by Level Access.</span><br>
</li></ol>
</div>
<div>
<div style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<div style="margin:0px; font-size:15px; color:rgb(32,31,30); text-align:start; background-color:rgb(255,255,255)">
<p style="font-size:11pt; font-family:Calibri,sans-serif; margin:0px"><img align="left" alt="Title: SBCTC logo - Description: Compass" style="width: 60px; height: 113px; max-width: initial;" width="60" height="113" data-outlook-trace="F:1|T:1" src="cid:0d0e9821-11bc-4113-8ce5-ea969ed6c9cd"></p>
<p style="font-size:11pt; font-family:Calibri,sans-serif; margin:0px"><b><span style="margin: 0px; font-size: 14pt; font-family: "Franklin Gothic Book", sans-serif, serif, EmojiFont; color: rgb(0, 32, 96);">Monica M. Olsson (she/her/hers)</span></b></p>
<p style="font-size:11pt; font-family:Calibri,sans-serif; margin:0px"><span style="margin:0px; font-size:12pt; font-family:"Franklin Gothic Book",sans-serif,serif,EmojiFont; color:rgb(0,32,96)">Policy Associate – Accessible IT Coordinator</span></p>
<p style="font-size:11pt; font-family:Calibri,sans-serif; margin:0px"><span style="margin:0px; font-size:12pt; font-family:"Franklin Gothic Book",sans-serif,serif,EmojiFont; color:rgb(0,32,96)">Washington State Board for Community and Technical Colleges</span></p>
<p style="font-size:11pt; font-family:Calibri,sans-serif; margin:0px"><u><span style="margin:0px; font-size:12pt; font-family:"Franklin Gothic Book",sans-serif,serif,EmojiFont; color:rgb(5,99,193)"><a href="mailto:molsson@sbctc.edu" target="_blank" rel="noopener noreferrer" style="margin:0px"><span style="margin:0px"><b>molsson@sbctc.edu</b></span></a></span></u><span style="margin:0px; font-size:12pt; font-family:"Franklin Gothic Book",sans-serif,serif,EmojiFont; color:rgb(0,32,96)"><span><b> </b></span>•
o: 360-704-3922 • c: 206-914-7187</span></p>
<p style="font-size:11pt; font-family:Calibri,sans-serif; margin:0px"><span style="margin:0px; font-size:12pt; font-family:"Franklin Gothic Book",sans-serif,serif,EmojiFont; color:rgb(0,32,96)"><a href="https://www.sbctc.edu/" target="_blank" rel="noopener noreferrer" style="margin:0px">sbctc.edu</a><span> </span>•
Twitter:<span> </span><a href="https://twitter.com/SBCTCWashington" target="_blank" rel="noopener noreferrer" style="margin:0px"><b>@SBCTCWashington</b></a><span> </span>• Facebook:<b><span> </span><a href="https://www.facebook.com/wasbctc/" target="_blank" rel="noopener noreferrer" style="margin:0px">@WASBCTC</a></b></span></p>
</div>
<br>
</div>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> ATcoord <atcoord-bounces@lists.ctc.edu> on behalf of Monica Olsson via ATcoord <atcoord@lists.ctc.edu><br>
<b>Sent:</b> Monday, February 28, 2022 8:58 PM<br>
<b>To:</b> atcoord@lists.ctc.edu <atcoord@lists.ctc.edu><br>
<b>Cc:</b> Monica Olsson <molsson@sbctc.edu><br>
<b>Subject:</b> [ATcoord] When you see an overlay, it's best to run the other way!</font>
<div> </div>
</div>
<style type="text/css" style="display:none">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div style="font-family:Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Hi AT Coords!</div>
<div style="font-family:Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Accessibility.com published its 2021 Web Accessibility Lawsuit Recap Report, which is attached. In the report, overlays are specifically called out as problematic. I have included an excerpt below.</div>
<div style="font-family:Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
"In September 2020, Disability Rights Advocates filed a lawsuit against Automatic Data Processing, Inc. (ADP), representing the LightHouse for the Blind and Visually Impaired of San Francisco and individuals Erin Lauridsen and Frank Welte. I<span style="color:rgb(0,0,0); font-family:Arial,Helvetica,sans-serif; font-size:12pt">n
December 2021, Disability Rights Advocates published a statement announcing that a settlement had been reached, along with a copy of the settlement agreement.</span></div>
<div style="font-family:Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<span style="color:rgb(0,0,0); font-family:Arial,Helvetica,sans-serif; font-size:12pt"><br>
</span></div>
<div style="font-family:Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<span style="color:rgb(0,0,0); font-family:Arial,Helvetica,sans-serif; font-size:12pt">In the agreement is a definition of “accessible,” as follows: “Accessible” (or “Accessibility” or “Access”) means that blind and low vision individuals have independent access
to the same information and equivalent ease of use of functionalities available to sighted individuals via the Website or Mobile Apps.
<b>For the purpose of this Agreement, “overlay” solutions such as those currently provided by companies such as AudioEye and AccessiBe will not suffice to achieve Accessibility."</b></span></div>
</div>
</body>
</html>