[GitHub] [echarts] kpierro914 commented on issue #18585: [Bug] ECharts claims to be accessible, but is not keyboard accessible

["kpierro914 (via GitHub)" <gi...@apache.org>]

kpierro914 commented on issue #18585:
URL: https://github.com/apache/echarts/issues/18585#issuecomment-1533679247

   The canvas element has support in all browsers and will render on screen but the canvas content will not be accessible to screen readers. With canvas the accessibility has to be added with JavaScript or ARIA on the canvas element itself or using internal fallback content placed within the opening and closing canvas tag. Canvas content is not part of the DOM except for the fallback content.
   
   SVG is a better choice for interactive content and custom controls than Canvas because SVG has internal accessibility semantics and ability to easily add interactivity with JavaScript.
   
   So, how exactly is this easily done? The other thread doesn’t really explain it. It looks like they added key listeners for certain keys and read things aloud to the user when those keys are pressed, but that’s not an all inclusive solution.


-- 
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: commits-unsubscribe@echarts.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@echarts.apache.org
For additional commands, e-mail: commits-help@echarts.apache.org