Why GitHub’s War On Toasts Is Bad News For Accessibility

2 min read Original article ↗

It’s a cop out. Plain and simple. Both bizarre and shocking from a tech giant that should know better…

Attila Vágó

Press enter or click to view image in full size

Photo by Shamblen Studios on Unsplash

That I and every web accessibility professional has a problem with toasts, is an understatement. The numerous ways they fail users, how to get a better UX with toasts, I explained in great detail all the way back in 2020. Looks like GitHub, and with that Microsoft needed another 6 years to reach the same conclusion — toasts as a design and UX component within the technological standards we have today, are problematic. You’d think that a $3.51 trillion company’s obvious next step would be to roll its sleeves up and fix it. But no, GitHub made the cop out decision to just ban toasts altogether.

Press enter or click to view image in full size

GitHub’s Primer design system doesn’t like toasts anymore. Screenshot by author.

A quick recap on toasts, and the GitHub position

Toasts are those little notifications that show up on top, bottom, or side of the screen. Sometimes they can be triggered by a user action, other times they’re automated. Why they show up doesn’t matter one bit, though. It’s more about the where and when they disappear.