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

Keyboard navigation unexpectedly throws user to the other column in stacked column chart when setting some value to null #17733

Open
maksim-pushkin-team-wrike opened this issue Sep 15, 2022 · 6 comments

Comments

@maksim-pushkin-team-wrike
Copy link

maksim-pushkin-team-wrike commented Sep 15, 2022

Expected behaviour

When I have one of the values for chart set to null, I expect keyboard navigation to work in an expected way:
when press left/right arrow button it should lead focus to the other columns if there are such.
And when I press up/down arrow button it should lead focus to the other bars inside the same column if there are such

Actual behaviour

When I have a value in some column set to null, let's say, between the other not-null values and mean to navigate the column containing the null value by pressing up/down arrows, the focus gets thrown to the other columns, which is unexpected and also makes navigation a bit complicated.

Live demo with steps to reproduce

In this fiddle the first column (Arsenal) has null value.
https://jsfiddle.net/me9xab5r/4/

Product version

10.2.1

Affected browser(s)

probably, all

@pawellysy pawellysy added the a11y Accessibility related. label Sep 15, 2022
@maksim-pushkin-team-wrike
Copy link
Author

maksim-pushkin-team-wrike commented Oct 6, 2022

This bug is also actual for the more natural case like in this demo: https://www.highcharts.com/demo/bar-stacked,the focus can be thrown unexpectedly to the neighbour column while navigating through the middle column by left/right arrow keys

@oysteinmoseng
Copy link
Member

Thanks for reporting. This is a fairly general issue that applies to many chart types with the current keyboard navigation model. The logic should be rewritten to better handle cases like this.

A suboptimal workaround is to set seriesNavigation.mode to serialize, which will make it behave consistently, but only allow one dimensional navigation through each series: https://jsfiddle.net/dhp0nfj4/

Copy link

github-actions bot commented Apr 7, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!

@github-actions github-actions bot added the Status: Stale This issue hasn't had any activity for a while, and will be auto-closed if no further updates occur. label Apr 7, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 14, 2024
@kamil-musialowski
Copy link
Contributor

unstale, issue still present

@oysteinmoseng oysteinmoseng removed the Status: Stale This issue hasn't had any activity for a while, and will be auto-closed if no further updates occur. label May 8, 2024
@oysteinmoseng
Copy link
Member

We will investigate if we can provide a quick fix for this, or a workaround. The longer term (2024, early 2025) plan involves a rewrite of how Highcharts handles keyboard navigation in general.

@marvin19
Copy link
Contributor

Workaround: https://jsfiddle.net/maritavindedal/nhbfqe9o/
Created custom accessibility component to tweak keyboard navigation logic for stacked column chart. Included more null points than the original demo to make sure solution is flexible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants