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
{{ message }}
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.
One of the more complex interactions, <md-toast>, needs to be made accessible. Because this is an interim element like <md-dialog>, it shares common characteristics and code, with the exception that md-toast goes away automatically after a timeout.
What needs to happen with toast:
Focus should be sent to the toast or toast child action for keyboard access
Toasts should be read aloud in a screen reader when they appear, either by using aria-live on a parent element or by sending focus to it
Focus should be sent back to triggering element after toast disappears/closes.
Sending focus to the element seems to make the most sense, since adding aria-live to the toast's parent element puts responsibility outside of the component itself. Adding tabindex="-1" will make the toast focusable by script.
The text was updated successfully, but these errors were encountered:
One of the more complex interactions,
<md-toast>
, needs to be made accessible. Because this is an interim element like<md-dialog>
, it shares common characteristics and code, with the exception that md-toast goes away automatically after a timeout.What needs to happen with toast:
aria-live
on a parent element or by sending focus to itSending focus to the element seems to make the most sense, since adding
aria-live
to the toast's parent element puts responsibility outside of the component itself. Addingtabindex="-1"
will make the toast focusable by script.The text was updated successfully, but these errors were encountered: