<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 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:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hi all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Getting to this a little late, but I just came across the following article regarding using overlays as an accessibility solution in the last WebAIM newsletter. It’s quite interesting.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a href="https://medium.com/@sheribyrnehaber/overlays-are-not-the-solution-to-your-accessibility-problem-c5ffe44bd61f">https://medium.com/@sheribyrnehaber/overlays-are-not-the-solution-to-your-accessibility-problem-c5ffe44bd61f</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Have a great weekend,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Russell<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>From:</b> athen-list <athen-list-bounces@mailman12.u.washington.edu>
<b>On Behalf Of </b>Lucy GRECO<br>
<b>Sent:</b> Tuesday, February 11, 2020 2:06 PM<br>
<b>To:</b> Access Technology Higher Education Network <athen-list@u.washington.edu><br>
<b>Subject:</b> Re: [Athen] UserWay<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">hello:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> i wanted to add one more worning about this kind of tool bar. as a screen reader user i find these overlays get in my way and end up blocking me from using an already hard to use or an accessible web site. many of these over lays will
draw focus continually witch then means that the screen reader user can not get to any thing elce on the page. i find then more problematic then any thing elce you could do on a web site.lucy
<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>
<p class="MsoNormal"><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>
<p class="MsoNormal" style="margin-bottom:12.0pt">Lucia Greco<br>
Web Accessibility Evangelist <br>
IST - Architecture, Platforms, and Integration<br>
University of California, Berkeley<br>
(510) 289-6008 skype: lucia1-greco<br>
<a href="http://webaccess.berkeley.edu" target="_blank">http://webaccess.berkeley.edu</a><br>
Follow me on twitter @accessaces<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>
<p class="MsoNormal">On Tue, Feb 11, 2020 at 12:51 PM Sean Keegan <<a href="mailto:skeegan@ccctechcenter.org">skeegan@ccctechcenter.org</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal">Hi Carrie,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">> Just curious is any of you have used UserWay (<a href="http://userway.org" target="_blank">userway.org</a>)?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I am familiar with UserWay (and a few other accessibility "overlays") and am generally not a fan. If you were to offer this tool on top of a website that is already accessible, then that's fine as it does provide some unique options to
modify the website content that a person with a disability might find useful. That said, several of the "features" offered by the widget are already present in most modern web browsers. Additionally, if a person needs that accessibility support, it seems to
me that he/she would likely need that support on many of the web pages they use, not just on the site that provides the overlay.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">A problem that I see with such overlays is that you still have a website with accessibility problems. Sure, the overlay may mitigate some issues, but the problems still exist and need to be corrected. Putting on rose colored glasses may
make everything look rosy, but the accessibility problems exist and can still pose barriers. For instance, what happens when the college decides to stop paying for the remediation service portion? You now have those same accessibility issues that have been
kicked down the road. I know the UserWay widget itself is free, but it is also combined with the remediation service to address accessibility issues.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Also, I find that a lot of students, faculty, staff are using resources that are not necessarily part of the college's public facing website. There is a learning management system, library databases, Google Docs/Office 365 Online environments,
publisher content, etc. If an institution is pursuing an overlay solution, restricting it to just the public-facing website does not offer support to the web environments in which students, faculty, and staff may be utilizing on a daily basis.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If the intent is to fix the underlying web page for accessibility errors, then I see adding such an overlay is a "nice-to-have" and can offer site visitors the opportunity to customize their user experience. However, the concern I would
raise is that the commitment to fix the accessibility errors can diminish quickly with the adoption of an overlay as the perception becomes any problems have now magically disappeared.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Take care,<br>
Sean<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>
<p class="MsoNormal">_______________________________________________<br>
athen-list mailing list<br>
<a href="mailto:athen-list@mailman12.u.washington.edu" target="_blank">athen-list@mailman12.u.washington.edu</a><br>
<a href="http://mailman12.u.washington.edu/mailman/listinfo/athen-list" target="_blank">http://mailman12.u.washington.edu/mailman/listinfo/athen-list</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>