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
We have a webpage that hosts multiple types of charts.
Some of these charts require the heatmap module, so we've included the heatmap module script.
We also want the charts to be accessible and support keyboard navigation, so we included the accessibility module script.
A user should be able to use the 'Tab' key to move focus to the chart legend.
After adding the heatmap module script to the page, a user is unable to use the keyboard to navigate to the legend.
http://jsfiddle.net/sxb3u3k8/1
Tab into the chart.
Keep pressing tab, and notice that you'll never get to the legend.
Remove the heatmap.src.js script from the html, re-run the jsfiddle, and note that the bug goes away.
Chrome, IE, Firefox.
The text was updated successfully, but these errors were encountered:
Related with: #6511
Fixed #6606, no legend keyboard navigation when heatmap module loaded.
8f876e0
c68094b
oysteinmoseng
Successfully merging a pull request may close this issue.
We have a webpage that hosts multiple types of charts.
Some of these charts require the heatmap module, so we've included the heatmap module script.
We also want the charts to be accessible and support keyboard navigation, so we included the accessibility module script.
Expected behaviour
A user should be able to use the 'Tab' key to move focus to the chart legend.
Actual behaviour
After adding the heatmap module script to the page, a user is unable to use the keyboard to navigate to the legend.
Live demo with steps to reproduce
http://jsfiddle.net/sxb3u3k8/1
Tab into the chart.
Keep pressing tab, and notice that you'll never get to the legend.
Remove the heatmap.src.js script from the html, re-run the jsfiddle, and note that the bug goes away.
Affected browser(s)
Chrome, IE, Firefox.
The text was updated successfully, but these errors were encountered: