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

Trigger + pop-up controls are not in DOM order for VoiceOver navigation #11106

Open
jasonzhang2022 opened this issue May 2, 2018 · 3 comments
Labels
Accessibility This issue is related to accessibility (a11y) area: material/autocomplete area: material/menu area: material/select G This is is related to a Google internal issue ios Issues specific to iOS P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@jasonzhang2022
Copy link

jasonzhang2022 commented May 2, 2018

Bug, feature request, or proposal:

bug

What is the expected behavior?

User can use VO-down arrow to navigate the drop down list
user can use VO-space to select one value from drop down list

What is the current behavior?

user can't reach the dropdown list using VO command

What are the steps to reproduce?

Providing a StackBlitz reproduction is the best way to share your issue.

StackBlitz starter: https://goo.gl/wwnhMV

What is the use-case or motivation for changing an existing behavior?

accessibility

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

angular material 2 as of 2018-05-03

Is there anything else we should know?

@josephperrott josephperrott added G This is is related to a Google internal issue Accessibility This issue is related to accessibility (a11y) labels May 2, 2018
@jelbourn
Copy link
Member

jelbourn commented May 3, 2018

We're working on revamping select and autocomplete this quarter to solve this. See #11083

@jelbourn jelbourn added the P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent label May 3, 2018
@Splaktar
Copy link
Member

If you manage to select an item in the popup menu, VO-space does select that item and close the popup menu.

However, the VO-Down Arrow combination does not allow entering the popup menu or changing options. Just the up/down arrow keys alone, do allow changing the options.

VO-Shift-Down Arrow should let you start interacting with the component (the popup menu in this case), but it does not currently do anything useful for mat-autocomplete.

When the mat-autocomplete is focused in VoiceOver, it announces that you are on a "Menu pop-up combobox" and suggests that you can type text or display a list of options using VO-Space. However, this does not apply since the menu opens/expands when the mat-autocomplete's input gets focus. VoiceOver does not give the use any indication of how to navigate the options and does not inform the user that the pop-up is expanded/open.

@jelbourn jelbourn changed the title autocomplete dropdown can't be navigated/selected by voiceover Autocomplete pop-up not in VoiceOver navigation order Nov 24, 2020
@jelbourn
Copy link
Member

jelbourn commented Nov 24, 2020

Revisited this today. This still stands in the sense that, while the dropdown is reachable by keyboard, it is not reachable through VoiceOver's navigation (not tab navigation). This is because the overlay is attached directly to the document body rather than being immediately after the text input in the DOM.

This affects select, autocomplete, menu, datepicker

@jelbourn jelbourn removed their assignment Nov 24, 2020
@jelbourn jelbourn changed the title Autocomplete pop-up not in VoiceOver navigation order Trigger + pop-up controls are not in DOM order for VoiceOver navigation Apr 20, 2021
@annieyw annieyw added the ios Issues specific to iOS label Apr 20, 2021
@zarend zarend self-assigned this Apr 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accessibility This issue is related to accessibility (a11y) area: material/autocomplete area: material/menu area: material/select G This is is related to a Google internal issue ios Issues specific to iOS 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

7 participants