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

Improve Screen Reader support for BottomSheet component #914

Open
3 of 4 tasks
etoledom opened this issue Apr 22, 2019 · 7 comments
Open
3 of 4 tasks

Improve Screen Reader support for BottomSheet component #914

etoledom opened this issue Apr 22, 2019 · 7 comments
Labels
Accessibility HACK week HACK week June 2020 [Type] Enhancement Improves a current area of the editor

Comments

@etoledom
Copy link
Contributor

etoledom commented Apr 22, 2019

@etoledom
Copy link
Contributor Author

About There is no simple way to close the Bottom Sheet:

We were talking a few weeks ago about improving the Bottom Sheet experience regarding saving, canceling the action.

Currently the BottomSheets used for settings (Links and Images so far), can be dismissed by tapping outside of it or scroll it down. Both actions will automatically save the changes. This has some problems:

  • There is no way to cancel and not apply the changes made.
  • There is no easily visible way to save/close the bottom sheet.
  • There is not Close element that a Screen Reader can scan and give the proper feedback to the user that it can close/save/cancel any changes.

I hope to open the discussion on how to improve this.

cc @iamthomasbishop @SergioEstevao @hypest @koke

@iamthomasbishop
Copy link
Contributor

This has some problems:

In terms of an explicit "Close" button, I was on the fence about this, and decided to not include it unless absolutely necessary. However, in terms of screen readers, we should absolutely supply a mechanism to allow easy closing.

For some background, early iterations of the Sheets included a more "traditional" navigation bar at the top with actions, but after doing some competitive analysis and investigation, I decided against it for a couple reasons (tl;dr: consistency and guidelines):

  • We're essentially following the Material guidelines for Bottom Sheets (also inline with our in-progress Design System), which are defined as "a supplementary surface that provides quick access to content that complements the screen’s primary content", and typically do not include save/cancel actions. If you look at examples on iOS (Pages/Numbers/Keynote, Maps, Google Docs, etc), this same thing applies. Also Gutenberg core's Advanced Block Settings inspector works this way :)

  • We do supply a helpful "clear all settings" button, which isn't exactly a "cancel" but does allow an escape hatch of sorts

I'm open to suggestions and discussion, but this is some of the rationale. Personally, the thing I can most understand the case for is a "cancel" button of sorts, but I would advise against a save button on Sheets.

@etoledom
Copy link
Contributor Author

etoledom commented May 23, 2019

I did an investigation on those apps, and how their bottom sheets perform with VoiceOver.

This is what I found:

01
02

The Google Docs case was super interesting, it has a hidden "dismiss menu" element at the left of the first visible element. A VoiceOver user can access to it via swiping left. It also support Z gesture to dismiss. But it's not accessible via exploring the UI with the finger.

This is the only one of the bottom sheets that implement a dismissal option in this way, so I believe it's not a standard. I can't say what is the most preferred way of VoiceOver users to explore (swiping or exploring with the finger).

This is a video that shows this more clearly.

I hope this can help to guide us 👍

@iamthomasbishop
Copy link
Contributor

Thanks for the examples! I've always been a fan of Maps on iOS, but I do think their bottom sheets are a bit more advanced (and the logic that comes with it) than what we need. Up to this point (not saying we have to stick to it), my approach has been closest to the Google Docs example above, so I think that is our best starting point.

@designsimply
Copy link
Contributor

Currently the BottomSheets used for settings (Links and Images so far), can be dismissed by tapping outside of it or scroll it down. Both actions will automatically save the changes. This has some problems:

This also came up in 13.5 beta testing and I am noting the feedback to add to the discussion:

Adding link to image block- The popup does not have an ‘OK’ or a ‘Cancel’ button, instead a ‘Clear all settings’ button. I had to press the Back button after adding the link, fearing that the changes would be lost.

cc @iamthomasbishop @ahmadbaig1, ref: p5T066-135-p2#comment-3726

@SergioEstevao
Copy link
Contributor

@iamthomasbishop @etoledom circling back to this issue did we got to any agreement for how to making the closing of the bottom sheet more accessible?

@etoledom
Copy link
Contributor Author

etoledom commented May 6, 2020

I don't think we got an agreement. We did implement the Z gesture to close it with VoiceOver, but that's probably not enough. There's also the close without applying changes case that is not implemented, nor considered.

@hypest hypest added the HACK week HACK week June 2020 label Jun 7, 2020
@etoledom etoledom removed their assignment Jun 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accessibility HACK week HACK week June 2020 [Type] Enhancement Improves a current area of the editor
Projects
None yet
Development

No branches or pull requests

5 participants