←back to thread

117 points FragrantRiver | 1 comments | | HN request time: 0s | source
Show context
robin_reala ◴[] 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 #
CharlesW ◴[] No.46183323[source]
> It’s notable that accessibility isn’t mentioned once in this post, or, in fact, in the component’s documentation.

It's a red flag for sure. That said, there's nothing preventing toasts from being accessible: https://react-spectrum.adobe.com/react-aria/useToast.html

I think it would be accurate for GitHub to say, "GitHub no longer uses toasts because we didn't want to make the effort to make them accessible or usable."

replies(3): >>46184464 #>>46185290 #>>46198911 #
robin_reala ◴[] No.46185290[source]
Spectrum’s Toast docs don’t mention how they make Toasts accessible with screen magnifiers (more widely used than screen readers based on the last WebAIM surveys I saw), so I guess they didn’t consider them?
replies(1): >>46188324 #
1. MrJohz ◴[] No.46188324[source]
Everyone knows accessibility is just throwing aria tags at any element you see. The more aria tags there are, the more accessible it must be, right? /s