<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:12.0pt;
font-family:"Times New Roman",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;}
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:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The Chrome and screen reader combination sometimes results in the user being unable to read what’s being typed in an edit field, or in finding an edit field.
The screen reader says one is focused there, but the browser does not agree.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Firefox and NVDA are more sluggish , but sometimes can read/find things the other combos cannot.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Also, though VFO has heavily marketed JAWS as the best thing for testing websites I don’t agree. JAWS can find items on a website that aren’t entirely accessible
by modern standards. It does a lot of hacking in to the browser to accomplish this, whereas if NVDA can’t read it, the web element probably has access issues.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">My favorite example of this are clickable elements which JAWS can find well enough to make you believe they are accessible. The problem is that JAWS doesn’t always
see them or let the user navigate to and activate them. JAWS also thinks an element is clickable when it isn’t at times.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">However if the situation isn’t a testing one and the website is only partly accessible, and the user has a choice, JAWS is better. So NVDA for testing, JAWS for
actualy dealing with sites that aren’t fully accessible.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">A comment on narrator: it has a developer mode which lets a sighted user actually know for sure what Narrator sees. It does this by blanking everything onscreen
that is not visible to narrator. To toggle this, press Caps lock plus Shift plus function key F12.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">With NVDA, sighted testers should enable the “focus highlight” add-on which shows where the voice is reading – what NVDA calls the navigator object.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">--Debee<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> athen-list [mailto:athen-list-bounces@mailman12.u.washington.edu]
<b>On Behalf Of </b>Robert Spangler<br>
<b>Sent:</b> Thursday, July 19, 2018 8:00 AM<br>
<b>To:</b> Access Technology Higher Education Network <athen-list@u.washington.edu><br>
<b>Subject:</b> Re: [Athen] Screen Reader/Browser Combination<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Yes you're right, I still run into issues with Chrome, especially with Google apps! Funny, isn't it? This is why I still keep Firefox around, for the instances where Chrome doesn't cut it. I just find Firefox to be more sluggish than
Chrome.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Thu, Jul 19, 2018 at 10:48 AM, Frederick, Kathryn A. <<a href="mailto:frederick.273@osu.edu" target="_blank">frederick.273@osu.edu</a>> wrote:<o:p></o:p></p>
<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" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">When we test websites for screen reader accessibility, we use NVDA and FireFox. Chrome presents some
browser accessibility challenges, especially when using NVDA. I agree, we should all keep Narrator in the back of our minds concerning screen reader access.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Katie Frederick, Digital Accessibility Specialist</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The Ohio State University</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> athen-list <<a href="mailto:athen-list-bounces@mailman12.u.washington.edu" target="_blank">athen-list-bounces@mailman12.u.washington.edu</a>>
<b>On Behalf Of </b>Robert Spangler<br>
<b>Sent:</b> Thursday, July 19, 2018 10:16 AM<br>
<b>To:</b> Access Technology Higher Education Network <<a href="mailto:athen-list@u.washington.edu" target="_blank">athen-list@u.washington.edu</a>><br>
<b>Subject:</b> Re: [Athen] Screen Reader/Browser Combination</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I'm no longer a student, but at one time I was - a blind student! At that time I was using Firefox with NVDA but nowadays I am using Chrome, since it has improved to a usable level.
I would never suggest Internet Explorer as most development work now is put towards Firefox/Chrome and improving their access with screen readers. Basically, you should be OK with JAWS/NVDA with Firefox and Chrome. I use Chrome as my main browser, with Firefox
as my secondary in case something doesn't work well with Chrome.<o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Chrome is much snappier in performance than Firefox, even since the Quantum update. This has been my experience, at least.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><br>
Robert<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">On Thu, Jul 19, 2018 at 9:30 AM, Castiglione, Deb A <<a href="mailto:deb.castiglione@cengage.com" target="_blank">deb.castiglione@cengage.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">I’ve asked previously about a screen reader/browser combination matrix, which does not appear to exist. It has been suggested that testing be performed
on the current and prior version of JAWS and <span style="color:black;background:white">
Internet Explorer, NVDA and Firefox, and VoiceOver on iOS. I’m also familiar with the WebAIM survey and results.
</span></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;color:black;background:white"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;color:black;background:white">I was curious, however, what the most popular combination is for students in higher education. And, are HE students using
Chrome? Any input you can provide is greatly appreciated.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;color:black;background:white"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;color:black;background:white">Thanks.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;color:black;background:white">Deb</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">What is “essential for some” is almost always “good for all” (Meyer, Rose, and Gordon, 2014).</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">Deb Castiglione, EdD, ATP</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">Director, Universal Design & Accessible Technologies</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">Learning Center of Excellence</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">Cengage</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">5191 Natorp Boulevard, Mason, OH 45040</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt">513-229-1654 / 513-309-6262</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt"><a href="mailto:deb.castiglione@cengage.com" target="_blank"><span style="color:#0563C1">deb.castiglione@cengage.com</span></a></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><br>
_______________________________________________<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="https://urldefense.proofpoint.com/v2/url?u=http-3A__mailman12.u.washington.edu_mailman_listinfo_athen-2Dlist&d=DwMFaQ&c=xoYdONxMEGxjdvKj5bOdEOV28uakaJ20R4TjadGGZBc&r=gcvya4Pqy0A2EsMRyTgo_3n3PIn53GqWAnSNzbIFuBs&m=Sth3YTYl7fMF_kRmFMwKxXmGZQPoluFG-VJxn1V3ELw&s=oHEQQsiIbMUepWi3cpj0waD-Qq3ihzvof41Mzv_BDro&e=" target="_blank">http://mailman12.u.washington.edu/mailman/listinfo/athen-list</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Robert Spangler<br>
Disability Services Technical Support Specialist<br>
<a href="mailto:rspangler1@udayton.edu" target="_blank">rspangler1@udayton.edu</a><br>
Office of Learning Resources (OLR) - RL 023<br>
Ryan C. Harris Learning & Teaching Center (LTC)<br>
University of Dayton | 300 College Park | Dayton, Ohio 45469-1302 <br>
Phone: 937-229-2066<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Fax: 937-229-3270<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Ohio Relay: 711 (available for individuals who are deaf or hard of hearing)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt">Web Site:
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__go.udayton.edu_learning&d=DwMFaQ&c=xoYdONxMEGxjdvKj5bOdEOV28uakaJ20R4TjadGGZBc&r=gcvya4Pqy0A2EsMRyTgo_3n3PIn53GqWAnSNzbIFuBs&m=Sth3YTYl7fMF_kRmFMwKxXmGZQPoluFG-VJxn1V3ELw&s=My5-xbC6W-Pyl8GK-YnPzVntK2l1BEEB-oaoj0_HOxU&e=" target="_blank">
http://go.udayton.edu/learning</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
athen-list mailing list<br>
<a href="mailto:athen-list@mailman12.u.washington.edu">athen-list@mailman12.u.washington.edu</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__mailman12.u.washington.edu_mailman_listinfo_athen-2Dlist&d=DwMFaQ&c=xoYdONxMEGxjdvKj5bOdEOV28uakaJ20R4TjadGGZBc&r=gcvya4Pqy0A2EsMRyTgo_3n3PIn53GqWAnSNzbIFuBs&m=Sth3YTYl7fMF_kRmFMwKxXmGZQPoluFG-VJxn1V3ELw&s=oHEQQsiIbMUepWi3cpj0waD-Qq3ihzvof41Mzv_BDro&e=" target="_blank">http://mailman12.u.washington.edu/mailman/listinfo/athen-list</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Robert Spangler<br>
Disability Services Technical Support Specialist<br>
<a href="mailto:rspangler1@udayton.edu" target="_blank">rspangler1@udayton.edu</a><br>
Office of Learning Resources (OLR) - RL 023<br>
Ryan C. Harris Learning & Teaching Center (LTC)<br>
University of Dayton | 300 College Park | Dayton, Ohio 45469-1302 <br>
Phone: 937-229-2066<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Fax: 937-229-3270<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Ohio Relay: 711 (available for individuals who are deaf or hard of hearing)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Web Site: <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__go.udayton.edu_learning&d=DwMFaQ&c=xoYdONxMEGxjdvKj5bOdEOV28uakaJ20R4TjadGGZBc&r=gcvya4Pqy0A2EsMRyTgo_3n3PIn53GqWAnSNzbIFuBs&m=Sth3YTYl7fMF_kRmFMwKxXmGZQPoluFG-VJxn1V3ELw&s=My5-xbC6W-Pyl8GK-YnPzVntK2l1BEEB-oaoj0_HOxU&e=" target="_blank">
http://go.udayton.edu/learning</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>