Skip to content
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

Closed
jelbourn opened this issue Feb 27, 2016 · 3 comments · Fixed by #238
Closed

Build aria-live announcer service / component #106

jelbourn opened this issue Feb 27, 2016 · 3 comments · Fixed by #238
Labels
Accessibility This issue is related to accessibility (a11y) feature This issue represents a new feature or feature request rather than a bug or bug fix help wanted The team would appreciate a PR from the community to address this issue
Milestone

Comments

@jelbourn
Copy link
Member

No description provided.

@jelbourn jelbourn self-assigned this Feb 27, 2016
@jelbourn jelbourn added this to the before beta milestone Feb 27, 2016
@jelbourn jelbourn added feature This issue represents a new feature or feature request rather than a bug or bug fix Accessibility This issue is related to accessibility (a11y) toolkit labels Feb 27, 2016
@jelbourn jelbourn added the help wanted The team would appreciate a PR from the community to address this issue label Mar 9, 2016
@jelbourn jelbourn removed their assignment Mar 9, 2016
@devversion
Copy link
Member

How should that component look? Should it have the same functionality as in $mdAria for Material 1?

@jelbourn
Copy link
Member Author

@devversion not quite. The idea here is that you have either a component or a service that makes aria-live announcements. It would be used by things like md-toast. At this point I'm leaning towards a component like

<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:

  • JAWS (Windows) with IE11 / Edge / Chrome / Firefox
  • NVDA (Windows) with IE11 / Edge / Chrome / Firefox
  • VoiceOver (OSX) with Safari / Chrome
  • VoiceOver (iOS) with Safari
  • TalkBack (Android) with Chrome

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.

devversion added a commit to devversion/material2 that referenced this issue Mar 30, 2016
devversion added a commit to devversion/material2 that referenced this issue Mar 30, 2016
devversion added a commit to devversion/material2 that referenced this issue Mar 30, 2016
devversion added a commit to devversion/material2 that referenced this issue Apr 2, 2016
devversion added a commit to devversion/material2 that referenced this issue Apr 3, 2016
devversion added a commit to devversion/material2 that referenced this issue Apr 6, 2016
devversion added a commit to devversion/material2 that referenced this issue Apr 6, 2016
devversion added a commit to devversion/material2 that referenced this issue Apr 6, 2016
devversion added a commit to devversion/material2 that referenced this issue Apr 6, 2016
jelbourn pushed a commit that referenced this issue Apr 6, 2016
andrewseguin pushed a commit to andrewseguin/components that referenced this issue Oct 15, 2018
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 4, 2019
alexeagle pushed a commit to alexeagle/material2 that referenced this issue Nov 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Accessibility This issue is related to accessibility (a11y) feature This issue represents a new feature or feature request rather than a bug or bug fix help wanted The team would appreciate a PR from the community to address this issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants