-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Unique viewers controls present on page analytics are not accessible with keyboard. #17442
Comments
Internal note: Color axis with data classes is not kbd accessible. Minimal demo: https://jsfiddle.net/oysteinmoseng/k63z1sbw/ |
@TorsteinHonsi As checked the issue still repro, can you please let me know the version in which the fix is deployed? |
Hi @ashish315, |
Hi @raf18seb Is it possible to have fix ported in the older versions such as high chart version 10.2.0 or below |
Hi @ashish315, unfortunately, this is not possible. |
Thanks for the info! |
User Impact
Unique viewers controls are not accessible by keyboard user depending only on keyboard will not be able to access these controls.
Expected behavior
Unique viewers controls present on page analytics should be accessible with keyboard also in scan mode also.
Actual behavior
Unique viewers controls present on page analytics dialog are not accessible with keyboard.
Observation-Unique viewers controls present on page analytics are not accessible in scan mode while navigating with narrator.
Test Environment:
OS: Windows 10 21H2 (build 19044.1766)
Browser: Microsoft Edge Version 103.0.1264.37 (Official build) (64-bit)
Demo URL: https://codepen.io/Harithalakshmi/pen/yLvZyqR
Steps to reproduce
1-Open the URL in edge browser
2-Turn on narrator
3.Navigate to preview
4-Navigate to "Chart context menu"
5-After Chart context menu there are viewer controls (0.00-10.00 11.00-100.00 101.00-150.00)
6-These controls are not accessible by keyboard with narrator these are not accessible in scan off/on mode.
Attachments
Unique.Viewers.0.1.Controls.Present.on.Page.Analytics.are.not.Accessible.with.Keyboard.mp4
The text was updated successfully, but these errors were encountered: