This repository was archived by the owner on Sep 5, 2024. It is now read-only.
This repository was archived by the owner on Sep 5, 2024. It is now read-only.
toast: announces "remove: " before "Alert", the toast, and toast content #10853
Open
Description
Actual Behavior:
- When an mdToast dialog pops up, it's announced twice by the screen reader. The transcript is:
[text in mdToast]
Alert
[text in mdToast]
Alert
- The text of the toast and alert only announced once.
CodePen (or steps to reproduce the issue): *
- See the demo on the Angular Material page here: https://material.angularjs.org/latest/demo/toast
- Tested using ChromeVox 53.0.2784.5 and we've had reports of this using JAWS as well.
AngularJS Versions: *
1.6.4-local+sha.617b36117
Additional Information:
- Chrome 59.0.3071.115
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
[-]mdToast announced twice by screen reader[/-][+]toast: announced twice by screen reader[/+]Splaktar commentedon Aug 10, 2018
I am only seeing the Toast announced once with Version 68.0.3440.87 (Official Build) beta (64-bit). However, I am hearing "removed: " as the first thing when a toast is displayed.
I am not hearing "remove: " announced with VoiceOver on macOS.
[-]toast: announced twice by screen reader[/-][+]toast: announces "remove" before the toast and toast message[/+]Splaktar commentedon Aug 10, 2018
This issue doesn't mention the version of AngularJS Material where this original issue was found. I am guessing 1.1.3 or 1.1.4?
Splaktar commentedon Aug 10, 2018
This looks like a Chromevox bug so I've opened https://bugs.chromium.org/p/chromium/issues/detail?id=873324 to track this issue.
1 remaining item
Splaktar commentedon Aug 24, 2018
Latest update from the Chrome team was to remove the use of
aria-relevant
or to change it fromaria-relevant="all"
toaria-relevant="additions text"
. However, doing this on macOS causes VoiceOver to not announce the toast after the first time it is opened. On Chromevox, it's worse, this causes toasts to not be announced at all.I've provided feedback to them and requested that they reopen the bug.