←back to thread

GitHub no longer uses Toasts

(primer.style)
123 points samsolomon | 1 comments | 08 Dec 25 19:58 UTC | HN request time: 0s | source
Show context
codingjoe ◴[08 Dec 25 20:47 UTC] No.46197454[source]▶
Finally, I hope that trend catches on. God knows how many messages are missed thanks to toasts.
replies(1): >>46197527 #
Groxx ◴[08 Dec 25 20:53 UTC] No.46197527[source]▶
>Toasts pose significant accessibility concerns and are not recommended for use.

yeah. OBVIOUSLY. good fucking riddance.

they wouldn't be half as bad if they always came with a notification center for seeing the ones you missed... but the other half is still incredibly bad and isn't worth using at all.

replies(1): >>46197773 #
Muromec ◴[08 Dec 25 21:18 UTC] No.46197773[source]▶
>yeah. OBVIOUSLY. good fucking riddance.

Are they really? Isn't it pretty normal "role status aria something something polite" thingy to announce feedback to user?

replies(2): >>46197971 #>>46198359 #
JoshTriplett ◴[08 Dec 25 21:36 UTC] No.46197971[source]▶
Accessibility is more than just screen readers. Toasts are also not accessible for folks with low vision, low peripheral vision, etc. And the time-based disappearance is unpleasant for many people, as one of many examples of "accessibility improvements are also often usability improvements".

A message that you have to explicitly dismiss, and that's stored in a "message history" somewhere, is much more accessible and usable.

replies(5): >>46198368 #>>46198369 #>>46198397 #>>46198475 #>>46200012 #
1. herpdyderp ◴[08 Dec 25 22:14 UTC] No.46198368[source]▶
Accessibility doesn't even need to be related to any disability or unusual user requirement. A user-hostile website can be inaccessible even to users with perfect visual and motor functions.