What TanStack Charts does for stacked charts on its own, and what you add so that everyone can read them.
What you get
A named chart. ariaLabel is required, and the chart is exposed as an image with that name. ariaDescription adds a longer description.
Keyboard navigation, on by default. Tab moves into the chart and focuses the first segment. Arrow keys move between them, and Home and End jump to the first and the last. Enter or Space pins a sticky tooltip, and Escape closes it.
The tooltip is announced to screen readers as it changes, so a keyboard user hears the values of the focused segment.
A visible focus ring in the theme's focus color, shown for keyboard focus only.
Reduced motion. Animated charts skip their animation when the reader has asked for less motion.
An interactive legend made of real buttons, each with a pressed state, when you use interactiveColorLegend.
What you add
A label that says what the chart shows, its unit and its period. "Revenue by channel, January to June" works. "Stacked area chart" does not.
A visible title, and a subtitle with the unit and the period, in HTML next to the chart.
The exact values another way, when they matter: a table under the chart, behind a toggle, or a download.
A second signal besides color for every series or part.
A keyboard path for every control you add yourself, such as a series filter or a period picker.
Name and describe the chart
Keep the label short and put the takeaway in the description. Do not put every value into the name: a screen reader reads it in one breath.
<Chart
definition={definition}
ariaLabel="Revenue by channel, January to June"
ariaDescription="Revenue rose from 78 thousand in January to 104 thousand in June, with online the larger part every month."
/>
Give the values as a table
A table is the most reliable way to give exact values to everyone, including people who zoom far in or print the page. Render the same array the chart reads with the kit's Table, under the chart or behind a "Show as table" switch. When the values are only an illustration, a one sentence summary is enough.
Do not rely on color
Keep the legend, the tooltip and the stack in the same order. Pass sort: "color-domain" to the tooltip so its rows follow the color domain.
Separate the segments with a thin gap or an edge, such as inset on bars or a stroke on areas, so neighbors stay apart in grayscale.
For an ordered scale, use light to dark steps of one or two hues, and a neutral gray for the middle answer, so the order reads without telling hues apart.
Marks need enough contrast with the background. Check light colors from a palette against the page in light and dark mode.
Say the totals
A screen reader user hears one segment at a time, and the tooltip shows each row's own value. When the total matters, put it in ariaDescription or in the table, so no one has to add the segments up.
Turning the keyboard off
A static chart with no tooltip can pass keyboard: false in the second argument of defineChart, so it does not add a tab stop. Keep it on for any chart that shows values on hover: otherwise keyboard users never see them.
Check it
Tab into the chart and read every segment with the arrow keys.
Listen to it with a screen reader.
Zoom the page to 400% and confirm the values are still there.
View it in grayscale and confirm the series are still apart.
The Accessibility guideline has the principles that apply to every chart.