-
Notifications
You must be signed in to change notification settings - Fork 3.4k
toast: needs to support non-visual & keyboard users #349
Comments
@marcysutton is this still an issue...? If so, can you update with status and assign to @jelbourn if more work needed. |
This is still an issue. Toasts are not read out loud or keyboard accessible, at least on the demo page. |
I have reassigned it to @jelbourn, sorry for the delay! |
I think there are still a11y issues. I have an internal bug filed saying it's not possible to reach a toast action via accessible navigation before the toast disappears. EDITED: Another issue is that the default configurations (e.g. simple) do not wrap the action in the role="alert", so no actions are mentioned when the toast displays. |
Adding role="alert" the wrapping container provides a signifier that there is an action, so that helps a bit. It's still challenging to get to that button. It'd be great to be able to configure a keyboard shortcut via an additional parameter to the .action() method, such that the button's label could be generated so the reader could say "Press {shortcut} to {action}". |
move the role="alert" up a level - makes action button visible to screen readers add support for defining an actionKey to assign a hot key to an action - this enables Control-actionKey to activate the action add support for defining a dismissHint for screen readers add support for defining an actionHint for screen readers align custom toast demo with Material Design guidelines enhance custom toast demo to demonstrate an accessible custom toast Fixes #349
I posted PR #11424 to address these issues. I would appreciate review feedback. |
move the role="alert" up a level - makes action button visible to screen readers add support for defining an actionKey to assign a hot key to an action - this enables Control-actionKey to activate the action add support for defining a dismissHint for screen readers add support for defining an actionHint for screen readers align custom toast demo with Material Design guidelines enhance custom toast demo to demonstrate an accessible custom toast Fixes #349
…11424) move the role="alert" up a level - makes action button visible to screen readers add support for defining an actionKey to assign a hot key to an action - this enables Control-actionKey to activate the action add support for defining a dismissHint for screen readers add support for defining an actionHint for screen readers align custom toast demo with Material Design guidelines enhance custom toast demo to demonstrate an accessible custom toast Fixes #349
…ngular#11424) move the role="alert" up a level - makes action button visible to screen readers add support for defining an actionKey to assign a hot key to an action - this enables Control-actionKey to activate the action add support for defining a dismissHint for screen readers add support for defining an actionHint for screen readers align custom toast demo with Material Design guidelines enhance custom toast demo to demonstrate an accessible custom toast Fixes angular#349
…ngular#11424) move the role="alert" up a level - makes action button visible to screen readers add support for defining an actionKey to assign a hot key to an action - this enables Control-actionKey to activate the action add support for defining a dismissHint for screen readers add support for defining an actionHint for screen readers align custom toast demo with Material Design guidelines enhance custom toast demo to demonstrate an accessible custom toast Fixes angular#349
To be accessible,
material-toast
needs to be exposed to users who cannot see it appear. It must also be operable without a mouse and be discoverable with touch. There are a few things involved:display: none
). Offscreen CSS works fine for this.Escape stack tool idea from @ajoslin: https://gist.github.com/ajoslin/498892d942e4fc5c552c
The text was updated successfully, but these errors were encountered: