[a11y] accessibility audit about visx HOT 3 CLOSED

Hi! I'm evaluating viz libraries for accessibility, and I'm surprised that there's little mention of this on a lib with 15k+ stars.

In response to "there haven't been any major issues reported for ~3 years" I can report that many interactive examples in the gallery¹ would likely not pass a WCAG 2.1 audit since the interactive functionality requires using some kind of pointer (mouse or tap).

Non-interactive vizzes are a different story since their a11y requirements range from alt text to exposing raw tabular data, depending on what the purpose of the viz is.

I wonder if a good start could be defining more explicit use cases for visx² and then documenting ways of making them accessible to all.

Is viz accessibility generally something that the visx team is planning of/interested in looking into? I'd be happy to help in some capacity, but since accessible data viz isn't straightforward, the initiative would definitely require maintainer involvement.

Let me know and have a good weekend ahead!

from visx.

I am interested in exactly this - and I will keep you posted on our progress here. We are following this guideline:

https://www.highcharts.com/blog/tutorials/10-guidelines-for-dataviz-accessibility/

from visx.

gonna close this as there haven't been any major issues reported for ~3 years.

generally I think vx isn't opinionated on accessibility and allows chart creators to make them accessible (aria-labels on svgs, tab-able tooltips, etc.)

from visx.