Re: Keyboard navigation in a custom menu and WCAG compliance

Hi Vlad,

I am not sure I am fully addressing your question, but it *sounds* as if the inability to arrow-key around in your case may be something I see sometimes, components that are not block-level but inline:
https://developer.mozilla.org/en-US/docs/Web/HTML/Inline_elements#list_of_inline_elements

I see pages like (pseudo code):
SPAN RADIO1 /SPAN
SPAN RADIO2 /SPAN
and using a screen reader and keyboard navigating one cannot get to RADIO2. It is necessary to use TAB.

My fix is to make each item that needs individual focus, block level.

Hope that's relevant and helps.

Regards,

Alan
. . . . -   . . - - -
Alan Bristow ( he / him / il )
Web Developer / Développeur Web
Elections Canada / Élections Canada
alan.bristow@elections.ca


________________________________________
From: Vlad Kolpakov <vkolp95@gmail.com>
Sent: Wednesday, July 13, 2022 9:24 AM
To: w3c-wai-ig@w3.org
Subject: Keyboard navigation in a custom menu and WCAG compliance

Ce message a été envoyé par un expéditeur externe. Veuillez faire preuve de prudence et ne pas cliquer sur les liens ou ouvrir les pièces jointes à moins de reconnaître l'expéditeur et de savoir que le contenu est sûr.

This message was sent from an external sender. Please exercise caution and do not click links or open attachments unless you recognize the sender and know the content is safe.

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 14:24:15 UTC