3 ms·
Timed toasts are bad for accessibility too, see WCAG 2.2: https://www.w3.org/TR/WCAG22/#enough-time https://www.w3.org/TR/WCAG22/#enough-time Basically, the us
by Cthulhu_ 2y ago
Timed toasts are bad for accessibility too, see WCAG 2.2: https://www.w3.org/TR/WCAG22/#enough-time https://www.w3.org/TR/WCAG22/#enough-time
Basically, the user should be able to configure toast messages; they should not autohide, or the time they hide should be adjustable, or they should be extendable within 20 seconds. TL;DR, self-hiding messages, dialogs, etc are not good for a11y.
That said, the toasts have a button where the user can undo the action taken, which is good for accessibility under criteria 2.5.2 and/or 3.3.4 / 3.3.6
- taneq 2y agoIt’s almost like we need a semantic level where the developer says “I want to send the use this small transient text message” and then a presentation level where a user can decide which method of presenting this information works best for them…
- katzinsky 2y agoEmail is nice. >But I don't want so many mails in my inbox Then write mail rules. It's really easy and personally I couldn't survive at work without them. That's a big part of why it's nice: You can choose how it works unlike practically everything else these days.
- JadeNB 2y agoThat ties the app to be usable only with network access (which is fine for, e.g., Youtube, but not for all apps!), and also includes a highly variable lag.