You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For better accessibility, the current design involves passing aria-role and aria-live through ariaProps. However, since aria-role already functions as aria-live, it could be beneficial to eliminate ariaProps and structure it to allow passing only ariaRole as a toast option.
Furthermore, referencing MDN reveals a potential double-speaking issue when assigning "alert" to aria-role and "assertive" to aria-live. To address this, it is recommended to set aria-live to "polite" for compatibility when aria-role is "status." Conversely, when aria-role is "alert," it is advisable not to assign a separate aria-live. Consider integrating these considerations into the code.
For better accessibility, the current design involves passing aria-role and aria-live through ariaProps. However, since aria-role already functions as aria-live, it could be beneficial to eliminate ariaProps and structure it to allow passing only ariaRole as a toast option.
Furthermore, referencing MDN reveals a potential double-speaking issue when assigning "alert" to aria-role and "assertive" to aria-live. To address this, it is recommended to set aria-live to "polite" for compatibility when aria-role is "status." Conversely, when aria-role is "alert," it is advisable not to assign a separate aria-live. Consider integrating these considerations into the code.
For more information on the aforementioned points, you can refer to ARIA live regions - Accessibility | MDN.
The text was updated successfully, but these errors were encountered: