Aria-practices: Multi-Select Listbox does not work

[JAWS-test]

Multi-Select Listbox: The following documented keys do not work:

Shift + Down Arrow: Moves focus to and selects the next option.
Shift + Up Arrow: Moves focus to and selects the previous option.
Control + Shift + Home: Selects from the focused option to the beginning of the list.
Control + Shift + End: Selects from the focused option to the end of the list.
Control + A: selects all options in the list. If all options are selected, unselects all options

Tested with Firefox, Chrome, IE 11 and Edge.

The multiple selection with Shift should also work with a pointing device like mouse.

[ZoeBijl]

Can confirm that these don’t work in Chrome or Safari on macOS.

Shift + Down Arrow and Shift + Up Arrow do move focus but don’t select anything. The options including Control only move focus to the first or last item. Control + A does nothing (on macOS).

[carmacleod]

@JAWS-test
Please re-test with the latest version of the rearrangeable multi-select listbox example.
Hopefully this issue can be closed?

[JAWS-test]

@carmacleod
I have tested it with Firefox, Edge and Chrome and it works fine (with and without screen reader). Thanks for fixing the problem

[sinabahram]

I'm sorry to reopen this, but are these examples expected to work at all with Jaws+Chrome. Given that's a rather popular combo, I'm confused why this example is virtually unusable with that combination and this issue is being closed.

The key mappings conflict with preexisting key combinations e.g. alt+upArrow collapses an expanded list box, alt+downArrow expands one, and alt+rightArrow moves forward in the browser. These keys have been true for decades, if I'm not mistaken, so I feel like having them be the default mappings is pretty problematic, no?

So, how do you move items between the lists without having to tab to the buttons each time. I hope we can all agree that's completely unacceptable as a default affordance, multiplying by 2, 3, or even 4, the number of keystrokes to perform an already lengthy operation.

The example, even though it's not in scope, has some anti-patterns that are also pretty problematic IMHO. Starting most of the options with the same words violates semantic prioritization and makes it super-irritating to use with a screen reader.

In my experience, developers treat these examples as golden, and while that usage may differ from the intended purpose, it never-the-less drastically affects the accessibility for AT users when developers assume these examples demonstrate the "right way" to do these things.

There's other items like a double label before the list, etc.

I'm always very confused on these examples when it's appropriate to bring up what issue and where, so maybe this isn't the right place. but I would appreciate knowing where the right place is to report the holistic issues rendering this example unusable IMHO.