Defining ‘Toast’ Messages
Hey Adrian! I don’t know if you get it enough, but I wanted to share some feedback that your site is invaluable. As much as we reference you on my team, we could build a slackbot to just link anything new you publish. :) But yep this post is super in-depth and also clear. It’s very hard managing announcements, and I agree that often the first step is to ask yourself if the component you’re choosing is the right one. If the toast does make sense, then this is awesome detailed advice.
Ryan, thanks for the feedback. I generally only hear IRL if the stuff I post is useful, so it is nice to hear that some of it is.
Really pleased to see the UX side of toasts discussed here. Like all the patterns designed to be small and unobtrusive, there are complex access needs that often get overlooked. Thanks for digging into the detail!
Thank you for this very detailed and useful post (and all the others! I second Ryan). You mention a possible issue with WCAG criteria 1.3.2: Meaningful Sequence. I wonder how you would go about building a component with toast messages in it. A file uploader for instance. The toast would be in the middle of the DOM… Do you think that would fail the criterion? Testing didn’t seem to reveal any issues.
