Post

🧵Okay let's do some BTS for Axios' elections #dataviz. 1/5: We used <canvas> for our big maps, which means we had to do some tricks with color hashes to get interactivity. What the reader sees vs. what the computer sees. Details on how it works: observablehq.com/@camargo/can...

Jacque Schrag@jacqueschrag.com

With so much election #dataviz to choose from, pretty pleased to have the map I worked on for Axios included. Thinking about sharing some behind-the-scenes look at what we did, so stay tuned for that.

2/🧵 #a11y with #dataviz is hard, and I won't claim that we got it 100% right. But I do think we made good choices: - Used aria or sr-only text for describing the graphics - All information available in accessible tables, with skip links to them - For bigger tables, we included a search option

3/🧵 Last year I built a component library in #svelte for Axios' visuals because nobody likes building the same things over and over again. We expanded it to include election #dataviz & it made it so much easier to have consistency across multiple codebases and implementations of these graphics.

Hi! Yes, we use Sveltekit + Storybook (which just shipped support for #svelte 5 yesterday). We build components in SK & use the package feature to build. Storybook for documentation. It gets published to a private NPM package we have included in our other Svelte templates.

0 reposts1 like

It’s gotten better! When I first started in early 2023, Svelte support was iffy but now that support is fully baked into Storybook. I will say I don’t think we’re taking full advantage of what SB offers & you could do it with SK alone, but I like the ease of use (now).