meganthecoder commented on issue #21022: URL: https://github.com/apache/echarts/issues/21022#issuecomment-3599323281
Sorry for the belated update. I don't have the time to contribute a fix for this after all, but I wanted to share my discoveries from looking into it: 1. The button role, tabindex, and aria attributes won't be enough to make the buttons keyboard accessible. It will also require adding a keyboard event listener to mimic the click event. (Since `<path>` isn't an element where that happens by default). 2. It's unclear to me whether a solution can be done completely in the echarts repo without zrender. The echarts team may want to discuss the desired architecture and where to add keyboard events and accessibility attributes, since it appears that this would be net-new functionality. Thank you! I look forward to this update, and please feel free to let me know if there are any questions. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
