select: does not work well with VoiceOver #10967

Activity

1. jelbourn

   added

   a11yThis issue is related to accessibilityThis issue is related to accessibility

   on Nov 3, 2017
2. Splaktar

   added

   - needs: Pull Request

   needs: investigationThe cause of this issue is not well understood and needs to be investigated by the team or communityThe cause of this issue is not well understood and needs to be investigated by the team or community

   P1: urgentUrgent issues that should be addressed in the next minor or patch release.Urgent issues that should be addressed in the next minor or patch release.

   on Dec 13, 2017
3. benjiallen commented on Dec 28, 2017

   

   benjiallen

   on Dec 28, 2017

   More actions

   • Component with issue
     • <md-select>
   • Overview of the Issues
     • Given I am using iOS VoiceOver, and an option within <md-select> has not been selected, when I try to "swipe right" to select the element, then focus jumps from the component to the label and makes it difficult to activate the control i.e., I need to “double tap” to get focus to the select and then “double tap” again to activate the control
     • Selects do not show up in the VoiceOver rotor. Given I select "form controls" from the VoiceOver rotor, when I try to "swipe down" to select an md-select then VoiceOver will skip the md-select
   • AngularJS Material Version
     • 1.1.5
   • Browsers and Operating System
     • iOS 11.2.1, Safari, VoiceOver
   • Reproduce the Error
     • Visit https://material.angularjs.org/latest/demo/select and interact with the select menu with VoiceOver

   👍React with 👍1Reacted by Michael Prentice
4. Splaktar

   added this to the 1.1.6 milestone on Jan 5, 2018
5. benjiallen commented on Jan 8, 2018

   

   benjiallen

   on Jan 8, 2018

   More actions

   Adding more issues with VoiceOver and md-select

   • What is the issue? *
     • In iOS VoiceOver, once an md-select with multiple selections is expanded, there is no way to collapse the list nor navigate to elements beyond the last option in the expanded option list. "Swiping right" past the last item in the md-select takes you outside of the viewport and into the browser chrome i.e., focus is moved to the back button
   • What is the expected behavior?
     • There should be a method for closing the select menu once the user has made a selection
     • After you reach the end of the list "swiping right" should move focus to the top of the list
   • CodePen (or steps to reproduce the issue): *
     • https://material.angularjs.org/latest/demo/select#option-groups
     • Details: Using iOS VoiceOver. Open the select menu for "topping", make a selection and then try to close the form control or move to the next form control on the page using the "swipe right" gesture.
   • AngularJS Versions: *
     • AngularJS Version: 1.5.5
     • AngularJS Material Version: 1.1.5
   • Additional Information:
     • Browser Type: * Safari and VoiceOver
     • Browser Version: * Latest that comes with iOS
     • OS: * iOS 11.2.1
     • Stack Traces: N/A

   👍React with 👍1Reacted by Michael Prentice
6. Splaktar

   modified the milestones: 1.1.6, 1.1.7 on Jan 17, 2018
7. Splaktar

   modified the milestones: 1.1.7, 1.1.8 on Jan 29, 2018
8. Splaktar

   modified the milestones: 1.1.8, 1.1.9 on Mar 16, 2018
9. Splaktar

   changed the title [-]Select does not work well with VoiceOver[/-] [+]select: does not work well with VoiceOver[/+] on Mar 27, 2018
10. Splaktar

    self-assigned this

    on Mar 27, 2018
11. 39 remaining items

    Load more
12. Splaktar

    added 3 commits that reference this issue on Jul 29, 2019

    fix(select): overhaul screen reader support

    ...

    This issue will close once commit 24c20d8 is merged into the 'master' branch.

    24c20d8

    fix(select): overhaul screen reader support

    ...

    This issue will close once commit 7073cb4 is merged into the 'master' branch.

    7073cb4

    fix(select): overhaul screen reader support

    ...

    This issue will close once commit 4694e08 is merged into the 'master' branch.

    4694e08
13. Splaktar

    added

    has: Pull RequestA PR has been created to address this issueA PR has been created to address this issue

    on Aug 5, 2019
14. Splaktar

    added a commit that references this issue on Aug 12, 2019

    fix(select): overhaul screen reader support

    ...

    This issue will close once commit 178a040 is merged into the 'master' branch.

    178a040
15. Splaktar

    modified the milestones: 1.1.20, 1.1.21 on Aug 15, 2019
16. Splaktar

    added a commit that references this issue on Sep 7, 2019

    fix(select): overhaul screen reader support

    ...

    This issue will close once commit 7584fe8 is merged into the 'master' branch.

    7584fe8
17. Splaktar

    modified the milestones: 1.1.21, 1.1.22 on Oct 22, 2019
18. Splaktar

    added 2 commits that reference this issue on Mar 6, 2020

    fix(select): overhaul screen reader support

    ...

    This issue will close once commit b10b7fe is merged into the 'master' branch.

    b10b7fe

    fix(select): overhaul screen reader support

    ...

    This issue will close once commit bb3f9f5 is merged into the 'master' branch.

    bb3f9f5
19. Splaktar

    closed this as completedin #11761on Mar 10, 2020
20. Splaktar

    added a commit that references this issue on Mar 10, 2020

    fix(select): overhaul screen reader support

    ...

    This issue will close once commit 928c71d is merged into the 'master' branch.

    928c71d
21. Splaktar

    added

    resolution: fixed

    on Mar 10, 2020