vaibhav.s.acc at gmail.com
Tue Jun 15 09:22:57 PDT 2021
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