Keyboard navigation in a custom menu and WCAG compliance

Hi listers,

I'm seeking guidance on the following case. Say, there's a custom UI 
component that works as menu which contains checkboxes and thus allows 
multiple selection. When the menu is expanded, I'd expect arrow keys to 
move between the menu items and tab key to move out of the menu to the 
next focusable item on the page. The actual behavior is that I cannot 
move between the items with arrows, but can use tab and shift+tab to 
move forward and backward between them and only when the first/last menu 
item is reached this way, I can tab/shift+tab once again to get out of 
the menu. In case it is important, pressing the esc key to collapse the 
menu does not work as well.

I'm not sure how to approach this when reporting this kind of issue. I 
don't think I can fail it under 2.1.1 Keyboard, since I can access all 
the menu items with keyboard (leaving aside that the interaction is 
horrible). I might address it under 2.4.3 Focus Order, but again - the 
menuitems can be navigated sequentially, though in an unusual way. 
Marking the issue as best practice with the highest severity level does 
not seem to be the way to go either.

Would be happy to have your thoughts on this matter.

Thank you!

-- 
Best,
Vlad
vkolp95@gmail.com

Received on Wednesday, 13 July 2022 13:24:59 UTC