Why GitHub's War on Toasts Is Bad News for Accessibility

It's a member-only story, so I can only read the first few paragraphs.

Toasts are indeed a problem because they can disappear without the user reading (or listening if on screen readers) to its feedback. So while I don't know what suggestions the author has, I find it hard to imagine it can be fixed in a way that you'd still call it a toast and not something else.

Of course, removing all toasts and making all feedback actionable until they disappear will instead create a lot of friction, it's not an easy UX problem.