Clarify required placement of Toast close button and consider allowing it within ToastContent

[emilmuller]

🙋 Documentation Request

The documentation for Toast isn't clear on whether the <Button slot="close"> must be a sibling of <ToastContent>. All examples show this pattern, but it's never explicitly stated as a requirement.

1. Documentation request:
   Please clarify in the docs if this structure is mandatory for accessibility and focus management?

2. API suggestion:
   If the structure is mandatory, I suggest re-evaluating this approach. The current design makes it difficult to implement common UI patterns, like placing the close button in a header next to the title, without using CSS workarounds (e.g., position: absolute).

🧢 Your Company/Team

No response

[LFDanLu]

For some background, it isn't required to place the CloseButton as a sibling of the ToastContent, rather it is just that screenreaders will automatically announce the ToastContent when the Toast appears which would then include the CloseButton, making it a bit verbose. We could perhaps add something in the docs to clarify this.

[emilmuller]

Thanks :)