To translate tables, charts, graph labels and figure captions accurately, you must preserve the relationship between words, numbers and position. A chart can contain only a handful of translated words yet still become seriously wrong if an axis label changes scope, a legend category is swapped, a unit disappears, a negative sign shifts, a table header no longer matches its column, or a figure caption describes the opposite comparison from the graphic.
This guide explains how to translate tables, charts, graphs, figure captions, legends, axis labels, data labels and visualisations in research papers, textbooks, reports, dashboards, presentations, technical manuals and educational material. It solves one practical search intent: how do you translate the language around a visual display without changing the structure, quantities, comparisons or evidence that the visual display is meant to communicate?
The central method is to treat every visual as a system rather than a picture. Identify the data object, row and column relationships, axis variables, units, legend categories, scale type, source note and caption before changing any text. W3C accessibility guidance emphasizes that data tables need structural relationships between headers and cells and that captions help users identify and understand tables. The same preservation mindset connects this specialist guide to Master Art of Translation, the protected Vocabulary Learning Hub, and How English Works.
A one-minute orientation: visual translation is relationship preservation
A paragraph is read mainly in sequence. A chart is read spatially. Meaning can depend on whether a label is above or below a line, whether a legend square matches a series, whether a column heading spans one or three columns, and whether an annotation points to the correct data point.
That means translation quality cannot be judged from extracted text alone. A perfectly translated phrase can be wrong when placed beside the wrong row. A correct legend term can still mislead if its color swatch or line style is attached to another series. Visual translation requires semantic accuracy and positional accuracy together.
The strongest question is: Could a reader reconstruct the same relationships from the translated visual as from the source? If the answer is no, then the visual has not been translated faithfully even if every isolated word is linguistically correct.
1. Inventory every text-bearing component before translating
Start by listing the title, subtitle, axis labels, tick labels, legend entries, data labels, annotations, table headers, stub columns, source notes, footnotes, statistical notes, figure number and caption. Hidden text may also appear in hover tooltips, accessibility labels, alt text or linked descriptions.
This inventory prevents the common problem of translating the obvious words while leaving embedded labels in the source language. Mixed-language graphics look unfinished and can create interpretation errors when two terms refer to the same category in different languages.
Keep a source-to-target map for repeated labels. If “Control” appears in the legend, table, caption and body text, translate it consistently unless context genuinely differs. Visual repetition is part of the reader’s navigation system.
2. Determine what the chart actually encodes before touching the wording
Ask what each visual variable means. Position may encode value. Color may encode category. Line thickness may encode confidence. Shape may distinguish groups. Size may encode magnitude. A translated label is only safe when you know which visual encoding it names.
For example, a bubble chart may use horizontal position for income, vertical position for life expectancy, bubble size for population and color for region. Translating only the axes leaves two additional meanings unexplained if size and color legends are missed.
Do not simplify a visual merely because the language is dense unless redesign is part of the assignment. Translation and redesign are different operations. A shorter label that deletes an important qualifier can change the encoded variable.
3. Preserve chart titles as claims, not decorations
A chart title can be descriptive—“Monthly Sales, 2024”—or argumentative—“Remote Teams Closed the Performance Gap.” The second title makes a claim about what the data show. Translation must preserve the level of certainty, direction and scope of that claim.
Do not intensify “associated with” into “caused,” “higher” into “better,” or “selected countries” into “all countries.” Visual titles are often read before captions and methods, so small wording changes can shape the reader’s entire interpretation.
If the source title is intentionally neutral, keep it neutral. A translator should not add an explanatory conclusion that the author did not make. If the source is promotional or rhetorical, preserve that function without inventing stronger evidence.
4. Axis labels must preserve variable, unit and transformation
An axis label may contain three layers: the variable name, unit and transformation. “Income (USD, log scale)” is not equivalent to “Income.” Dropping USD removes the unit; dropping log scale changes how distance on the axis should be interpreted.
Preserve qualifiers such as per capita, seasonally adjusted, index, baseline=100, percentage change, rate per 100,000 or log10. These words and symbols tell the reader what the numbers mean. Shortening them for layout without compensation can create a false quantity.
When space is tight, use an established abbreviation and explain it in the caption or note. Do not simply remove the qualifier. The visual must remain interpretable without requiring the reader to guess which version of the variable was plotted.
5. Tick labels can carry locale conventions without changing value
Numbers may use decimal points, decimal commas, spaces, periods or commas as grouping separators depending on locale. A visual can be localized typographically while preserving the underlying numeric value.
Be cautious when converting “1,234” because in one convention it means one thousand two hundred thirty-four, while in another context a comma can mark the decimal. Determine the source locale and target convention before changing separators.
Do not recalculate values merely to make a chart look familiar. Localizing number format is not the same as changing currency, unit or statistical definition. If conversion is required, document it and update the axis unit accordingly.
6. Linear and logarithmic axes must stay distinguishable
A linear axis uses equal visual distances for equal absolute differences. A logarithmic axis uses equal visual distances for equal ratios under its defined scale. Translation must preserve that distinction explicitly.
A chart with ticks at 1, 10, 100 and 1,000 may look deceptively simple. If the axis is logarithmic and the target label drops that fact, the geometry becomes misleading. The reader may interpret equal spacing as equal additive change.
For a deeper treatment, use Translate | Logarithmic Scales, Decibels, pH and Orders of Magnitude. This article focuses on preserving the visual system in which that scale appears.
7. Legends are mapping keys and must not be detached from their symbols
A legend says which visual symbol represents which category or series. During translation, the wording may expand and force reflow. If labels are rearranged manually, a category can become attached to the wrong color, line or marker.
Verify each mapping after layout: label to swatch, label to line style, label to symbol, and label to series. Do not assume the design software preserved the relationship when text boxes were moved or recreated.
Where color is not sufficient for accessibility, preserve secondary cues such as dashed versus solid lines, marker shapes or direct labels. Translation should not remove these distinctions just because the target text is longer.
8. Direct labels must point to the correct line, bar or point
Many modern charts label series directly instead of using a legend. This can improve readability, but it makes positional fidelity essential. A translated label that shifts toward a neighboring line can reassign the series visually.
Keep connector lines, leader lines and anchor positions intact. If the target wording is longer, consider a controlled line break rather than moving the label far from its data series. Any movement should preserve unambiguous association.
Test the graphic at the final display size. What looks clear while zoomed in may become ambiguous on a phone screen or printed page. Translation length can change visual crowding substantially.
9. Table headers define the meaning of every cell beneath them
A table header can apply to a column, row, group of columns or nested hierarchy. If the header is translated too broadly or narrowly, dozens of numeric cells may acquire the wrong meaning at once.
Preserve distinctions such as “Mean,” “Median,” “Change,” “Change (%)” and “Difference from baseline.” They may look similar but represent different quantities. The target header must tell the reader exactly which operation produced the numbers.
W3C accessibility guidance emphasizes that header cells and data cells should have programmatically determinable relationships. Translation should preserve not only visible words but also the markup that associates row and column headers with their data.
10. Multi-level headers require scope checking after translation
Complex tables may have a top header such as “2025 Results” spanning three subcolumns: “Mean,” “SD” and “n.” Another group may show 2026 with the same subcolumns. Translation can widen the group label and change wrapping.
Confirm that the visual span still covers the intended columns and that any HTML header associations remain correct. A border or merged cell moved by one column can alter which year the reader assigns to a statistic.
If the translated table becomes too complex, consider splitting it only if redesign is permitted. Do not silently collapse a hierarchy into flat headings that lose the relationship among groups, subgroups and measures.
11. Stub columns are often category labels, not ordinary prose
The leftmost column in a table may contain row categories such as age groups, regions, treatment arms or indicators. These labels need consistent terminology because each one anchors an entire row of values.
Do not translate one occurrence differently merely for stylistic variety. In prose, synonym variation can sound elegant; in tables, it can imply that two different labels represent different categories.
Use the project glossary and the Vocabulary Learning Hub principle of contextual word knowledge. A category label must preserve domain meaning, register and scope, not just dictionary equivalence.
12. Units belong in headers or labels exactly where readers expect them
Tables often place a unit once in the header instead of repeating it in every cell. If the unit is lost during translation, an entire column becomes ambiguous. A value of 25 could mean 25 mg, 25%, 25 °C or 25 years.
Preserve SI symbols and other recognized unit symbols unless the target publication uses a documented convention. Translate unit names in explanatory prose, but do not casually localize symbols such as kg, mm, °C or kWh.
If values are converted to another unit, update every dependent component: header, axis, caption, note, rounding and sometimes the chart scale. Unit conversion is a mathematical transformation, not merely a language edit.
13. Percentages and percentage points must stay distinct in visuals
A chart may show a rate rising from 20% to 30%. That is an increase of 10 percentage points and a relative increase of 50%. If a translated annotation says “increased by 10%,” it changes the quantitative claim.
Preserve the language used by the source and check whether a plotted difference is absolute or relative. Bar labels, callout bubbles and captions are common places where the distinction gets simplified incorrectly.
For detailed treatment, use Translate | Percentages, Percentage Points and Basis Points. Visual translation should carry that exact quantitative distinction into titles and annotations.
14. Missing values, zeros and blanks must remain semantically different
Tables and charts often use blank cells, dashes, NA, N/A, null, zero or special symbols. These do not necessarily mean the same thing. A dash may mean not applicable, not available, too small to report or suppressed for confidentiality.
Translate the legend or footnote that defines the symbol, but do not replace every non-number with zero. Zero is a measured or defined value; missingness is absence of usable data.
Use Translate | Missing Data, N/A, Null, Blank and Zero for the deeper semantic distinctions. In a visual, those distinctions must survive both language and formatting changes.
15. Error bars and confidence bands need accurate names
A vertical whisker may represent standard deviation, standard error, confidence interval, credible interval, range or another uncertainty measure. Never translate all of these as a generic “error range.”
Check the caption or methods section to identify what the bars represent. Preserve the confidence level if stated, such as 95% CI. If the graphic uses a shaded band, ensure the target caption still identifies it correctly.
Readers often overinterpret uncertainty graphics. A translation should not add claims such as “not significant because the bars overlap” unless the source makes them and the statistical conditions support them.
16. Figure captions are compact arguments and methods notes
A good figure caption can identify the population, variables, time period, method, statistical summary and visual conventions. Translation should preserve all of those functions rather than reducing the caption to a decorative title.
Watch scope carefully. “Bars show means; lines show 95% confidence intervals” assigns different meanings to two marks. Reordering clauses in the target language must not make the reader think the lines show means.
Captions often contain abbreviations defined nowhere else. Translate definitions consistently and preserve the abbreviation if the figure itself uses it. Otherwise the caption and graphic can stop matching.
17. Figure numbering and in-text references must stay synchronized
Translation projects may add, remove or reorder figures. If Figure 4 becomes Figure 5, every in-text “see Figure 4” reference must be updated. A mislabeled figure can send readers to the wrong evidence.
Use cross-reference fields where possible. Manual numbering is fragile, especially in long documents with many tables and appendices. Translation should not create a second, disconnected numbering system.
Keep prefixes such as Figure, Fig., Table, Appendix Figure or Supplementary Figure consistent with the target style. The number itself identifies the object; the translated label tells readers what kind of object it is.
18. Annotations should preserve direction, comparison and reference point
Charts frequently contain annotations such as “Peak,” “Policy introduced,” “Baseline,” “50% reduction” or “Above target.” These phrases depend on where the annotation sits and which point, line or region it references.
A target phrase may be longer and force the annotation box to move. Keep arrows, brackets and reference lines anchored correctly. If the box must move, the pointer should still terminate at the original data feature.
Do not change direction words casually. “Above baseline,” “below threshold,” “increase from baseline” and “decrease to target” describe different relationships. Visual position alone may not rescue an imprecise translation.
19. Color names should describe categories only when color is part of the meaning
Some visuals use color merely for decoration; others use it to encode categories, intensity or status. If the caption says “red bars indicate treatment,” translate the color word only if the actual bar remains red and color is intended as a navigational cue.
Localization or rebranding can change palette colors. If design changes from red to orange but the caption still says red, the translated visual becomes internally inconsistent. Text and visual encoding must be reviewed together.
For accessibility, avoid relying on color alone when the source provides other cues. Preserve labels, patterns, shapes or line styles that help readers with color-vision differences or monochrome printing.
20. Right-to-left languages may require visual reflow without reversing the data meaning
In right-to-left interfaces and documents, surrounding text direction may change while numeric axes, equations or chronological sequences follow their own conventions. Do not mirror a chart automatically without deciding what the horizontal direction means.
A timeline may still progress from earlier to later according to the target design convention; a mathematical x-axis may retain increasing values left to right; a table may reorder descriptive columns while numeric relationships remain fixed. The correct treatment depends on the content type.
Bidirectional punctuation and minus signs deserve special testing. A negative value that visually separates from its sign can become dangerous in financial, medical or engineering data.
21. Maps add geographic labels, scales and legends to the translation problem
Maps combine place names, region boundaries, scale bars, compass directions, legends and sometimes projections. Place names may have official target-language exonyms or internationally recognized local forms. Use authoritative geographic naming conventions when accuracy matters.
Do not translate a street or locality name word by word if that creates a place that does not exist in mapping systems. Preserve official names and add explanations where needed. A location label is partly language and partly geospatial identity.
Scale bars and distance units must remain mathematically correct. If miles are converted to kilometres, the graphic length, numerical labels and caption must all agree. A translated unit attached to an unconverted scale bar is wrong.
22. Dashboards contain interactive text beyond the visible chart
Interactive dashboards add filters, dropdowns, hover tooltips, button labels, date selectors, export commands and screen-reader descriptions. Translating only the static chart title leaves much of the user experience untranslated.
Tooltips often repeat values with fuller context. Verify that number formats, units and category names match the visible chart. A tooltip showing “0.25” while the axis shows “25%” may be valid only if the formatting logic is understood.
Filter labels can change the data displayed. If “All regions” is mistranslated as “Selected regions,” the interface language contradicts the query state. In dashboards, translation is part of interaction logic.
23. Embedded images require source files or careful recreation
When chart text is baked into a PNG or JPEG, translators cannot edit labels directly. The ideal workflow uses the original chart file or underlying data. Recreating the graphic from a screenshot increases the risk of changed positions, values and visual proportions.
If recreation is necessary, verify every number and geometry against the source. Do not approximate bar heights by eye. Rebuild from data where possible, then compare the result at the same scale.
Keep a record of whether the translated figure is a direct localization or a recreated visualization. This distinction matters for quality assurance because recreated graphics need numeric verification in addition to language review.
24. Accessibility text should describe the same evidence as the visual
Alt text and long descriptions are not secondary decoration. For readers who cannot see the graphic, they may be the primary route to the evidence. Translate them with the same attention to variables, comparisons, trends and uncertainty.
Do not describe every pixel. Identify the visual’s purpose and key message, then preserve important data relationships. If a table is already accessible in HTML, duplicating the entire table in alt text can be unnecessary and cumbersome.
W3C’s table guidance notes that structural markup helps assistive technology connect data cells to their headers. Translation should preserve those semantic structures so accessibility survives localization rather than becoming an afterthought.
25. Statistical terminology inside visuals must remain exact
Charts often compress statistical language into abbreviations: SD, SE, CI, OR, RR, HR, p, n and R². Preserve each statistic’s identity. Replacing a technical label with a vague word such as “variation” can erase the method.
Use surrounding context to distinguish similar terms. “Mean ± SD” is not “mean ± SE.” “95% CI” is not a 95% prediction interval. A visual can look unchanged while its statistical interpretation changes completely.
The recent eduKateSG specialist guides on confidence intervals, standard deviation, regression, p-values and risk measures can be used as companion references when a chart contains those concepts. This article protects the visual layer in which those statistics appear.
26. Worked example: a two-series line chart
Imagine a fictional chart titled “Reading Accuracy Over Eight Weeks.” The x-axis is Week 1 to Week 8. The y-axis is Correct Answers (%). A solid line represents guided practice and a dashed line represents independent practice. The final values are 88% and 81%.
A correct translation preserves the title, percentage unit, week sequence, legend mapping and line styles. A bad translation might reverse the legend terms, causing readers to conclude that independent practice reached 88%. The numbers have not changed, but the evidence has.
If the target labels are longer, direct labeling may require more space. The solution is controlled layout adjustment, not swapping series positions or changing dash patterns. Visual design must bend around meaning, not the reverse.
27. Worked example: a table with nested headers
Consider a fictional table comparing 2025 and 2026 test results. Each year spans three columns: Mean, Median and n. Rows show three grade levels. The top header is therefore a hierarchy, not six unrelated columns.
During translation, the word for “Median” is longer and forces a wrap. The correct solution preserves the three-column grouping under each year. If the cell border shifts and “n” appears under the wrong year, the table becomes structurally false.
After layout, check both visual grouping and programmatic header associations. A screen-reader user should hear the correct year and statistic for each value, not only see a visually plausible grid.
28. Worked example: a chart with missing values
Imagine a bar chart where one country has no observation and the data label shows “N/A.” Another country genuinely records 0. A note explains that N/A means no comparable data available. Translation must preserve the distinction.
If N/A is replaced with 0 for visual neatness, the chart says the country’s measured value is zero. If 0 is replaced with a dash, a real measurement disappears. The legend and note are part of the data model.
The safest release check is to compare the translated data object cell by cell or point by point with the source, not merely compare screenshots aesthetically.
29. A release checklist for translated visuals
Structure: Do row, column, group and series relationships match the source? Variables: Are axis names, measures and transformations correct? Units: Are symbols and conversions accurate? Legends: Does every label still map to the correct color, line, symbol or shape?
Numbers: Are values, signs, decimal separators and rounding preserved? Uncertainty: Are error bars, confidence intervals and notes identified correctly? Navigation: Do figure numbers and cross-references point to the right object? Accessibility: Do captions, headers, alt text and semantic relationships survive translation?
Meaning: Does the translated title make the same claim and no stronger one? Layout: Have longer labels created overlap or ambiguous pointers? Evidence: Could a reader infer the same trend, comparison and conclusion from both versions? If not, the visual needs repair.
30. Practice clinic: identify the hidden risk
Practice one: The y-axis says “Rate per 100,000.” The translation keeps only “Rate.” Risk: the denominator disappears. Practice two: Two legend labels are translated correctly but attached to opposite swatches. Risk: the series identities reverse.
Practice three: A table cell shows N/A and the translator enters 0. Risk: missingness becomes a measured zero. Practice four: A figure caption says “bars show medians,” but the translator writes “means.” Risk: the statistical summary changes.
Practice five: A chart title says “associated with” and the target says “caused by.” Risk: observational evidence becomes a causal claim. Practice six: An RTL layout mirrors a time series without reviewing chronology. Risk: the visual direction may imply time runs backward.
31. Frequently asked questions
Should chart numbers be translated? Values usually remain values, but number formatting may be localized. Any unit or currency conversion must be deliberate and mathematically correct.
Can I shorten axis labels? Yes only if the shortened form preserves variable, unit and necessary qualifiers. Move explanation to a caption or note rather than deleting meaning.
Do I translate abbreviations? Use the established target-language or international abbreviation for the field. Do not invent one simply to save space.
What if the original chart is inaccessible? Translation can be an opportunity to improve accessibility if the assignment allows it, but distinguish accessibility remediation from translation and preserve the underlying evidence.
What is the strongest final test? Hide the source text and ask a reviewer to explain the translated visual. If the explanation matches the source relationships, quantities and uncertainty, the translation has preserved the evidence.
32. Connect this specialist guide to the wider eduKateSG translation architecture
This article is a specialist branch of Master Art of Translation, not a competing general hub. It complements the existing numerical and statistical translation articles while preserving their individual ownership. For terminology learning and category precision, use the protected Vocabulary Learning Hub. For sentence scope, comparison language and claims in captions, use How English Works.
Visual translation succeeds when data relationships survive contact with another language. Preserve structure before style, variables before brevity, mappings before decoration and evidence before fluency. A translated table or chart should let the reader see the same world the source visual showed—no extra trend, no missing qualifier, no swapped category and no broken path from label to data.
Authoritative reference point
For accessible data-table structure, see the W3C Web Accessibility Initiative’s Tables Tutorial and its guidance on captions and summaries. The accessibility principle is also a translation principle: relationships that are obvious visually must still be represented explicitly enough that every reader and system can recover them.