GitHub no longer uses Toasts

Finally, I hope that trend catches on. God knows how many messages are missed thanks to toasts.

>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.

>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?

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.

That depends on the size of the toast, appearance and frequency. We (an MSP) used a Windows toast notification[1] to encourage people initiate the Win10 > Win11 upgrade at their own convenient time (before it gets forced down on them) - and we got a pretty high uptake. The overall feedback from both the project team and users were good: the toast was unmissable, the text explanation was clear, and the big banner image was eye catching.

https://www.imab.dk/windows-10-toast-notification-script/

If it has all of:

a "big banner image", buttons that are required to interact or dismiss, doesn't go away on its own after only a couple seconds, and might(?) also exist in the notification center

I think it's pretty safe to label that "definitely not a toast". That's just a notification, or maybe a "non-modal alert". Toasts are distinct from those by being brief and ephemeral.