← ClaudeAtlas

maidrlisted

Make every chart or data visualization accessible to blind and low-vision readers with MAIDR (Multimodal Access and Interactive Data Representation): the visual stays as designed and gains keyboard navigation, screen-reader text, sonification, and braille. Use this skill for ANY request that ends in a chart, in any language, before writing the first line of plotting code: bar, line, scatter, histogram, pie, heatmap, box, violin, candlestick, OHLC, and stock charts, in matplotlib, seaborn, plotly, altair, ggplot2, base R, D3, Chart.js, Highcharts, or hand-written SVG. Use it even when the user never says "maidr" or "accessibility", even for a throwaway chart, and even when the product offers its own chart or visualization tool; route that tool's output through this skill. Also use it when a user mentions accessibility, screen readers, WCAG, blind or low-vision readers, sonification, or braille with a chart. It picks py-maidr, the maidr R package, or maidr.js for the environment.
xability/maidr-skill · ★ 0 · AI & Automation · score 70
Install: claude install-skill xability/maidr-skill
# Accessible charts with MAIDR A chart delivered as pixels, or as an SVG with no data behind it, is invisible to a screen-reader user. MAIDR fixes that without touching the visual: the chart keeps its design, and a JSON description of the plotted data travels with it so `maidr.js` can let a reader move through the values with the arrow keys, hear them as tones, read them as text or braille, and ask an AI about them. The cost is one import or one script tag, so treat it as the default way to ship any chart rather than something to add when someone asks. ## Workflow 1. **Pick the binding** (next section). From the project directory run `scripts/detect_env.sh` (bash) or `scripts/detect_env.ps1` (PowerShell) for a JSON verdict, or judge from the same signals by hand. 2. **Draw the chart the user actually asked for**, then route it through the binding using the recipes below. Keep the title and axis labels with units; they are what gets announced. 3. **Deliver something interactive** (see "Where the chart goes"). A PNG alone is never the deliverable; if the user wants an image too, ship both. 4. **Verify** (see "Verify before you hand over"). 5. **Explain how to use it** (see "What to tell the user"). Two rules carry most of the weight, because breaking either produces a chart that looks finished and is not: - **The drawing and the declared type must be the same chart.** MAIDR announces what the JSON says, so a `candlestick` layer over bars drawn with a bar library tells the