[paragon-openedx.netlify.app] Feedback (on /components/toast/) Duplicating the "alert" role in the Toast component

[PKulkoRaccoonGang]

In the current implementation of the Toast component, we render this component inside the React portal. At the moment, the alert role is present both for the alert wrapper (the element with the toast-container class) and for the alert itself (the element with the pgn__toast class).

Should the alert role be specified only for the alert itself (the element with the pgn__toast class), or for the wrapper (the element with the toast-container class)? The main idea is to keep the element with the alert role in one instance.

[adamstankiewicz]

Interesting, I agree having the duplicate role="alert" doesn't seem correct. I wonder if the same could also be said for the aria-atomic (same value) and aria-live (competing values), per your screenshot above.

[PKulkoRaccoonGang]

Good catch! I also think this is unnecessary duplication. Removed in this commit: 90d695f