|Enrique Sánchez||Jan 29, 2020||keyboard-only||Overall, keyboard-only navigation was difficult and confusing. The nested blocks proved to be extremely hard to traverse.||- No matter how much I tried, I was unable to move focus to the 'Add Navigation Link' button, thus not being able to add a new first-level link.|
- I was able to add a submenu item by way of the option in the block toolbar, but I was also not able to reach the 'Add Navigation Link' button after the first submenu item was created.
- I found it easier to add new links after discovering the 'Block navigator'. This pattern feels more intuitive and easier to navigate. However, having the interaction split into two different places (on the modal I create a new navigation link, but then I have to go back to the block to edit the newly added link placeholder) was confusing.
- Having the nested links disappear when the subblock was not selected was disorienting. It made me believe that somehow my sublinks had been deleted.
|Enrique Sánchez||Jan 29, 2020||VoiceOver||Given that I also rely on a keyboard when using VoiceOver, I felt lost and confused while attempting to interact with the Navigation block and was not successful in creating a basic navigation structure beside the pre-populated option.|
|Joe Dolson||Jan 31, 2020||keyboard-only||It was very difficult to move between the main block and nested blocks via keyboard. Felt hard to predict what would happen with the next key press.|
There was no visible focus that gave a clear sense of place while exploring the blocks. Tabbing from an active submenu list item sent focus to the sidebar, when I had expected to move to the next top level menu item. The relationship between a top-menu list item and its children was confusing; it seemed like being in edit mode for the parent item automatically included being in edit mode for the children, but that didn't continue to other parent items.
|Joe Dolson||Feb 6, 2020||NVDA / Firefox||I found the navigation menu difficult to use from the keyboard. I was able to edit link text & add new links, but it took some trial and error to figure out how. The double-esc bug in Firefox/NVDA was particularly problematic navigating child blocks. Adding a new link defaulting to using the URL as link text was disorienting; it was difficult to realize what had happened. It would be easier if you could define the link text in a single step, rather than having to remove and replace the auto-placed text.||It was very difficult to understand what was going on in the blocks - what mode am I in? Am I in the navigation block, or in a menu item?|
|Grzegorz Ziółkowski||Feb 4, 2020||keyboard-only||Tested against Gutenberg 7.4. I echo the comments related to navigation between block and the dificulties to add another link, It needs more work to be usable for all type of users. It is possible to apply the color of the links from the parent block, but in practice it's hard to use.||- in the color pallete when you don't like the default colors offered, you need to open another popover and you can only use arrows keys to change the color. When I tab to use HEX section the popover closes.|
- I catch myself trying to change the preselected colors with arrow keys in the popover but it closes the popover
|Joe Dolson||Feb 6, 2020||n/a||Nav menu block auto-adds 'title' attribute value on links & prominently displays the title attribute field in the sidebar settings.||Title attributes are almost always an undesirable accessibility problem on navigation menu items. They should be at most an option that is available but not prominent; this change is a significant a11y regression. See #32218, #24766, #35374, etc.|