Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DOM order should follow keyboardNavigation.order #15876

Closed
oysteinmoseng opened this issue Jun 10, 2021 · 1 comment
Closed

DOM order should follow keyboardNavigation.order #15876

oysteinmoseng opened this issue Jun 10, 2021 · 1 comment
Assignees
Labels
a11y Accessibility related. Flow: Done status Type: Bug

Comments

@oysteinmoseng
Copy link
Member

Expected behaviour

Specific use case: If the legend is placed above the chart, setting keyboardNavigation.order will allow tab navigation order to change, but the DOM order should change as well. This impacts screen reader users navigating by virtual cursor.

Actual behaviour

The DOM order of proxy elements is fixed.

Live demo with steps to reproduce

https://jsfiddle.net/oysteinmoseng/nyv6as9f/
Navigating with virtual cursor, the order is data points first, then legend, then menu, while the Tab order is opposite.

@oysteinmoseng oysteinmoseng added Type: Bug a11y Accessibility related. labels Jun 10, 2021
@oysteinmoseng oysteinmoseng self-assigned this Jun 10, 2021
@circleci-mu circleci-mu added this to To do in Development-Flow Jun 10, 2021
@oysteinmoseng
Copy link
Member Author

This will be closed once PR #16124 is merged

Development-Flow automation moved this from To do to Done Aug 27, 2021
@circleci-mu circleci-mu added the Flow: Done status label Aug 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a11y Accessibility related. Flow: Done status Type: Bug
Projects
Development

No branches or pull requests

2 participants