A valid chart spec does not guarantee a readable result. Review the rendered artifact at its intended size, including axis labels, units, threshold annotation, legend, contrast, and clipping. Provide a concise text alternative that states the chart's purpose and a longer data view when exact values matter. Avoid encoding status by color alone; pair it with labels or distinct marks. The text alternative must match the actual plot, including missing intervals and uncertainty, rather than repeating an earlier draft claim. A release gate compares rendered marks with the source table and checks keyboard or screen-reader access when the chart is interactive.
Make this comfortable
Chart prompts: review rendered and nonvisual outputs
Operational case
The C-47 plot renders correctly at desktop width but clips the 5.0-degree threshold label on a narrow report page. A visual review catches the cut-off label before release. The text alternative states that two of five observed hourly readings exceed the limit and that the third scheduled hour is missing. An accompanying data view lists all six slots, including the missing one. The team checks that an interactive tooltip is reachable by keyboard; if it is not, the static data view still exposes the exact values.
Visual check: title, time zone, °C axis, 5.0 °C label, gap.
Text: two of five observed readings above limit; one missing slot.
Exact data: six scheduled rows available in a data view.
Color: supplemented by labels or distinct marks.
Narrow render: threshold label must remain visible.Performance and operating cost
A visual review costs a small fixed inspection per viewport, while exact value reconciliation requires O(N) comparisons for N plotted rows. Accessible alternatives add authoring time but allow a reader to obtain the same critical finding without relying on color or pixels. Automated schema checks cannot catch clipping, misleading label placement, or a stale text alternative. Treat the rendered chart and its nonvisual description as one release unit.
Common Mistakes
- Do not assume a valid spec means the rendered chart is legible.
- Do not make color the sole carrier of threshold status.
- Do not publish a text alternative that ignores the missing hour.
Connected lessons
- Production prompt engineering
- Prompt Engineering
- Accessible output evaluations: measure failures by artifact and user task
- Image alternatives: prompt for purpose, then check the image
- UI release prompts: compare appearance and verify access
- Chart prompts: state the decision and measured quantity
- Chart prompts: choose marks and scales by data type
- Chart prompts: expose missing data and checked denominators
- Chart prompts: produce a reproducible spec and data lineage
- Project: review a cold-chain temperature chart
- Chart-creation prompt decisions
Continue with: Location prompts: review the map and gate dispatch effects.
Continue with: Accessibility prompts: measure contrast and describe image purpose.
prompt engineering
chart creation