keyboard accessibility issues in Stacked Bar

Hello.

I need to use the chart via the keyboard, but I have found two issues that I don't know how to solve.

1) Tooltip - Wrong tooltip is displayed when navigating with the keyboard between bars

tooltip.png

2) Bar with value "0" - When a bar has a value of 0, I would like it to be skipped. Currently there is a focus with an empty bar

value 0.png

Is it possible to solve these two problems in the current version?


2 Replies

NP Nishanthi Panner Selvam Syncfusion Team January 13, 2025 03:01 PM UTC

Hi Rafal,


Greetings from Syncfusion.


Query1: Tooltip - Wrong tooltip is displayed when navigating with the keyboard between bars


We have considered your reported scenario as bug and logged a defect report for this issue. This fix will be available in our weekly patch release which is scheduled to be rolled out on January 21, 2025. We appreciate your patience until then. You can keep track of the bug from the below feedback link.


Feedback: https://www.syncfusion.com/feedback/64626/the-tooltip-position-is-incorrect-when-navigating-through-the-chart-series-points


Query2:  Bar with value "0" - When a bar has a value of 0, I would like it to be skipped. Currently there is a focus with an empty bar


Currently, the default behavior of the chart during keyboard navigation does not skip data points where the y value is 0. When navigating through the chart using the keyboard, the focus will move through all data points, including those with a y value of 0.


Kindly revert us if you have any concerns.


Regards,

Nishanthi



NP Nishanthi Panner Selvam Syncfusion Team January 21, 2025 04:34 PM UTC

Hi Rafal,


Thank you for your patience


We have included the fix for the reported scenario in our weekly patch release (v 28.1.41) .


Please update the “ej2-angular-charts” package to the latest version in your application to resolve the reported issue. Please find the package from the below links.


Packagehttps://www.npmjs.com/package/@syncfusion/ej2-angular-charts


Root cause: The mouse x and mouse y is not proper while performing navigation action.

Fix: Now, we have updated the proper mouse x and y values in keyboard navigation.


Sample: Uasndqcd (forked) - StackBlitz


Please let us know if you need any further assistance.


Regards,

Nishanthi


Loader.
Up arrow icon