-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build aria-live announcer service / component #106
Comments
How should that component look? Should it have the same functionality as in |
@devversion not quite. The idea here is that you have either a component or a service that makes <md-a11y-announcer> Other components can then simply inject it from higher up in the component tree. I actually started writing one for material1 but never got around to finishing up the PR. You can find a lot more information in the issue discussion. Polymer also has something like this, the iron-a11y-announcer. My approach was based on theirs (though I had to do a decent amount of testing to figure out why that timeout was needed). The hardest part of this is actually testing the announcer on all of the different platforms:
Which is... tedious, so say the least. They can be wildly inconsistent. Unfortunately there not really a way (yet) to automate testing of what a screen-reader says. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
No description provided.
The text was updated successfully, but these errors were encountered: