Skip to content

VoiceOver doesn't read MatSelect options inside of a dialog for Safari/Firefox #20900

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
jelbourn opened this issue Oct 27, 2020 · 7 comments
Closed
Labels
Accessibility This issue is related to accessibility (a11y) area: material/select P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@jelbourn
Copy link
Member

To reproduce: Use the dev-app example for a mat-select inside of a dialog. #20695 fixed this for VoiceOver + Chrome, NVDA, and ChromeVox, but VoiceOver + Safari and Firefox seem to still have issues.

Related to #20694

@jelbourn jelbourn added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent Accessibility This issue is related to accessibility (a11y) area: material/select labels Oct 27, 2020
@rameshworsht
Copy link
Contributor

@jelbourn Has there been consideration to provide the CDK overlay user with the option to attach it to the parent node instead of the body of the page. We could fix this issue if we could attach the select or tooltip on the dialog component rather than to the end of the body at all times.

@jelbourn
Copy link
Member Author

That would cause the select panel to be clipped by the dialog.

@TQuinn33
Copy link

TQuinn33 commented Feb 5, 2021

The inconsistent behavior I submitted an issue for is occurring in Chrome, but this ticket is targeted at Safari/Firefox. I am also not sure if this ticket is addressing the same inconsistent behavior described in #21787, as I don't see any description of the specific behavior being addressed for this ticket.

@jelbourn
Copy link
Member Author

jelbourn commented Feb 5, 2021

@TQuinn33 I believe the issue is the same underlying root cause

zarend added a commit to zarend/components that referenced this issue Jan 23, 2023
@zarend
Copy link
Contributor

zarend commented Jan 23, 2023

Hello,

Thank you for participating this this issue. I can no longer reproduce, and I believe this issue has already been fixed.

Environment:

-Zach

@zarend zarend closed this as completed Jan 23, 2023
@zarend
Copy link
Contributor

zarend commented Jan 23, 2023

screenshots of above verification ^
Screenshot 2023-01-23 at 8 54 38 AM

Screenshot 2023-01-23 at 8 51 38 AM

@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 Feb 23, 2023
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) area: material/select 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

4 participants