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

select(multiple): bad UX for exiting pop-up panel on iOS #11791

Open

Description

@Splaktar

Bug

CodePen and steps to reproduce the issue:

CodePen Demo which demonstrates the issue:

https://material.angularjs.org/latest/demo/select#option-groups

Detailed Reproduction Steps:

#10967 (comment)

What is the expected behavior?

It should be possible to exit/close the options pop-up panel in multiple mode after the user is done making selections via iOS VoiceOver.

What is the current behavior?

This issue with being difficult to exit a multiple selection select exists with Angular Material as well. The "Two finger scrub" to dismiss alerts/dialogs or go back a page seems to always go back a page when used with AngularJS/Angular Material Autocomplete and Select. I tried changing the md-select-menu-container to role="dialog" and adding "aria-haspopup="dialog" to the md-select, but that didn't help and the Z (two finger scrub) always went back to the previous page.

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

  • Touching the backdrop doesn't make much sense from a screen reader perspective like iOS VoiceOver.
  • The normal gesture to close the dialog/panel/alert navigates the browser back and loses the user's progress.
  • This is a common use case and pattern and the UX is very bad.

Which versions of AngularJS, Material, OS, and browsers are affected?

  • AngularJS: 1.7.8
  • AngularJS Material: 1.1.20
  • OS: iOS 12.x
  • Browsers: Chrome and Safari

Is there anything else we should know? Stack Traces, Screenshots, etc.

This was tested as part of PR #11761, but unfortunately, it was not fixed there.

This was originally reported in #10967 (comment), but it's being moved here as a separate issue as that one is going to be closed out due to fixing most of the other issues there.

Activity

  1. self-assigned this
    on Sep 7, 2019
  2. added this to the 1.1.22 milestone on Sep 7, 2019
  3. added
    a11yThis issue is related to accessibility
    os: iOSThis issue is specific to iOS
    P2: requiredIssues that must be fixed.
    g3: reportedThe issue was reported by an internal or external product team.
    needs: investigationThe cause of this issue is not well understood and needs to be investigated by the team or community
    on Sep 7, 2019
  4. modified the milestones: 1.1.22, 1.1.23 on Oct 22, 2019
  5. modified the milestones: 1.1.23, 1.2.0 on Jun 8, 2020
  6. modified the milestones: 1.2.0, 1.2.1 on Jul 29, 2020
  7. modified the milestones: 1.2.1, 1.2.2 on Sep 21, 2020
  8. added
    P3: importantImportant issues that really should be fixed when possible.
    and removed
    needs: investigationThe cause of this issue is not well understood and needs to be investigated by the team or community
    P2: requiredIssues that must be fixed.
    on Dec 15, 2020
  9. modified the milestones: 1.2.2, - Backlog on Dec 15, 2020
  10. removed their assignment
    on Dec 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3: importantImportant issues that really should be fixed when possible.a11yThis issue is related to accessibilitybrowser: Safarig3: reportedThe issue was reported by an internal or external product team.os: iOSThis issue is specific to iOStype: bugtype: gestures

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions