acl-services / acl-services/paprika

Keyboard Navigation issues with ListBox / ListBoxWithTags

Abierto
#956 0 comentarios 0 reacciones 0 asignados Ver en GitHub
A11y Editor's Choice
Lenguaje dominante
JavaScript
Estrellas
54
Forks
10
Merge medio
1 d 12 h
PR fusionados (30 d)
6

Descripción

# Bug Report

## Expected behavior
1. When using keyboard to navigate, it should be smooth and don't need to click arrow down on the first option twice if there is a filter.

2. In ListBoxWithTags, after choosing an option with the keyboard, the focus should go to the next available option in the list.

3. Pressing `space` to select an item from the list of options should not cause the list of options to scroll down.

4. Pressing `esc` to dismiss the popover list of options for a ListBox with a footer results in the selection being cleared.

5. When user enters a string in the filter input, then presses the `↓` key, the focus should move to the first item in the filtered list which can subsequently be selected with `space` or `enter`.

6. If the input for the search filter does not match any items, the screen reader should announce the "no results found" message.

7. As each item in the list of options is focused, the screen reader announces it as "1 of 1".

8. When the list of options is focused by the screen reader, it should announce how many items are selected.

## Current behavior
1. When using keyboard to navigate, if you have a Filter in the ListBox component. Using arrow keys to go down will get stuck on the first option for one key press. You have to press arrow key down twice in order for it to work.

2. In ListBoxWithTags, after choosing an option the focus gets lots.

3. When you press `space` to select an option, the list scrolls down too and the use can lose context.

4. If an item is selected for a ListBox with a footer and the user presses `esc` to dismiss the popover, the selection should remain as it was when the popover was opened.

5. Once there is content in the filter input, pressing `↓` does not move the focus away from the filter input (it is trapped).

6. If the input for the search filter does not match any items, the "no results found" message is displayed, but nothing is announced by the screen reader.

7. As each item in the list of options is focused, the screen reader should announce that is is: an item in a list, which index the current item is, and the total number of items in the list (ex. "2 of 10").

8. When the list of options is focused by the screen reader, it always announces "0 items selected" even when there _are_ selected items.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.