travis at travisroth.com
Tue Jun 15 09:37:17 PDT 2021
Certainly an interesting use case and not altogether accessibility friendly sounding.
With JAWS, possibly if the setting Screen Tracks Virtual Cursor is enabled, you may receive some onBlur events. I suspect it’d be unreliable at best. But if you’re up to experimenting I’d be interested in the results.
From: athen-list <athen-list-bounces at mailman12.u.washington.edu> On Behalf Of Vaibhav Saraf
Sent: Tuesday, June 15, 2021 11:23 AM
To: athen-list at mailman12.u.washington.edu
Hi List Members,
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.
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.
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?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the athen-list