Rethinking Data Visualization for Rich Screen Reader Experiences (transcript)
Speaker 1 Imagine for a moment you’re looking at a really complex graph. Maybe one from a news article or a scientific paper, packed with information. Now stop. Imagine trying to get the meaning out of that same visualization if you couldn’t see it at all. What if those charts, the ones designed to make things clearer, were just, well, completely impenetrable? Just silence—or maybe garbled sounds?
Speaker 2 Yeah. Well, for millions of blind and visually impaired users navigating the web, that’s not really a thought experiment. It’s a daily frustration.
Speaker 1 A daily reality.
Speaker 2 Absolutely. Current web accessibility guidelines are a start, but they often fall short, especially for these dynamic data visualizations.
Speaker 1 How so?
Speaker 2 Well, they’re frequently invisible to screen readers. Or worse, you just hear something meaningless like “graphic, graphic, graphic.”
Speaker 1 Yeah, that doesn’t tell you much, does it? So what about the usual fixes, like simple alt text—that little description—or maybe linking to a raw data table? You’re saying those aren’t enough?
Speaker 2 They’re really inadequate. It’s a fundamental gap. Alt text just gives you a high-level summary, usually the author’s interpretation.
Speaker 1 Okay.
Speaker 2 You don’t get to interrogate the data yourself. You can’t zoom in on what you think is important.
Speaker 1 Right, you’re just given the conclusion.
Speaker 2 Exactly. And those raw data tables—yes, they have the data, but they’re incredibly tedious if you’re trying to spot trends or get a quick overview.
Speaker 1 Yeah, I can imagine. It’s like trying to find a needle in a haystack of numbers.
Speaker 2 Sort of, yeah. Like drinking from a fire hose just to find one specific value.
Speaker 1 So what does this really mean for someone relying on a screen reader day to day? That’s what we’re diving into today. Our mission in this deep dive is to unpack some really groundbreaking research. It’s a paper called Rich Screen Reader Experiences for Accessible Data Visualization, presented at the Eurographics Conference on Visualization in 2022.
Speaker 2 That sounds promising. Rich experiences.
Speaker 1 Exactly. It’s not just about tweaking things—it’s about fundamentally rethinking how screen readers can interact with and explore data visualizations. Proposing new ways to bridge that gap.
Speaker 2 To offer comparable experiences for everyone.
Speaker 1 Yes, truly comparable interactive experiences. And what I find compelling is that the team—from MIT, Carnegie Mellon, and University College London—included a blind researcher in their co-design process.
Speaker 2 That’s fantastic. Embedding lived experience right into the design.
Speaker 1 Right. So before we get into their solutions, let’s pin down those limitations of the older methods. You mentioned alt text.
Speaker 2 Yeah. The core issue with static alt text is it forces the user to accept the author’s viewpoint. There’s no chance to interpret the numbers for themselves.
Speaker 1 No agency, no chance to disagree—or find something the author missed.
Speaker 2 Precisely. And the raw data tables—we touched on it. But the cognitive load is immense for large datasets.
Speaker 1 Yeah. Like that participant said, “If I didn’t know what I was looking for, forget it.” It makes it really difficult to identify overall trends.
Speaker 2 And finding relationships between different points can be really tricky.
Speaker 1 So even the technical standards, like ARIA specs, don’t quite cut it.
Speaker 2 Even when they’re used, they often just result in the screen reader reading out long sequences of numbers without identifiable information. It’s just noise.
Speaker 1 Really not very helpful.
Speaker 2 It presents a low expressive ceiling, as the paper puts it. It doesn’t enable the rich exploration sighted users get.
Speaker 1 Okay, so the breakthrough from the research seems to be that screen reader users have the—
Speaker 2 Same fundamental goals. Exactly the same information-seeking goals. They want an overview first, then zoom and filter, and finally details on demand—just like sighted users.
Speaker 1 But the current tools don’t let them follow that sequence.
Speaker 2 They don’t. And that raises the big question: how do you design for that kind of dynamic, explorative interaction when the main interface is auditory and sequential?
Speaker 1 Yeah. How do you represent something inherently spatial and visual through sound?
Speaker 2 Well, the paper gives a powerful answer. They identify three key design dimensions through this iterative co-design process: structure, navigation, and description.
Speaker 1 Structure, navigation, description.
Speaker 2 Yes. Basically the three pillars for a truly rich screen reader experience with data visualization.
Speaker 1 Okay, let’s break those down. Pillar 1: structure.
Speaker 2 Structure is about organizing the chart’s elements for the screen reader—moving beyond simple linear lists or grid tables. The key idea is using tree structures.
Speaker 1 Tree structures, like branches?
Speaker 2 Exactly. Hierarchical branching lets users browse different components of a visualization and traverse them at different levels of detail.
Speaker 1 Like a roadmap—you can see the whole country, then zoom into a state, then a city.
Speaker 2 Precisely. It shifts the experience from hearing a flat list to exploring a multidimensional landscape.
Speaker 1 So nodes in the tree represent things like data, encodings, and annotations?
Speaker 2 Yes. Data values, encodings such as axes or legends, and annotations—the explanatory callouts that often get lost. Together, these provide both detail and narrative context.
Speaker 1 That’s powerful. And it gives flexibility too—users can choose which path to explore first.
Speaker 2 Exactly. Depending on the task, one branch might be more important than another. It gives real user control.
Speaker 1 Okay. Pillar 2: navigation.
Speaker 2 Navigation is about how you move through the structure. They identified three types:
- Structural navigation (step-by-step within the hierarchy),
- Spatial navigation (moving as if across coordinates, mimicking how sighted users scan a chart), and
- Targeted navigation (direct jumps to landmarks, like “go to maximum value” or “jump to 2020”).
Speaker 1 That’s really varied. And it reduces cognitive load by offering anchor points.
Speaker 2 Yes. Multiple methods let users pick the right approach for their task.
Speaker 1 Okay. Pillar 3: description.
Speaker 2 This is what the screen reader narrates. It covers content (focusing on meaning and trends, not just raw visual properties), composition (the order in which information is presented), and verbosity (how much detail to give). Crucially, users need control to adjust description levels depending on their goal.
Speaker 1 So personalization is key.
Speaker 2 Absolutely. It builds trust by letting users validate information themselves.
Speaker 1 And how did these ideas work in practice?
Speaker 2 The team ran a mixed-method study with 13 blind and visually impaired participants. They compared standard HTML tables with two new prototypes: one using structural and spatial navigation, and one that added targeted navigation.
Speaker 1 And?
Speaker 2 Tables were confirmed as tedious and limited. The prototypes, however, made interactions more enjoyable, supported efficient exploration, and helped participants actively build mental models of the data. Users could quickly get an overview, then zoom into details.
Speaker 1 So not just passive listening—active hypothesis testing.
Speaker 2 Exactly. Participants used the tools to test patterns and boundaries, actively constructing understanding. Navigation aids and landmarks were especially valuable for orientation.
Speaker 1 That’s huge.
Speaker 2 It is. It shows how thoughtful design can empower independence and insight.
Speaker 1 So, to synthesize: this research tackles visualization accessibility by focusing on structure, navigation, and description. Moving far beyond alt text or tables, it creates rich, interactive experiences for blind and visually impaired users.
Speaker 2 Right. And the implications are broad. It highlights how profoundly design choices impact understanding and interaction—for everyone.
Speaker 1 Which brings us to a final thought. For screen reader users, reading a visualization isn’t passive—it’s an active, embodied, and interactive experience, as the paper puts it.
Speaker 2 Yes.
Speaker 1 So what does that insight—that even looking at a chart can be seen as an interaction—tell us about designing all human–computer interaction, not just for accessibility? What if we thought of all information consumption as an active, embodied process? How might that change how we design websites, apps—everything?