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...

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.

I would really love to know a bit more about your component library! I’m currently working on ours at @publico.bsky.social but I was curious how you guys manage everything :)

Yeah, that would be great! E.g. do you use Storybook?

And, if you do, how? :) I’m also curious about the workflow. There’s a big repo template and you use something like the use this template GitHub feature?

Oh I was thinking about doing the same! Well, I think I’ll steal a lot of your ideas guys! Thank you! 🫡

Reuters Graphics folks have some similar tooling that we used for starting templates, and they've made the scaffolding CLI tool public. It is a neat way to write templating configs that do whatever you need to, while keeping the main source of truth a GitHub repo. github.com/reuters-grap...

Yes!! Love all the work you all do and appreciate that it's public (I'm hoping to eventually get ours to be). I often joke that we're all just reinventing the same processes/templates in our own special way, but it is genuinely cool to see the different approaches.