With the changes in #3427657: Implement the new designs to the drawer it is now possible to open up all available submenus for one top level item in the drawer. the intended behavior is that only a single submenu is expanded at a time.
only 1 submenu item should be open at a time
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | vo-keyboard-focus-in-sync.mov | 10.17 MB | bronzehedwick |
| #6 | vo_cursor.mp4 | 339.99 KB | rkoller |
| submenu.jpg | 105.47 KB | rkoller |
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
compare changes, plain diff MR !218
Comments
Comment #2
rkollerComment #3
bronzehedwickComment #5
bronzehedwickComment #6
rkollerthank you for the quick fix, I've manually tested and and can confirm the behavior is as expected now. i've tested on the configuration menu and only one submenu remains open at a time.
i've only noticed one detail i am unsure if it is possible to be fixed. if you are having voiceover active then the voiceover cursor position remains at the position the submenu item was before it got expanded. so you have the voiceover cursor and the focus outline in two different places.
Comment #7
bronzehedwickGreat catch @rkoller! We can move the focus using JavaScript. I'll work on that now.
Comment #8
bronzehedwickComment #9
bronzehedwickHey @rkoller, I tested the VO/keyboard focus with the built-in macOS accessibility tools using Firefox, and wasn't able to replicate the issue.
vo-keyboard-focus-in-sync.mov
Is there a step to reproducing I'm missing?
Comment #10
ckrinaBased on Slack conversation postponing this until #3437401: Drawer closes when moving from the opening item to "popover" gets in. Let's see if this is still needed when that gets in.
Comment #11
ckrinaThis has been fixed in #3437401: Drawer closes when moving from the opening item to "popover". Closing as fixed per the work done here :)
Comment #12
rkoller@ckrina the problem with the focus and VO-cursor still persists. in safari they remain separated as long as no new keyboard input happens while in edge and firefox there is the short delay as described in the conversation on slack by @bronzehedwick. i still have to do some research (asking on the a11y slack and or safari folks on mastodon), should i open up a followup issue as soon as i get news or should i already open up a one outlining the problem in case someone else comes along knowing how to fix this?