You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey an application I'm working on has had an ergonomy and screenreading test, which included ag-charts.
The tester had some critique on the keyboard behavior. In version 9.3.2 it was working as he expected, in version 11.1.1 it does not.
Behavior
In version 11.1.1 the focus jumps directly into the chart, in version 9.3.2 the focus first jumps onto the chart and YAWS reads out" figure" and jumps into the chart when the user presses "enter".
When focus is inside the chart, the keyboard behavior differs. For version 11.1.1 the user must disable the virtual cursor with Insert + Z to access the series in chart otherwise it skips the whole element on cursor keys.
Version
11.1.1
Does the issue occur for a specific framework only?
All languages
Is the issue only observable on a specific browser?
All browsers
The text was updated successfully, but these errors were encountered:
j0yk1ll
changed the title
[Bug]: Focus behavior does not work correctly (with virtual cursor on)
[Bug]: Keyboard behavior does not work correctly in version 11.1.1 with YAWS (and virtual cursor on)
Feb 25, 2025
Link to reproducible scenario
None
Describe the bug
Hey an application I'm working on has had an ergonomy and screenreading test, which included ag-charts.
The tester had some critique on the keyboard behavior. In version 9.3.2 it was working as he expected, in version 11.1.1 it does not.
Behavior
In version 11.1.1 the focus jumps directly into the chart, in version 9.3.2 the focus first jumps onto the chart and YAWS reads out" figure" and jumps into the chart when the user presses "enter".
When focus is inside the chart, the keyboard behavior differs. For version 11.1.1 the user must disable the virtual cursor with
Insert + Z
to access the series in chart otherwise it skips the whole element on cursor keys.Version
11.1.1
Does the issue occur for a specific framework only?
All languages
Is the issue only observable on a specific browser?
All browsers
The text was updated successfully, but these errors were encountered: