-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
[BITV] Menus must be focus trapped #33743
Comments
Notifications nextcloud/notifications#1367 |
@PVince81 @skjnldsv focus trap all header menus like in nextcloud-libraries/nextcloud-vue#3489 or allow tabbing out and closing like in https://github.com/nextcloud/server/pull/35090/files#diff-ae814dad42ef834e47dfd1d175e798e67c703ede5105470317fafabec5c2f60f |
I added focus trap on nextcloud-libraries/nextcloud-vue#3489 too to help with your ongoing accessibility work :) |
Will go with focus trap version introduced in nextcloud-libraries/nextcloud-vue#3489 and will have to port over the existing menus as discussed with @PVince81
|
|
|
@michaelnissenbaum for the top-right menus we have 2 options
Which option would pass the accessibility audit?
|
My favourite is the version one - tabbing out and auto closing. The second version is OK as well, but then keep in mind that after you leaved the dialog using ESC key the keyboard focus must be returned back to the element which was used to open it and has to be clearly visible. And there's always a possibility that users don't know that they can use ESC to close the dialog. |
Thanks for your feedback @michaelnissenbaum! After discussions with @PVince81 we've chosen go with option 2 as we have already been focus trapping many other UI elements and this will keep it consistent across the entire interface |
Transferred "contacts menu" |
Transferred "Port notifications menu" |
Transferred "Port global search menu" |
Transferred "user menu" |
Tabbing out of a menu should close it.
Need to check all the menus in the top bar:
Also: probably the menu should close when Escape is hit while inside the menu ? (need to check if WCAG requires this)
The text was updated successfully, but these errors were encountered: