Lorixen.
EN

Accessible charts and dashboards: beyond the pretty graph

Short answer: Charts are one of the least accessible parts of most business dashboards and reports. A sales graph that relies on colour, has no text alternative and cannot be reached by keyboard tells some users nothing. Give every chart a short description and a fuller explanation of the key message, offer the underlying numbers as a real data table, never use colour as the only way to tell series apart, keep lines and segments at a contrast of at least 3:1, and make interactive parts usable without a mouse.

Who gets left out

Charts appear everywhere in business software: revenue dashboards, booking trends, website analytics, energy usage in a customer portal, annual report pages. The people who struggle with them include:

  • Screen reader users, who hear "image" or nothing at all.
  • People with colour vision deficiencies, who cannot tell a red line from a green one.
  • People with low vision, who cannot see thin, pale lines or small labels.
  • Keyboard users, who cannot reach tooltips that only appear on hover.
  • People who simply find charts hard to read and want the numbers.

That includes customers, staff and the managers reading the dashboard on a phone in sunlight.

Describe what the chart says

The W3C Web Accessibility Initiative's tutorial on complex images, which covers graphs and charts, says such images need a two-part text alternative: a short description that identifies the image and, where appropriate, says where the long description is, and a long description that gives a textual representation of the essential information the image conveys.

For a chart, that might be:

  • Short: "Bookings per month, January to June."
  • Long: "Bookings rose steadily from 120 in January to 310 in June, with the largest jump between April and May after the spring campaign."

The tutorial notes that structural details, such as the sequence of colours and the relative heights of columns in a bar chart, may also be relevant information alongside the values and trends. Write the description around the decision the chart supports, not every pixel.

Offer the data as a table

The same tutorial's examples include a long description made of headings, text and a table, wrapped in a figcaption with the figure marked as a group. A real HTML table of the data behind a chart is often the most useful alternative: screen readers can navigate it cell by cell, and anyone can read exact values.

Practical patterns:

  • A "Show data" toggle under each chart that reveals the table.
  • The table placed right after the chart, visually hidden only if space is very tight.
  • A download of the underlying data where people need it for their own analysis.

Do not rely on colour alone

WCAG's Use of Color success criterion says colour must not be the only visual means of conveying information or distinguishing a visual element. For charts:

  • Label lines directly at their ends instead of relying on a colour legend.
  • Use different line styles, such as solid and dashed, or markers such as circles and squares.
  • Add patterns or textures to bars and pie segments, or label them.
  • Pick a palette that remains distinguishable for common colour vision deficiencies, and check it with a simulator.

Contrast for lines, bars and labels

WCAG's Non-text Contrast criterion requires a contrast ratio of at least 3:1 against adjacent colours for parts of graphics required to understand the content. Pale grey gridlines can be fainter, since they are decoration, but data lines, bars, pie segments and important markers should meet that ratio against the background and, where they touch, each other. Text labels and axis values follow the normal text contrast rules.

Interactivity without a mouse

Tooltips, filters and drill-downs are common in dashboards. Make sure:

  • Chart controls such as series toggles and date-range filters are real buttons and form controls, reachable by keyboard.
  • Information shown on hover is also available another way, such as the data table or on focus.
  • Changing a filter announces the update for screen reader users, for example "Showing last 30 days".
  • The chart reflows sensibly on narrow screens and at high zoom.

Check it with real tools

Before calling a chart done, try it the way people will use it. Turn on a screen reader and listen to the page from the chart heading to the data table. Use a colour vision simulator in your browser's developer tools to see the chart as someone with red-green colour blindness would. Zoom the page to 200% and check labels still fit. Then tab through the controls without touching the mouse. Each check takes minutes and catches problems that automated scanners usually miss.

Choosing a charting library

Libraries vary widely in accessibility support. Look for built-in descriptions, keyboard navigation between data points, pattern fills and an option to render an accompanying table. Test with a screen reader before committing, since claims and reality differ.

A worked example

Picture a hypothetical Galway community energy co-operative whose customer portal showed each household's generation and usage as a colourful line chart. A customer who is colour-blind could not tell which line was generation; a screen reader user heard only "graph".

The team added a short label and a one-sentence summary above each chart, such as "This week you generated more than you used on four of seven days", a "Show data" table with daily figures, direct line labels, a dashed style for usage and darker lines that meet 3:1 contrast. The date filter became a set of buttons that announce the new range. Support questions about reading the chart dropped, and the summary sentence became the most-read part of the page.

FAQ

Is alt text enough for a chart?

For a simple chart with one point, maybe. For anything with real data, add a longer description or a table.

Do PDF reports need the same treatment?

Yes. Charts in PDFs need alternative text and, ideally, the data in an accessible table nearby.

Should every dashboard chart have a table?

Ideally, yes, even if collapsed by default. It also helps sighted users who want exact numbers.

If customers or staff struggle to read the charts in your portal or dashboards, tell us what your charts show.

Sources

WhatsAppBook a call