[privatemonkey]

Awesome. With a build step to do some data conversion I can see this being a more accessible option than rendering with canvas or SVG. Not that tables are that accessible but still, a better option. I think you could make that into the main selling point for your apporoach as it's an overlooked and difficult area of visualisation.

Apart from different chart types, examples on how to rig data/image export will make this even more usefull.

I currently work on accessibility guidelines for visualisations at a national bureau of statistics. This came just at the right time for me as I'm exploring options to improve accessibility beyond the capabilities of libraries like highcharts, vega, charts.js etc. Don't hesitate to contact me. I'm very interested in the possibilities in this approach.

[mwcampbell]

> Not that tables are that accessible

What do you find lacking in the accessibility of tables?

[privatemonkey]

The amount of data a table often contain presents an accessibility issue in itself. Simple tables with few datapoints is not a big issue though.

I haven't found a good way to highlight the data points in a table in such a way that it is easy to pick up by a screen reader. I would love a summary tag or similar to be part of the table in the same way we now have caption.

Anyway, I find the solution with tables way better than other html based chart solutions I've seen in regards to accessibility. They usually have a bunch of divs, spans and other tags that are really hard to follow.

Using tables seems so obvious now that I see it. I'm surprised I haven't seen it before. Good job!