Toast messages, those brief notifications that pop up in a user interface, have been banned by GitHub's Design System due to their accessibility issues and poor user experience. The author argues that toast messages can be problematic for several reasons. They disappear quickly, making it easy to miss important information. They also obscure content behind them, causing frustration, and are often placed at the edges of the screen, where they can be hard to see. In response to GitHub's decision, the author examines various comments that defend toast messages. One commenter suggests that they are useful for long processes, like video exports, to allow users to continue working. The author counters that instead of a toast message, a clear notification method for completion can be used. Another commenter believes toast messages prevent users from spamming buttons, but the author argues that if users feel the need to spam, the underlying system has issues that need addressing. A significant point of contention arises from accessibility specialist Attila Vago, who believes toast messages can be improved for accessibility rather than banned. While the author acknowledges that it's possible to enhance toast messages, they stress that those improvements might fundamentally change their nature. The author concludes that true accessibility for all users isn’t achievable through toast messages, as they leave out individuals who may be distracted or have cognitive impairments.