Support inline link in toasts

[digitalsadhu]

Design specifies that links can be added to messages on the right hand side, just left of the close button.

[Skadefryd]

Should probably be very strict on that implementation? like not allowing a link if the thing is set up to auto-close.

[digitalsadhu]

There is a wider discussion to be had regarding accessibility and toasts. Normally (but perhaps not always), a toast is triggered when the user interacts with the page in some way. Our toast implementation means that the toast will appear at the bottom of the screen. This is fine so long as it is not interactive. That is to say that it doesn't have a link or a close button. As soon as it is interactive, for accessibility reasons, the toast needs to be located directly after the action that triggered it. Is this stated correctly @martin-storsletten ?

[martin-storsletten]

That's correct. And here are a few examples:

• Keyboard users must be able to Tab easily to the toast in order to interact with it. If it appears at the bottom, then there would be a lot of other interactive elements between the current focus and the toast. This would be even more problematic if the toast times out.
• Low vision users who rely on a lot of zoom may totally miss the toast altogether if the distance between current focus and toast is too great.
• Screen reader users may not know where to look for the toast. ARIA live ensures that it's read out loud, but if the toast is interactive then the user would need to navigate to it in order to interact with it. And the user would intuitively look for the response next to whatever element they interacted with that caused the toast to appear in the first place, not all the way at the bottom below the footer.