<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;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;
mso-ligatures:standardcontextual;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@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="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Perusall support recorded me demoing how I could easily select text with google docs and Office online with the virtual cursor off but not in Perusall.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">They are going to contact the developers of JAWS and NVDA to find out why it works in both those web apps but not in theirs.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I really appreciate this company’s over the top commitment and I think we need to realize the screen readers are as much to blame. The read out loud feature is very nice for any student who doesn’t need a
screen reader but does need speech.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Another issue with browsers is that the tab key, which keyboard navigation relies on when in a web based app, also takes you in to the browser’s interface, where you can often get stuck. We should all be complaining
to google, Microsoft and Mozilla that they should use F6 and not tab so that tab lets you stay confined within the web page itself.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">--Debee<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-ligatures:none">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-ligatures:none"> athen-list <athen-list-bounces@mailman12.u.washington.edu>
<b>On Behalf Of </b>Deborah Armstrong via athen-list<br>
<b>Sent:</b> Thursday, April 10, 2025 8:54 AM<br>
<b>To:</b> 'Access Technology Higher Education Network' <athen-list@u.washington.edu><br>
<b>Subject:</b> [Athen] Perusall update<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">So the folks at Perusall are very supportive. Even their CTO contacted me about my accessibility issue. I am going to screen share with one of their developers in just a few minutes.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Perusall does automatically OCR any document the teacher embeds in its interface. But if it is a low-res image, such as a camera-phone photo of a page, the OCR is lousy. Hence professors really need to put
accessible content in to the app.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">For selecting text, the keyboard user turns on caret browsing mode and selects text with the shift and arrow keys. To annotate (comment) on it) enter is pressed and the user is now in an edit field, able to
easily type and correct text, just as if they were editing a discussion in Canvas.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Screen reader users need to be sure to toggle the JAWS virtual cursor or the NVDA browse mode off. Mac users need to use Chrome or Firefox because they say, Safari doesn’t have caret browsing. And I’d guess
VoiceOver users would also need to disable the quick key navigation.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Anyway, the problem I believe is really one with the screen readers, as they don’t support caret browsing. Once you turn off browse or virtual cursor mode, you get no feedback.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I’ve written to Freedom Scientific, saying this is a broader issue than just one web-based app. Caret browsing should be fully supported with feedback when that cursor is moved and focus changes.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The screen readers are stuck in this 20<sup>th</sup>-century paradigm of the static web page, where you occasionally use a Forms or Focus mode to fill in a form. But the reality now of web-based apps means
they need to fully support the browser as if it is an operating system.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">--Debee<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
</body>
</html>