Skip to content

Investigate "0 items selected" message in VoiceOver for MdSelect #1670

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

Closed
kara opened this issue Nov 1, 2016 · 6 comments
Closed

Investigate "0 items selected" message in VoiceOver for MdSelect #1670

kara opened this issue Nov 1, 2016 · 6 comments
Assignees
Labels
Accessibility This issue is related to accessibility (a11y) needs: discussion Further discussion with the team is needed before proceeding P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@kara
Copy link
Contributor

kara commented Nov 1, 2016

Currently in VoiceOver, the select will always read "0 items selected", even if aria-selected, aria-owns, aria-posinset, and aria-setsize are set. It appears to be this way in Material 1 as well. Needs investigation / fixing.

@kara kara added Accessibility This issue is related to accessibility (a11y) discussion labels Nov 1, 2016
@kara kara self-assigned this Nov 1, 2016
@HumanMedia
Copy link

+1
We really need this fixed as well. Trying to do a site for a major organization for disabled. This is a big problem for us.

@jelbourn jelbourn added the P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent label Jun 6, 2017
@jelbourn jelbourn changed the title Investigate "0 items selected" message in VoiceOver Investigate "0 items selected" message in VoiceOver for MdSelect Jun 6, 2017
@naomiblack naomiblack assigned jelbourn and mmalerba and unassigned kara Oct 5, 2017
@naomiblack
Copy link
Contributor

We think this is also related to an issue we're seeing in aXe testing for md-select with child options.

@naomiblack
Copy link
Contributor

possibly connected to #6382

@jelbourn jelbourn assigned devversion and unassigned jelbourn and mmalerba Jan 9, 2018
@devversion
Copy link
Member

devversion commented Jan 17, 2018

This issue seems to be more related to the general accessibility approach of the select. Since the select options are displayed dynamically outside of the <mat-select> element, the options won't be found by screenreaders if the panel is closed.

This means that the aria-selected option can't be found, and there will be always 0 items selected.

I think that it would be better to keep the list options permanently in the DOM, and also inside of the <mat-select> element.

On VoiceOver (even with aria-owns) the active option doesn't seem to be announced either (when using the arrow keys). Meaning that the select isn't really usable with VoiceOver.

@jelbourn
Copy link
Member

Tracking via #11083

@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 8, 2019
@mmalerba mmalerba added the needs: discussion Further discussion with the team is needed before proceeding label Mar 3, 2020
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) needs: discussion Further discussion with the team is needed before proceeding P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

No branches or pull requests

6 participants