Skip to content
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.

Md-toast should be accessible #688

Closed
marcysutton opened this issue Nov 19, 2014 · 1 comment
Closed

Md-toast should be accessible #688

marcysutton opened this issue Nov 19, 2014 · 1 comment
Labels
a11y This issue is related to accessibility

Comments

@marcysutton
Copy link
Contributor

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:

  1. Focus should be sent to the toast or toast child action for keyboard access
  2. 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
  3. 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.

@marcysutton marcysutton added the a11y This issue is related to accessibility label Nov 19, 2014
@marcysutton
Copy link
Contributor Author

Oops! This is a duplicate of #349.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
a11y This issue is related to accessibility
Projects
None yet
Development

No branches or pull requests

1 participant