The Future of Accessible Charts

(originally published on the Benetech DIAGRAM Center website, as part of their Office of Special Education Programs (OSEP) grant report)

by Doug Schepers, Fizz Studio, on behalf of the Benetech DIAGRAM Center. 8-September-2020.

One part of our remit was to investigate the viability of the ChartML format proposed in 2012 by Ed Summers and Julianna Langston of the SAS Institute. ChartML was intended as a neutral XML source format for representing data visualizations, to be transformed into suitable formats for visual, tactile, or sonification display.

The technology landscape has shifted from the time of that proposal, particularly in Web technology. There has been a shift away from domain-specific XML formats toward markup attribute-based semantics decoration of HTML and SVG, such as author-defined Dataset attributes or the Accessible Rich Internet Applications (WAI-ARIA) attributes, enhanced by script-based interaction.

Scalable Vector Graphics (SVG) has emerged as the graphics format of choice for data visualizations on the Web, and its markup metadata capabilities make it suitable as the source for other non-visual representations, including haptics and sonification. The native capabilities of the Web have also increased, introducing APIs both for haptics (the Vibration API) and sonification (the Web Audio API).

SVG was also enhanced to be more accessible to screen readers, detailed in the W3C WAI-ARIA Graphics Module and Graphics Accessibility API Mappings specifications.

These increased capabilities, as well as pressure from regulation, have led to a recent proliferation of accessible data visualizations in several major software packages. There is rapid iteration in the commercial and open-source product side of accessibility for charts, with many different approaches. In the coming years, this may culminate in shared common practices, and even in a universal standard for interaction and the interpretation of data visualizations within a standards body like W3C.

In addition, there is activity among W3C’s participants that may lead to more detailed guidelines for data visualizations, as distinct from the generic “complex image” guidelines, within the W3C Web Content Accessibility Guidelines (WCAG), which serve as the basis for regulation and legislation such as the US Section 508 directive. This has the potential to become a virtual cycle, where innovation in the market leads to standardization, which leads to widespread legal requirements, which in turn rewards technical and user experience innovation, all benefiting not just people with disabilities, but all consumers of data visualizations.

The DIAGRAM Center has fostered this progress in accessible data visualizations in three ways: by convening leading accessible charting developers, projects, and companies in discussions toward standards; by fostering community collarboration and development in our code sprints; and by disseminating this information to educators, parents, publishers, and software professionals through our reports, code repositories, and other publications. One recent success story from our code sprints was the creation of a new open-source software project called SparkBraille, which enables the easy creation of interactive tactile line and bar charts through a common refreshable braille display, right from the Web, with no special hardware or software required; this project was started and completed from scratch in the 3 days of our 2020 code sprint, and the developers continued to refine it after the event.

It is clear that the nature of digital accessibility of charts lies in the future of Web technology, Web standards, and Web applications. While not all the details are yet obvious, the renewed emphasis on digital content being “born accessible” has shifted, and will continue to shift, the market for data visualizations.

Why Accessibility is at the Heart of Data Visualization

To make data viz more accessible, we first need to understand assistive technology

Originally published by invitation on Nightingale, the Journal of the Data Visualization Society, on May 21, 2020, for Global Accessibility Awareness Day.

When I tell people I make data visualizations for blind people, the response is almost inevitably a quick pause while the gears of their mind start spinning wildly, then “How does that work?”

I’m not going to tell you how I do it. (At least, not in this article.) But I will tell you how I think about it, and suggest how you can too. Many people love data visualization because it makes data and other complex information accessible. But there are many people for whom data viz doesn’t make things accessible, and it’s not because they don’t understand data.

For example, data viz has played a critical role in educating people about COVID-19. But have you wondered how blind people are getting detailed information about the pandemic, given that so much of it is in chart or infographic form? The answer, for the most part, is that people with visual impairments are simply not afforded access to that critical data. To understand how we can—and must—change that, we first need to understand assistive technology.

Assistive Technology

Assistive Technology, or AT, is pretty much what it sounds like: technology that helps people overcome a constraint in how they interact with the world. In the case of people with a visual disability, that often means using a screen reader. A screen reader is software that literally reads text from the screen, a bit like an interactive audio book where the user can change the pace, skip passages, find text, or jump to sections or links they’re interested in. It also describes the structure of the text, like headings or tables or lists. But the caveat is that it only reads text, so if there’s something on the screen that’s not text, it’s hidden from them. Some non-text things have built-in descriptions, like form fields or buttons or links, which are announced along with their text labels. So images need text descriptions, called alt text, and complex images like charts need effective text descriptions to be useful to a screen reader.

Blind person using a screen reader
A blind screen reader user at work (photo credit: U.S. Air Force photo/Nan Wylie)

Or course, visual disabilities aren’t the only ones to consider, but for a primarily visual medium like data visualization, blindness is the obvious design constraint. Not everyone who has a visual disability uses a screen reader, and not everyone who uses a screen reader has a visual disability. And fortunately, text (which includes numbers) is a remarkably robust and transformable container for meaning, and works well with many types of AT. So providing a text equivalent is usually a great starting point.

The dirty little secret of accessibility is that there’s no single correct way to make your content accessible, and no one-size-fits-all solution … and this also applies to make your charts, graphs, and diagrams accessible. You need to consider your audience, and what you’re trying to convey, and decide how you want to convey the information to them.

The good news is that this is business as usual for someone skilled in data visualization. You don’t just take every dataset and render it as a bar chart, and call it a day. You think about the message you’re trying to send, and you pick the correct chart type, the right subset of the data, the correct framing, the clearest symbols, and the pithiest prose to craft your message. You adapt, remix, and innovate.

What I do, and what I’m asking you to do, is to bring the same craft of data design to accessibility as you do to visual representation. True accessibility means telling your data story to everyone.

When I work on making an accessible dataviz, here are some principles I focus on.

Value your reader’s time and attention

Use alt text to provide a one-sentence summary of the chart. One of the benefits of a dataviz is that it can convey a complex idea with a small investment of effort on behalf of the reader. If the fastest, best way to provide information were to use a data table, then you wouldn’t have used a chart. Please don’t make your readers walk through each cell of a table to get the gist of what you’re saying.

There’s enormous cognitive load in consuming large amounts of data. If at all possible, provide a textual summary of the chart in alt text, so the reader can decide if they want to drill in. Make it about the length of a text message, no longer. Write them a poem, not a novel.

Give all your reader access to all the data

While you don’t want to force users to slog through a data table, you don’t want to hide information from them. They may want to verify your conclusions, or might want to look at some relationship you don’t mention in your summary; for example, your article might specifically be about the COVID-19 infection rates in New York compared to other states, but they want to look at the numbers for their own state. If you’re showing it to some of your audience, don’t hide it from others.

A great way to do this is to include an alternative data table (often visually hidden but available to a screen reader) or a link to a CSV file that they can download and read in the app of their choice. As a side note, providing access to the raw data is generally a best practice so everyone can benefit from it.

Design equivalent experiences for all your readers

Even though blindness is an obvious constraint in data viz, it’s not the only disability to consider. We need to provide affordances for all of our users, on all of their devices. In general, don’t rely on only a single way to convey an idea. Add redundant representations for critical messages. Here are a few examples.

If you’re using color, think of how you can convey the same distinctions to people with colorblindness. Do you change the thickness of a line, or use patterns as well as color, or limit your palette to eliminate possible confusion? These are decisions you need to make on a case-by-case basis.

If you’re using visual media, consider how blind people can consume your content. That might be structuring your SVG markup to allow users to tab through each data point, or it might be providing an alternative data table. Or it might be using sonification. Sonification is the representation of data as nonverbal sounds, like a Geiger counter or EKG; you can see and hear an example of sonification on the Accessible Pandemic Data Bulletin, one of the few sources that blind users can find partial data about the spread of COVID-19.

If you’re offering only data tables as a fallback, think of how people with low vision, like fully sighted people, benefit more from clear, high-contrast, low-noise visualizations.

If you’re using animation, factor in people with epilepsy, ADHD, or cognitive disabilities, and give the user control of the animation.

If you’re using metaphors and symbols, consider how people with cognitive disabilities will interpret your information.

If you’re using sound, such as sonification or spoken aspects, think of the deaf.

Don’t rely on a single signal for your most important message. Repetition is the key to mastery, and the easiest way to ensure that you’ve made your point.

Data Visualization IS Assistive Technology

You might be thinking that this isn’t relevant to what you do. Your talent is in representing complex ideas visually, and isn’t that incompatible with accessibility? The simple fact is that data visualization is assistive technology. It’s cognitive assistive technology. Our amped-up monkey brains aren’t good at seeing patterns in numbers, but they’re great at discerning patterns in topological space. So we map numbers to colors, location, size, and other visual symbols, and suddenly we can understand trends and relationships.

As an illustration, here’s the same data as a spreadsheet and as a line chart. Which one more clearly shows the fastest rate of population growth?

Spreadsheet of population numbers for 4 most populous countries, with lots of numbers
Line chart of population numbers for 4 most populous countries, with the highest point for China but steepest line for India

It just so happens that this visual mapping doesn’t work for people who can’t see. So, think of different mappings to make those trends and relationships explicit to people who need it, as another constraint in your user-centered design process.

Uncharted Territory

If I could, I’d just hand you a set of instructions, and say, “Follow these steps, and your data visualizations will be accessible!”

But that list of instructions doesn’t exist. You are going to help write it.

There are numerous mechanical techniques that you can use, from structured markup to color-contrast checkers. And there are different media you can apply, from text to sonification to animation to tactile feedback. There are general authoring principles in the W3C’s Web Content Accessibility Guidelines (WCAG), though precious little specifically about dataviz, and there are good articles you can read on applying those standards to data visualizations. And there are legal reasons to make sure you check those boxes. These are tools, but they aren’t the solution.

You can follow all the rules, and still make data visualizations that aren’t accessible and that don’t inform your reader. As a craftsperson your goal should not be the worst content you can get away with, it should be the best experience you can build.

Don’t look at this as a requirement, an obligation, another checkbox to tick off. Look at accessibility as an opportunity to hone your skills, to move beyond the ordinary, and to provide an intentional experience for your users.

Some of the most effective, emotive, and affecting data visualizations I’ve experienced have blended two or more sensory techniques together to make a rich data representation that stays with me, that motivates me, that means something to me. That’s a high bar to aim for, but even if your experiment doesn’t reach that mark, you’ll be providing a better experience for a larger audience. Don’t be afraid to innovate.

We are at just the beginning of accessible data visualization. Join the conversation with me and others in the Data Visualization Society, and let’s aim for that high bar together.

About the author: Doug Schepers (@shepazu) is the founder and director of Fizz Studio, an accessible data visualization startup in Chapel Hill, NC, USA. Fizz Studio creates hand-crafted accessible diagrams and a next-generation accessible charting platform. Prior to founding Fizz Studio, Doug was a project manager at W3C, where he developed standards and prototypes and launched the developer relations program. He believes in positive social change through building communities and interoperable open technology.

DIAGRAM Center Report 2019

Benetech just published their Third Annual DIAGRAM Report. This is a resource aimed at providing resources on digital accessibility for educators and parents of children with disabilities, largely in the K-12 age range.

I was pleased to contribute the chapter on Accessible Data Visualizations. This was an interesting challenge for me, because I normally write for a highly technical professional web development audience, while this audience is broader and more focused on the pragmatics of education, sometimes using low-cost and low-tech solutions.

Volunteering at Benetech

I’ve volunteered with Benetech for over 7 years. I met their technical director at Open Web Camp in Open Web Camp 2013, where I demoed my early prototype of a web-based sonification system. It turned out that Benetech needed someone to help convert a desktop application for an accessible graphing calculator, originally developed by NASA, to the web, and they needed to sonify it like the original. I signed up to do the work, and in lieu of payment, I asked them to join W3C, where I thought their money would be better spent. Benetech has been a core contributor to W3C accessibility standards ever since.

Over the years, I’ve contributed to their accessibility projects in one way or another, from serving on their advisory board to chairing their accessible dataviz task force to writing accessible open-source apps and components at their code sprints (like an annotation browser extension and a reusable infobox popup).


Benetech does many things to promote social equity through technology. In 2010, they launched DIAGRAM: Digital Image and Graphic Resources for Accessible Materials. Their goal is to develop tools and best practices to reduce costs and other barriers to accessible images in educational content. It’s a worthy goal, one I’m proud to be involved with.

Born Accessible

Benetech’s DIAGRAM Center has a mantra for digital content: “Born Accessible”. They urge everyone to think about accessibility when they’re first creating digital content, not to bolt it on as an afterthought, or worse yet, to publish inaccessible material that others have to remediate.

“Born Accessible” is a philosophy we embrace at Fizz Studio. When I first started talking about making data visualizations accessible by embedding the data in the SVG file, back in 2009, I often met with two primary objections:

  1. File size: the data would add too much content to the chart
  2. Proprietary data: authors would not be willing to share their data

But a decade later embedding data (part of what I call “Deep Graphics”) has emerged as a common practice for accessibility in web charts. Openness and accessibility will ultimately win the day. I’ll write more about Deep Graphics and embedding data in another post.

If you’re an educator, or the parent of a child with disabilities, or just someone who wants to learn more about making your digital content born accessible, I hope you’ll read the DIAGRAM Center’s 2019 Report and find it useful. We want to support you.

Uncharted Territory

Fizz Studio is an experiment.

I’ve never run my own startup before, and for the past decade, I’ve been focused on open standards rather than production software development. So, I’m learning a lot about the modern software development and business side of things.

And more importantly, accessible data visualization is still uncharted territory. There are plenty of techniques that have been attempted, from data-table alternative to sonification to haptics and tactiles, but they all have their tradeoffs.

We have a unique vision to set the standard, to change expectations for what it means to provide a truly equivalent experience of data exploration for people with disabilities. Whether we can realize that vision is yet to be seen, through a glass darkly.

Data visualizations are not pictures of data, they are user interfaces to data. The map is not the territory, it is a tool to navigate the territory.

This blog will be an exploration of the known, the unknown, and the experimental. We’ll share what we’ve learned, and invite you to teach us what you know and what you need.

By the end, our destination may not be where we thought it was, but we welcome you to come on this journey with us, across unknown waters and strange lands. We think the trip will be worthwhile.