Skip to main content

disability-access-charts

Charts that check their own words.

Built for Curb Cut, an accessible platform for Nigerian disability data. Every chart ships with alt-text built from its data, and the library then checks that text against the data: every number, and every comparison it recognises ("highest", "higher than", "twice", "ranked 3rd"). With survey estimates, it tests whether the confidence intervals actually support the claim. The same checker gates any LLM rewording and runs on any Plotly figure in CI.

Status: 0.3 (alpha). English only, built so other languages can be added.

New in 0.3: maps that are easier to read

  • A clearer default map scheme. choropleth(scheme="ylgnbu"), now the default: a colour-blind-safe yellow to green to blue scale (ColorBrewer's YlGnBu in the light theme, a matching dark palette that gets brighter with the value) with larger lightness steps than 0.2's greens. MAP_SCHEMES lists the schemes.
  • Cased boundaries. No one boundary colour stands out from both a pale yellow and a dark blue, so a theme can add a halo: the page draws a wide halo stroke under a narrow edge stroke. The audit asks that the edge is 3:1 against the background and the halo, and that the edge or the halo is 3:1 against the background and every fill.
  • Map patterns ordered by ink weight, lowest class lightest: plain, dots, lines, crosshatch, solid (MAP_PATTERNS; ordered subsets for fewer classes). Each class has its own ink, black or white, whichever contrasts more with its fill, audited at 3:1. Bars are unchanged.
  • A colour-vision check. Neighbouring fills are compared under simulated deuteranopia, protanopia and tritanopia (Machado et al. 2009) with CIEDE2000: an error under 5, a warning under 10. The default scheme's closest pair is 10.3 (light) and 11.6 (dark). Pure Python, in disability_access_charts.vision.
  • Legend-filter metadata. Each class lists its regions and the sentence a page announces when a legend button shows only that class ("Showing 6 states in 4% to under 6%: …"), checked against the data.

What changed from 0.2, precisely:

  • Changed default: choropleth() uses scheme="ylgnbu" (and MAP_THEMES is now its themes). For the 0.2 look, pass scheme="green": the 0.2 greens, one boundary colour, the 0.2 pattern order and one ink per theme. Its audit now adds a colour-vision-target warning (the greens reach 7.5 and 8.2), so check --strict fails on it. Custom themes too: choropleth(..., themes=...) without scheme now gets the 0.3 pattern style (ink-weight order with an ink per class, no single patterns.ink) and the new audit checks, so a custom set of fills can fail the new colour-vision error (or the casing rule, if a theme has a halo); pass scheme="green" with your themes= to keep the 0.2 pattern order and one ink per theme.
  • Map documents use schema "1.1": themes may have a halo, patterns has sequence and (outside the green scheme) class_ink in place of ink, classes have regions and announce, and there are legend, keyboard.legend_filter and meta.scheme. legend_filter=False leaves the legend metadata out.
  • New audit checks: cased-boundary contrast, colour-vision, colour-vision-target, legend-filter-matches-data, and patterns-ink-rule for maps.
  • svg_pattern() takes ink=None for a tile with no ink. Bars, dot plots and everything else are unchanged apart from the version number.

See the maps note and the patterns note.

New in 0.2

  • Statistical findings. findings=True on bar(), grouped_bar() or dot() adds a block that compares the estimates in four families declared in advance (highest and lowest against the next, gaps between series, neighbours in the ranking, each estimate against an overall value), counts every comparison, and controls the false discovery rate (Benjamini-Hochberg, q = 0.05). It prints "N comparisons checked, K supported", hedges findings that involve an estimate flagged for review, and leaves out (and counts) those that involve a suppressed or unreliable one. The sentences go through the claim checker, and the audit recomputes the block from the data. It is descriptive, not causal: see the findings method.
  • Patterns. Five abstract tiles inspired by adire (dots and rings after oniko, checks, lines, crosshatch), drawn for this library; never nsibidi or Ukara signs. grouped_bar() (new) gives each series its own colour and pattern, shown in the legend; bar(patterns=True) and every map class get one too. The audit checks that patterns and colours line up one to one and that the pattern ink is 3:1 against every fill in both themes. See the patterns note.
  • Maps are stable. choropleth() is exported, with a pattern per class by default, so neighbouring classes differ by more than a shade.
  • Precision flags. Series(..., precision=...) takes a flag per estimate (reliable, review, unreliable, suppressed), shown in the table and used by the findings.

What changed from 0.1, precisely:

  • choropleth() gives each class a pattern by default (patterns=None means "auto": on with five classes or fewer, off with more, when the audit warns that neighbouring classes differ by shade alone). patterns=False gives the 0.1 document; patterns=True with more than five classes raises.
  • describe(chart_type="bar") with several series now describes grouped bars; in 0.1 it raised.
  • In the claim checker, a list of names with values separated by semicolons ("A, 1%; B, 2%; and C, 3%") is one clause, so each estimate in a list written that way (with "; and" before the last item) is checked (a two-item list without the "and", or a comma list, is only partly checked), and a hedged rank ("the second-highest estimate") no longer warns when the test cannot separate it from a neighbour.

Otherwise bar() and dot() with patterns and findings off (their default) give the same document as in 0.1, apart from the version number.

pip install disability-access-charts            # core: no dependencies
pip install "disability-access-charts[plotly]"  # adds Plotly Figure support

What it looks like

Every chart comes in a light and a dark theme, both contrast-checked:

Light theme: dot plot of synthetic prevalence in four areas for women and men, each with a 95% confidence interval. The generated description follows the images.

The same dot plot in the dark theme.

The description the library wrote for this chart (synthetic data), shortened here:

Women: highest estimate Area A, 9.8%, and the survey cannot show a difference from the next estimate, Area B, 9.1%; lowest estimate Area D, 4.0%, and the survey can show a difference from the next estimate, Area C, 6.2%. …

So "Area A is the highest" is never written, and if someone writes it, the checker rejects it:

from disability_access_charts import ChartData, Series, check_alt_text, dot

areas = ["Area A", "Area B", "Area D"]
women = Series(
    "Women",
    values=(9.8, 9.1, 4.0),
    lower=(8.1, 7.6, 3.1),  # 95% confidence interval
    upper=(11.5, 10.6, 4.9),
)

doc = dot(
    areas,
    [women],
    title="ILLUSTRATIVE ONLY: synthetic prevalence (not real data)",
    value_label="Prevalence (%)",
    category_label="Area",
    source="Synthetic",
    unit="percent",
)
data = ChartData.from_dict(doc["data"])

check_alt_text("Area A is higher than Area D.", data)  # [] : the difference is supported
check_alt_text("Area A is higher than Area B.", data)
# [Problem(..., kind='comparison', severity='error',
#   reason='the survey cannot show that Area A is higher than Area B: the difference 0.70
#           is not more than 2.27', suggestion='the survey cannot show a difference')]

What you get

bar(), grouped_bar(), dot() and choropleth() return one JSON document per chart, with no Plotly import needed:

key what it holds
plotly a static Plotly.js spec: no hover-only data, no zoom or pan
alt_text the description, built from the data, summary first
table the same numbers as an accessible table
data the numbers the checker reads (categories, series, intervals)
themes light and dark colours, contrast-checked (WCAG 2.2 SC 1.4.3, 1.4.11)
keyboard how a keyboard user reaches the data (the table)
audit every check, each with a WCAG criterion and a severity
meta generator, library version, source, alt-text language and origin
findings with findings=True: the comparisons, their tests, the FDR result and the sentences
patterns with patterns on: the tiles, each series' or class's tile, and the ink (each theme's, or since 0.3 each map class's)

Also: audit(fig) for a document or any Plotly figure, theme(fig, "dark"), to_html(doc) and to_csv(doc), figure(doc) for a Plotly Figure, and a CLI for CI:

disability-access-charts check charts/*.json            # exit 1 if any chart fails
disability-access-charts check --strict charts/*.json   # warnings fail too

What the checker checks

  • Numbers: each must be a figure of the category it sits next to (value, interval bound or share), so "Kano, 11.9%" fails if 11.9% is Lagos's.
  • Extremes: largest, highest, smallest, lowest.
  • Comparisons: higher, lower, more, fewer than, including lists ("higher than Lagos and Abuja").
  • Ratios: twice, half, N times, within 5%.
  • Ranks: "ranked 2 of 37", "3rd", "the second-highest".
  • "No difference" always fails: a survey can't show that two groups are equal.

With confidence intervals, "A is higher than B" passes only if the difference is larger than 1.96 times its standard error, worked out from the two intervals. This assumes roughly symmetric intervals and independent groups, and applies no correction for multiple comparisons; it warns when groups may not be independent. "A is the highest" must be separated from every other group; otherwise write "A has the highest estimate".

What a pass means: no recognised claim was found false. It does not make a description true or complete.

Limits. Negated claims ("not higher"), words it doesn't know ("exceeds", "similar"), and numbers written as words get a warning, not a check. Differences written as numbers ("3 points higher"), comparisons with a stated number ("above 10%"), trends and causes are not understood. The full rules are in the claim checker reference.

LLM polish (optional)

polish_alt_text(doc, disclosure_checked=True) asks Gemini, then Groq, to reword the alt-text. A rewording is kept only if the checker finds no errors or warnings in it and it keeps every category, number, interval label and the source; otherwise the data-built text stays. It sends only the chart's aggregates, title and source. Pass only disclosure-checked public aggregates, never microdata. Results are cached in .disability_access_charts_cache/, and the tests never call the network.

More

  • Languages: one table of templates and claim words per language (_lang/en.py); only English ships so far. Numbers stay as digits in every language, so the checker still works.
  • Maps: choropleth() builds a shaded-map document in fixed classes, each with its own pattern (up to five classes, ordered by ink weight) on a colour-blind-safe scale with cased boundaries, with the same alt-text checks, a table and an audit; audit() and check handle it. The page draws the SVG from the document. How its colours and patterns meet WCAG is in the maps note.
  • Python: 3.10 or later. Tests and CI run on 3.12; 3.10 is checked by installing the wheel and running the examples.
  • Examples (in the source distribution and the repository's examples/): JONAPWD's 2025 assumed figures by disability type (a WHO 15% benchmark applied to population, not survey estimates), a synthetic dot plot with intervals and findings, a synthetic patterned map written out as a standalone SVG page, and an audit of a plain Plotly figure. The installed package holds no data.

How it compares

We found no other library that checks the comparative claims in a chart description against its data. The closest work we found is AggChecker (Jo et al., VLDB 2019), a research system that checks claims against a database rather than charts.

  • a11yviz has WCAG-tagged palettes, alt-text scaffolds and audits for plotnine, plotly and Quarto.
  • maidr makes charts explorable by keyboard, with sound, braille and text descriptions.

Use maidr for multimodal exploration. Use this library to catch numbers and comparisons in a description that contradict the data, and to report which differences in a chart survive a multiple-comparison correction. (Both descriptions checked against their PyPI pages on 2026-10-29: a11yviz 0.1.8, maidr 1.28.1.)

MIT licensed.

Metadata

Release files for disability-access-charts 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for disability-access-charts 0.3.0
File Size Uploaded Provenance Actions
disability_access_charts-0.3.0.tar.gz 189.2 kB With provenance Details for disability_access_charts-0.3.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for disability-access-charts 0.3.0
File Interpreter ABI Platform Actions
disability_access_charts-0.3.0-py3-none-any.whl Python 3 none any Details for disability_access_charts-0.3.0-py3-none-any.whl

Total release size: 290.4 kB

Release files / disability_access_charts-0.3.0.tar.gz

Download URL disability_access_charts-0.3.0.tar.gz
Size 189.2 kB
Tags Source
SHA-256 checksum
How to use checksums
4e92ae1c67750d1a7db87dbb4292783b86cef0e3ac085040f91534f83de6f456
BLAKE2b-256 checksum
How to use checksums
0010f8bb7ab5dfbb503bc86369c2d8f0fe4d6e5bf37af3c48d6c0dc7139ac3ca
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

Release files / disability_access_charts-0.3.0-py3-none-any.whl

Download URL disability_access_charts-0.3.0-py3-none-any.whl
Size 101.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8e54aab7b07895b236decddda625b93846819533c51b8fcd11d855a605f7bc32
BLAKE2b-256 checksum
How to use checksums
155971197d543a8adccb16c911213e29dbc51d65431b346fbf85b1c66e1df851
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

Security for disability-access-charts 0.3.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for disability_access_charts-0.3.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page