←back to thread

Building a Toast Component

(emilkowal.ski)
117 points FragrantRiver | 1 comments | 03 Dec 25 14:51 UTC | HN request time: 0.203s | source
Show context
robin_reala ◴[07 Dec 25 16:13 UTC] No.46182756[source]▶
Meanwhile, GitHub is removing Toasts from Primer, their design system.[1] They’re next to impossible to implement in a way that retains accessibility across all needs, and if you try to restrict their usage to places where accessibility doesn’t matter so much (simple ephemeral confirmations) people misuse them anyway.

It’s notable that accessibility isn’t mentioned once in this post, or, in fact, in the component’s documentation.

[1] https://primer.style/accessibility/toasts/

replies(5): >>46183323 #>>46184146 #>>46186685 #>>46187013 #>>46189172 #
toddmorey ◴[07 Dec 25 23:55 UTC] No.46186685[source]▶
When async notifications arrive from background processes… How is the user notified? (Not defending toasts, just curious how to do it better.)
replies(1): >>46186710 #
1. toddmorey ◴[07 Dec 25 23:58 UTC] No.46186710[source]▶
GitHub seems to suggest banners or “Also consider ways to notify the user in other communication channels such as email, notifications, or a push notification in the GitHub app.”

On MacOS… emails and push notifications create… toast messages