Øystein Moseng

Workaround: Set `mode` to `serialize` https://api.highcharts.com/highcharts/accessibility.keyboardNavigation.seriesNavigation.mode

@arunkumarcision Do you have a demo that reproduces the issue with `serialize` active? I can not reproduce it here: https://jsfiddle.net/oysteinmoseng/suda6qw9/ Edit: To clarify, `serialize` makes the up/down arrow keys work...

@arunkumarcision The option should be `accessibility: { keyboardNavigation: { seriesNavigation: { mode: 'serialize' } } }`, see the demo linked above - hope this helps as a workaround at least.

Hi @dmoxin, do you have an example with code - for example on CodePen or jsFiddle that reproduces the issue? Since there are so many possible Highcharts configurations it is...

Hi @dmoxin, sorry, I did not get notified about your post edit with the question! The advantage of getting it from codepen/jsFiddle is that we can see the options you...

@dmoxin Excellent, thank you for the demo. I am able to reproduce it on my side and will take a look shortly.

@dmoxin This no longer seems to be an issue with later Highcharts versions, so closing this for now. Feel free to comment to reopen if needed. See https://jsfiddle.net/o6c9svgd/

@pawelfus Many ways to optimize a11y descriptions, as you say we could keep track of whether or not changes have been made. Also with data grouping I would have thought...

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...

_Internal note:_ Agree @KacperMadej - we should add a listener to the change event on the media query, like in that example.