E-mail List Archives
SC 2.1.2: Leave, but to where?
From: wolfgang.berndorfer
Date: Nov 29, 2020 12:08PM
- Next message: Birkir R. Gunnarsson: "Re: SC 2.1.2: Leave, but to where?"
- Previous message: Vaibhav Saraf: "Re: Edge Chromium vs Chrome - accessibility differences?"
- Next message in Thread: Birkir R. Gunnarsson: "Re: SC 2.1.2: Leave, but to where?"
- Previous message in Thread: None
- View all messages in this Thread
A project wants to include a navigational menubar. Searching for best
practices I found a WAI example:
<https://www.w3.org/TR/wai-aria-practices/examples/menubar/menubar-1/menubar
-1.html#ex_label>
https://www.w3.org/TR/wai-aria-practices/examples/menubar/menubar-1/menubar-
1.html#ex_label
The problem: I cannot leave the menu with arrow keys. Pressing arrow-right
holds me in the carousel of elements in the menubar.
By pressing tab, I can leave the navigational component, but I land
somewhere on the next focusable element. This way I bypass the content
between.
Is this a violation of SC 2.1.2?
How should we solve this issue? Give the first element behind the navigation
in the DOM a tabindex?
As a SR user I don't like menus for navigations at all, but this is because
I never found an example causing no problems. I tested the example above
with jaws 2020 Firefox, chrome, and edge. None supported all available
aria-attributes. And when the mouse occasionally was in the wrong place,
arrow-right did not move the focus but started spelling a word letter by
letter. And I use the mouse, when I work with magnification.
Thanks for ideas!
Wolfgang
- Next message: Birkir R. Gunnarsson: "Re: SC 2.1.2: Leave, but to where?"
- Previous message: Vaibhav Saraf: "Re: Edge Chromium vs Chrome - accessibility differences?"
- Next message in Thread: Birkir R. Gunnarsson: "Re: SC 2.1.2: Leave, but to where?"
- Previous message in Thread: None
- View all messages in this Thread