Feature Request: Accordion keyboard support for accessibility #24566
laflannery
started this conversation in
Feature Request
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Prerequisites
What problem is your feature request going to solve? Please describe..
The keyboard support of the latest accordion component has introduced complexity that does not assist users, but rather makes the information within the accordions more difficult to access. The accordions do not follow typical keyboard support, they use the arrows keys to navigate through the elements instead of TAB to move to the next focusable item. There is an
aria-labelindicating these directions however it's on a non-focusable div so the user doesn't have a way of finding or accessing these instructions. Also, the user cannot move from within the accordion content to another accordion header using the keyboard at all, they must move backwards back up to the accordion header and use the arrow keys. This is a very non-typical pattern.Describe the solution you'd like.
The accordions should follow standard keyboard support patterns:
Describe alternatives you've considered.
I did research this pattern though I could not find instances where arrows keys where expected to navigate through multiple accordions in this manner.
Additional context
I was also having an issue where when NVDA was on, the visual focus indicator was not following my arrow keys as I navigated through the accordions. For example, I would tab to an accordion section, then hit the down arrow twice but my visual indicator did not move. However when I hit enter the 3rd FAQ would open. So the focus did properly move but the indicator was staying on the wrong accordion. Some sighted folks who user screen readers would be confused by this behavior. By using a more typical pattern, that may resolve this issue as well.
Agreement
All reactions