<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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">In short, the answer to your main question is “probably not.” – when screen readers are reading the text of a web page they aren’t actually focusing any of the content on the page. JAWS does have a setting, disabled by default, to have
the mouse follow the virtual cursor. If that were enabled you might get mouse events but such would be a bad thing to rely on for a number of reasons.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">My suggestion is to not automatically dismiss your notification; either on focus or otherwise. Doing so is problematic for reasons you have already discovered e.g. text disappearing in the middle of being read. If you need to draw user’s
attention to that text, you should focus the text and have a keyboard and screen reader accessible method for dismissing the notification, if desired.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> athen-list <athen-list-bounces@mailman12.u.washington.edu>
<b>On Behalf Of </b>Vaibhav Saraf<br>
<b>Sent:</b> Tuesday, June 15, 2021 12:23 PM<br>
<b>To:</b> athen-list@mailman12.u.washington.edu<br>
<b>Subject:</b> [Athen] JavaScript events related to Screen Reader Virtual Cursor<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi List Members,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Folks at my organization have decided to implement a toast notification for one of the applications. Though toasts are not considered good for accessibility, they have tried to incorporate most of the accessibility use-cases to it, and
advocated to restrict it only to cosmetic updates.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Now here is one interesting problem - When a user hovers or tabs into the notification, its timeout resets. Interestingly when a screen reader user reads the notification with arrow keys, the timeout does not reset and the toast disappears
while the user is reading it. And the user can also read the notification using some of the screen reader shortcuts as well.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Are there any events triggered by the virtual cursors of screen readers which can be handled to determine the presence of the user on the toast body and reset its timeout?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Vaibhav<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>