Accessibility

[ber4444]

Can we add some documentation on how to add accessibility to the chart?

Want to have full control of reading order, accessibility labels, etc

[Gowsky]

Hello @ber4444, I'm afraid that currently there is no other way for adding the accessibility other than editing the source code yourself.

[github-actions[bot]]

There hasn’t been any activity here for four weeks. If no activity occurs over the next week, this issue will be closed as stale.

[ber4444]

https://eevis.codes/blog/2023-07-24/more-accessible-graphs-with-jetpack-compose-part-1-adding-content/

This new article just came out on this exact topic

[ber4444]

Another recently released charting library does support accessibility: https://github.com/yml-org/YCharts#accessibility-support

[Gowsky]

Thanks @ber4444, we’ll look into adding accessibility to Vico in the future.

[karel-bouwkamp-db]

Hi, any updates on accessibility? Is it planned or still an open decision?
Starting from mid 2025, there will be a legal requirement in the EU for accessibility support in certain app categories.
Thanks :)

[Gowsky]

Hi @karel-bouwkamp-db, no, there are no updates on this topic currently. We're currently focused on key features and improvements for version 2. Once they're done, we can start looking into extra stuff like this. We're also open to contributions.

[williamdcole]

Can you provide a starting point as to where accessibility support could be added the library? Let's say we are only concerned about supporting bar charts.

[williamdcole]

How does that help me add accessibility to a Vico chart in an Android app?

[williamdcole]

My initial question was technical in nature. I would like to know if the code authors could provide any guidance as to how I could implement accessibility support in the Vico library.

[patrickmichalik]

Hello! Are you using Vico 1 or Vico 2, and are you using it with Jetpack Compose or with the view system?

[williamdcole]

Vico 2 with Compose

[Gowsky]

Hi! Accessibility is a broad topic, and it all depends on what you want to do exactly. Since you're using Vico 2 with Jetpack Compose, the starting point will be forking Vico and editing CartesianChartHost, where you can use Compose accessibility APIs. CartesianChart.markerTargets contains the data used by CartesianMarker, but it can be used for accessibility purposes as well. You can extend CartesianChart and its layers like ColumnCartesianLayer to store and expose more data you need.

If you have any specific questions, feel free to ask.

[Leedwon]

Hi folks, I opened a PR with initial accessibility support: #1069
It doesn’t solve all accessibility cases in the library, but it’s a starting point for further contributions while allowing visible data points to be announced by accessibility services.