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

md-autocomplete: number of matching items and the selected one are not announced by the screen reader at the same time. #9603

Closed
wnwnzhou opened this issue Sep 14, 2016 · 0 comments
Assignees
Labels
a11y This issue is related to accessibility has: Pull Request A PR has been created to address this issue P0: critical Critical issues that must be addressed immediately. resolution: fixed
Milestone

Comments

@wnwnzhou
Copy link

Actual Behavior:

  • What is the issue? *
    In the case when the autocomplete dropdown shows a list of matching item, and a auto selected one in the list:
    Sometimes the screen reader only announces the '# of matches available', or only the auto selected item.
  • What is the expected behavior?
    Should announce both the # of matches item and the auto selected one together.
    I took a look into the code, and found that the message announce by the screen reader is put in tag which has aria-live. But by default aria-live only catches the changed content. I suggest to add aria-atomic="true" attribute to , so that all the messages in it can be announced together when the change is detected.

Angular Versions: *

  • Angular Version: 1.5.9
  • Angular Material Version: 1.1.1

Additional Information:

  • Browser Type: * Chrome
  • Browser Version: *
  • OS: *
  • Stack Traces:

Shortcut to create a new CodePen Demo.
Note: * indicates required information. Without this information, your issue may be auto-closed.

Do not modify the titles or questions. Simply add your responses to the ends of the questions.
Add more lines if needed.

@devversion devversion added a11y This issue is related to accessibility P5: nice to have These issues will not be fixed without community contributions. labels Sep 15, 2016
@devversion devversion self-assigned this Sep 15, 2016
@ThomasBurleson ThomasBurleson modified the milestone: - Backlog Sep 16, 2016
devversion added a commit to devversion/material that referenced this issue Oct 3, 2016
* Removes the static messages, which should be detected by the screenreaders

* Introduces a Screenreader Announcer service (as in Material 2 - angular/components#238)

* Service can be used for other components as well (e.g Toast, Tooltip)

Fixes angular#9603.
@devversion devversion added the has: Pull Request A PR has been created to address this issue label Oct 3, 2016
@ThomasBurleson ThomasBurleson added the P0: critical Critical issues that must be addressed immediately. label Oct 5, 2016
@ThomasBurleson ThomasBurleson modified the milestones: 1.1.2, - Backlog Oct 5, 2016
kara pushed a commit that referenced this issue Oct 12, 2016
* Removes the static messages, which should be detected by the screenreaders

* Introduces a Screenreader Announcer service (as in Material 2 - angular/components#238)

* Service can be used for other components as well (e.g Toast, Tooltip)

Fixes #9603.
@Splaktar Splaktar added resolution: fixed and removed P5: nice to have These issues will not be fixed without community contributions. labels Aug 10, 2018
@angular angular locked as resolved and limited conversation to collaborators Aug 10, 2018
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 has: Pull Request A PR has been created to address this issue P0: critical Critical issues that must be addressed immediately. resolution: fixed
Projects
None yet
Development

No branches or pull requests

4 participants