Kb Data Visualization Accessibility logo

Kb Data Visualization Accessibility

Organization
Community-Access
kb-data-visualization-accessibility

Reference data, not a reviewer. Audit charts and graphs for accessibility: SVG ARIA, data table alternatives, keyboard interaction, color-safe palettes, and library APIs.

Overview

PublisherCommunity-Access
Repositoryaccessibility-agents
Skill namekb-data-visualization-accessibility
Stars
429
Forks
51
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Community-Access on GitHub. Read the source before you install it.

Installation

Install the Kb Data Visualization Accessibility AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-data-visualization-accessibility
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git /tmp/accessibility-agents
mkdir -p .claude/skills
cp -r /tmp/accessibility-agents/skills/kb-data-visualization-accessibility .claude/skills/kb-data-visualization-accessibility
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Kb Data Visualization Accessibility in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Kb Data Visualization Accessibility on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Kb Data Visualization Accessibility is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Data Visualization Accessibility Skill

Reference data for making charts, graphs, dashboards, and interactive data visualizations accessible. Used by data-visualization-accessibility agent.


Chart Accessibility by Type

Bar/Column Charts

  • Provide a text summary of the key takeaway (e.g., "Sales increased 40% in Q4")
  • Include a data table alternative (visually hidden or toggleable)
  • Each bar should be keyboard-focusable with a tooltip announcing the value
  • Use patterns or textures in addition to color to distinguish series

Line Charts

  • Describe the trend in alt text (e.g., "Upward trend from January through June, then decline")
  • Provide data table with all data points
  • Keyboard navigation: Left/Right arrows move between data points, value announced on focus
  • Use distinct line styles (solid, dashed, dotted) alongside colors

Pie/Donut Charts

  • Accompany with a data table showing percentages
  • Each segment keyboard-focusable with percentage and label announced
  • Use patterns/hatching — color-only distinction fails WCAG 1.4.1
  • Consider: pie charts are generally poor for accessibility; a bar chart + table is often better

Scatter Plots

  • Provide summary statistics (mean, median, correlation) as text
  • Data table with all points is essential
  • Interactive exploration via keyboard may not be feasible for large datasets — prioritize the summary

Treemaps / Heatmaps

  • Provide hierarchical data table alternative
  • Keyboard navigation through segments with value announcements
  • Color scales must have sufficient contrast between adjacent levels

SVG Accessibility Patterns

Static Chart (Image-like)

html
<figure>
  <svg role="img" aria-labelledby="chart-title chart-desc">
    <title id="chart-title">Monthly Revenue 2025</title>
    <desc id="chart-desc">Bar chart showing revenue from January through December.
      Revenue grew from $50K in January to $120K in December with a dip in July.</desc>
    <!-- chart elements -->
  </svg>
  <figcaption>Figure 1: Monthly Revenue 2025. <a href="#revenue-table">View data table</a></figcaption>
</figure>

Interactive Chart

html
<svg role="application" aria-roledescription="interactive chart" aria-label="Monthly Revenue">
  <g role="list" aria-label="Revenue data points">
    <rect role="listitem" tabindex="0" aria-label="January: $50,000" .../>
    <rect role="listitem" tabindex="0" aria-label="February: $55,000" .../>
  </g>
</svg>
<div aria-live="polite" class="sr-only" id="chart-announcements"></div>

Decorative Charts

html
<svg aria-hidden="true" focusable="false">
  <!-- decorative background chart -->
</svg>

Chart Library Accessibility APIs

Highcharts

javascript
Highcharts.chart('container', {
  accessibility: {
    enabled: true,
    description: 'Chart showing quarterly revenue growth',
    point: {
      valueDescriptionFormat: '{point.name}: {point.y} dollars'
    },
    keyboardNavigation: {
      enabled: true,
      order: ['series', 'zoom', 'rangeSelector', 'legend', 'chartMenu']
    }
  },
  // Highcharts has built-in sonification for data
  sonification: {
    enabled: true
  }
});

Highcharts built-in a11y features:

  • Automatic <table> fallback generation
  • Keyboard navigation between data points
  • Screen reader announcements for each point
  • Sonification (data as sound)
  • High contrast mode support

Chart.js

javascript
new Chart(ctx, {
  type: 'bar',
  data: { /* ... */ },
  options: {
    plugins: {
      // Chart.js has limited built-in accessibility
      // Use chartjs-plugin-a11y-legend for legend accessibility
      // Use chartjs-plugin-datalabels for visible data values
    }
  }
});
// Chart.js renders to <canvas> — provide a fallback table or aria-label on canvas

Chart.js limitations:

  • Canvas-based — no DOM elements for screen readers to traverse
  • Must provide <canvas aria-label="..." role="img"> or a fallback <table>
  • No built-in keyboard navigation — requires custom implementation

D3.js

D3 renders to SVG — accessibility must be manually implemented:

javascript
// Add ARIA to each data element
bars.attr('role', 'listitem')
    .attr('tabindex', '0')
    .attr('aria-label', d => `${d.name}: ${d.value} units`);

// Add keyboard navigation
bars.on('keydown', (event, d) => {
  if (event.key === 'ArrowRight') { /* focus next bar */ }
  if (event.key === 'ArrowLeft') { /* focus previous bar */ }
});

Recharts (React)

jsx
<BarChart data={data} accessibilityLayer>
  <Bar dataKey="value" />
</BarChart>

Recharts: accessibilityLayer prop adds basic ARIA attributes. Supplement with a data table.

Data Table Fallback Template

html
<details>
  <summary>View data table</summary>
  <table id="revenue-table">
    <caption>Monthly Revenue 2025</caption>
    <thead>
      <tr>
        <th scope="col">Month</th>
        <th scope="col">Revenue ($)</th>
        <th scope="col">Change (%)</th>
      </tr>
    </thead>
    <tbody>
      <tr><td>January</td><td>50,000</td><td>—</td></tr>
      <tr><td>February</td><td>55,000</td><td>+10%</td></tr>
    </tbody>
  </table>
</details>

Color-Safe Palettes

Palettes that remain distinguishable under common forms of color vision deficiency:

Wong Palette (8 colors — CVD safe)

Each color, with its hex and use.

ColorHexUse
Black#000000Text, borders
Orange#E69F00Data series 1
Sky Blue#56B4E9Data series 2
Bluish Green#009E73Data series 3
Yellow#F0E442Data series 4
Blue#0072B2Data series 5
Vermillion#D55E00Data series 6
Reddish Purple#CC79A7Data series 7

Rules for Color in Charts

  • Never use red/green as the only distinction (deuteranopia affects ~8% of males)
  • Always add a secondary visual channel: pattern, shape, label, or position
  • Test with CVD simulation tools (Sim Daltonism, Chrome DevTools Emulate vision deficiencies)
  • Ensure adjacent colors in a chart have sufficient contrast with each other (not just against white)

Keyboard Interaction Model

Single-Series Chart

Each key, with its action.

KeyAction
TabEnter/exit chart
Left/Right ArrowMove between data points
Up/Down ArrowMove between series (if multiple)
Enter/SpaceShow detail or drill down
EscapeExit drill-down or chart
Home/EndJump to first/last data point

Dashboard Navigation

Each key, with its action.

KeyAction
TabMove between chart widgets
EnterEnter interactive chart
EscapeExit back to dashboard level
Arrow keysNavigate within active chart

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Kb Data Visualization Accessibility AI skill do?

Reference data, not a reviewer. Audit charts and graphs for accessibility: SVG ARIA, data table alternatives, keyboard interaction, color-safe palettes, and library APIs.

Why use Kb Data Visualization Accessibility on TypingMind?

Because you install it once and use it with any model. Kb Data Visualization Accessibility is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Kb Data Visualization Accessibility in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-data-visualization-accessibility. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Kb Data Visualization Accessibility?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Kb Data Visualization Accessibility?

As many as you like. As long as a model supports skills, you can use Kb Data Visualization Accessibility with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Kb Data Visualization Accessibility AI skill free?

Yes. It is published on GitHub by Community-Access under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇