The Guidelines Explorer was developed to make our corpus 52 data visualization guidelines accessible and actionable. Our goal is to create an interface that supports exploration, teaching, and practice, allowing users to interrogate guidelines at scale, retrieve practical advice quickly, and understand consensus and conflict across industries.
We’re grateful to DataVizStyleGuide.com for compiling the list of guidelines from which this dataset was derived. This is ongoing work intended as an educational resource. Please treat these as guides, not hard rules. Have fun on your journey to designing better visualizations!
Chart | Consensus Representative | Confidence | Actions |
|---|---|---|---|
Bar Chart USE · AXIS_ZERO | Start the axis at zero | Confidence 100% · 23 orgs · 7 industries | |
Bar Chart USE · BAR_CHART | Use a bar chart to show and compare categories and their values | Confidence 82% · 20 orgs · 5 industries | |
Bar Chart CONSIDER · ORDERING | Sort data from highest to lowest to enable quick comparison | Confidence 71% · 15 orgs · 6 industries | |
Bar Chart AVOID · BAR_CHART | Do not use a bar chart like a histogram | Confidence 64% · 14 orgs · 5 industries | |
Bar Chart LIMIT · COLOR_COUNT | Use consistent colours throughout the chart | Confidence 70% · 13 orgs · 7 industries | |
Bar Chart USE · COLOR | Use a lighter shade for projection/estimate bars to distinguish them from actual values | Confidence 55% · 11 orgs · 5 industries | |
Bar Chart USE · DIRECT_LABELS | Include a label on each bar; if a bar is too small, place its label outside the bar. | Confidence 45% · 9 orgs · 4 industries | |
Bar Chart CONSIDER · ALTERNATIVE_CHART | Use a table when the number of data points exceeds 6. | Confidence 41% · 8 orgs · 4 industries | |
Bar Chart AVOID · ROTATED_LABELS | Do not rotate bar labels | Confidence 37% · 8 orgs · 3 industries | |
Bar Chart ENSURE · SPACE_RATIO | Make each bar about twice as wide as the space between bars. | Confidence 34% · 7 orgs · 3 industries | |
Bar Chart AVOID · DECORATION | Do not add shadows behind bars or use three-dimensional vertical bars | Confidence 31% · 6 orgs · 3 industries | |
Bar Chart ORDER · SEGMENTS | Arrange clusters and the bars within them in a logical order | Confidence 21% · 4 orgs · 2 industries | |
Bar Chart LIMIT · CATEGORIES | Limit time series to 4 or fewer | Confidence 21% · 4 orgs · 2 industries | |
Bar Chart AVOID · GRIDLINES | Do not use gridlines and direct labels together; use one or the other | Confidence 22% · 3 orgs · 3 industries | |
Bar Chart USE · ABBREVIATION | If category labels are too long horizontally, consider using abbreviated labels | Confidence 22% · 3 orgs · 3 industries | |
Bar Chart RIGHT_ALIGN · HORIZONTAL_LABELS | Right-align horizontal labels to be closer to the horizontal bar | Confidence 22% · 3 orgs · 3 industries | |
Bar Chart ENSURE · SUM_TO_100 | Consider stacking bars to show proportions of datasets | Confidence 18% · 3 orgs · 2 industries | |
Bar Chart USE · LEGEND | Use a legend when there are multiple categories | Confidence 18% · 3 orgs · 2 industries |
AVOID||ABBREVIATIONENSURE||BAR_WIDTHHIGHLIGHT||BARENSURE||TOOLTIPS| Organization | Summary | Target | Strength |
|---|---|---|---|
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | omit the horizontal axis when values are labeled directly | AXIS Action: OMIT | MUST |
Cato Institute (CTO) NON-PROFIT | Do not use long labels for column charts. Rationale: Long labels don’t fit well below the columns of a column chart, especially if there are many of them. | LONG_LABELS Action: AVOID | MUST |
Delish (Kraft Heinz Food) (KHZ) FOOD | Include an x-axis on column charts to establish a baseline Rationale: to establish a baseline | AXIS Action: ADD | SHOULD |
Delish (Kraft Heinz Food) (KHZ) FOOD | Include a y-axis on bar charts to establish a baseline. Rationale: to establish a baseline | AXIS Action: ADD | SHOULD |
Government of Canada (CAN) GOVERNMENT | Use 60% opacity for negative bars while keeping the same colour | TRANSPARENCY Action: USE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Use 12px font size, #888888 fill, and Source Sans Pro for axis tick labels | TYPOGRAPHY Action: SET | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | set the x-axis stroke color to #888888 for the vertical bar chart variant | AXIS Action: SET | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Use grid lines when direct labelling isn't possible due to space Rationale: BECAUSE DIRECT LABELLING IS NOT POSSIBLE DUE TO SPACE | GRIDLINES Action: USE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Do not use a legend when there is only one data category. | LEGEND Action: AVOID | MUST |
Humanitarial Data Exchange (HDX) NON-PROFIT | Use date format DD Mmm YYYY for horizontal bar chart variant | DATE_FORMAT Action: USE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Do not sort the data in alphabetical order. | ORDERING Action: AVOID | MUST |
Humanitarial Data Exchange (HDX) NON-PROFIT | Do not use numeric or American-standard date formats; use proper date formats | DATE_FORMAT Action: USE | MUST |
Justice Innovation Lab (JIL) NON-PROFIT | Add error bars to show uncertainty in the data Rationale: to show uncertainty in the data (e.g., standard deviation, confidence interval) | ERROR_BARS Action: USE | SHOULD |
London City Intelligence (LDN) GOVERNMENT | Limit gridlines to just enough to frame the data | GRIDLINES Action: LIMIT | SHOULD |
London City Intelligence (LDN) GOVERNMENT | Group items using labels rather than using many color variations | LABELS Action: GROUP | SHOULD |
Material Design 2 (MTD) TECHNOLOGY | Allow subtle rounded corners on bars while ensuring the bar top precisely measures the bar's length Rationale: ensure the top of the bar precisely measures the bar’s length | BAR Action: CONSIDER | MAY |
Material Design 2 (MTD) TECHNOLOGY | Avoid shapes that make charts hard to read, such as bars with imprecise top edges. | SHAPE Action: AVOID | MUST |
National Institutes of Health (NIH) GOVERNMENT | Choose the primary and secondary x-axes based on which data relationships and comparisons should be highlighted Rationale: to highlight which data relationship and comparison will be most important for the reader | AXIS Action: SELECT | SHOULD |
National Institutes of Health (NIH) GOVERNMENT | Choose which category is primary (clusters) and which is secondary (subcategories) based on which comparisons or bar arrangements should be highlighted for the reader Rationale: to highlight for the reader which comparisons or bar arrangements are most important | SEGMENTS Action: SELECT | SHOULD |
Office for National Statistics (ONS) GOVERNMENT | Group bars into category-based groups with subheadings when bars belong to high-level categories to improve interpretability Rationale: adds structure and makes it easier for users to interpret values, especially when there are many bars | BAR Action: GROUP | MAY |
Office for National Statistics (ONS) GOVERNMENT | Use groups to show values for different breakdowns of a population (e.g., age, gender, ethnicity). | GROUP Action: USE | MAY |
Office for National Statistics (ONS) GOVERNMENT | Cluster together bars that the audience should compare or that have the smallest differences between values | BAR Action: GROUP | SHOULD |
OPattern (OPR) TECHNOLOGY | Draw attention to the most important aspect of the chart. | UNSPECIFIED Action: HIGHLIGHT | SHOULD |
OPattern (OPR) TECHNOLOGY | Include a descriptive caption (subtitle) for the horizontal bar chart when needed, written as a full sentence. | HEADINGS Action: ADD | MAY |
OPattern (OPR) TECHNOLOGY | Use light horizontal grid lines to guide the eye across multiple columns Rationale: to help guide the eye across multiple columns | GRIDLINES Action: USE | SHOULD |
OPattern (OPR) TECHNOLOGY | Identify the chart's most important aspect and call attention to it | UNSPECIFIED Action: HIGHLIGHT | SHOULD |
OPattern (OPR) TECHNOLOGY | Choose logical increments for the scale on vertical bar charts | SCALE Action: SET | SHOULD |
OPattern (OPR) TECHNOLOGY | Do not show more than 30 columns in a single chart | COLUMNS Action: LIMIT | MUST |
Pinterest (PIN) SOCIAL MEDIA | Show additional gridlines in bar charts; use vertical gridlines for row (horizontal) bar charts | GRIDLINES Action: ADD | SHOULD |
Pinterest (PIN) SOCIAL MEDIA | Keep labels short to avoid wrapping and improve readability Rationale: so that they don’t wrap and make it hard to read data | LABELS Action: CONCISE | SHOULD |
Pinterest (PIN) SOCIAL MEDIA | Do not create extra-long labels that require wrapping or truncation | LONG_LABELS Action: AVOID | MUST |
RedHat (RHT) TECHNOLOGY | Bar charts should be displayable either vertically or horizontally depending on the data and available space Rationale: dependent on the data and space at hand | BAR Action: SHOULD | SHOULD |
Semrush (SMR) TECHNOLOGY | Ensure the chart's axes are clear; add labels if the title isn't descriptive enough. | LABELS Action: USE | SHOULD |
Semrush (SMR) TECHNOLOGY | Consider a logical order for the values on the axes | AXIS Action: CONSIDER | MAY |
Semrush (SMR) TECHNOLOGY | Set the upper part of bars to have a border radius of 2px | BORDER Action: SET | SHOULD |
Semrush (SMR) TECHNOLOGY | Set a 4px margin between grouped bars Rationale: to avoid clutter | BAR_GAP Action: SET | SHOULD |
Semrush (SMR) TECHNOLOGY | Set a minimum bar height of 2px so small values remain visible next to large values Rationale: to keep small values visible alongside large ones | BAR_HEIGHT Action: SET | SHOULD |
Semrush (SMR) TECHNOLOGY | Consider using a logarithmic scale to make data comparisons more uniform, especially when there are outliers Rationale: for a more uniform data comparison | LOGARITHMIC_SCALE Action: CONSIDER | MAY |
Semrush (SMR) TECHNOLOGY | Do not include a legend for single-category bar charts | LEGEND Action: OMIT | MUST |
Semrush (SMR) TECHNOLOGY | Do not display bars for data points without values. | BAR Action: OMIT | MUST |
Semrush (SMR) TECHNOLOGY | Ensure clear margins and spacing (e.g., 8px top/bottom; 16px between category labels and bars) Rationale: for readability and to avoid clutter | SPACING Action: ENSURE | SHOULD |
Semrush (SMR) TECHNOLOGY | Omit axes when showing category values as a percentage of 100. | AXIS Action: OMIT | MUST |
Semrush (SMR) TECHNOLOGY | Use axes to display distribution without percentage constraints Rationale: for displaying distribution | AXIS Action: USE | SHOULD |
Semrush (SMR) TECHNOLOGY | Allocate space for category labels on both sides of the horizontal bar chart | HORIZONTAL_LABELS Action: PLACE | SHOULD |
Semrush (SMR) TECHNOLOGY | Show a 'no more results' label with an 8px margin below values and gray text | LABELS Action: ADD | SHOULD |
Semrush (SMR) TECHNOLOGY | Ensure the chart's axes are understandable; label them if needed. | AXIS Action: ENSURE | SHOULD |
Semrush (SMR) TECHNOLOGY | Do not use a grid for the compact horizontal bar chart variant | GRIDS Action: AVOID | MUST |
Semrush (SMR) TECHNOLOGY | Add a legend when there are multiple categories. | LEGEND Action: ADD | SHOULD |
Semrush (SMR) TECHNOLOGY | When using horizontal layout show values left-to-right; when using vertical layout show values bottom-to-top | AXIS Action: SET | MAY |
Semrush (SMR) TECHNOLOGY | Always name (label) the value. | LABELS Action: USE | MUST |
Semrush (SMR) TECHNOLOGY | Increase a sector by 2px on hover | SEGMENTS Action: HIGHLIGHT | SHOULD |
Semrush (SMR) TECHNOLOGY | Show zeros in the legend but omit zeros on the chart | LEGEND Action: LABEL | SHOULD |
Semrush (SMR) TECHNOLOGY | Display values less than or equal to 1% as 1% on the chart | LABELS Action: SET | SHOULD |
Semrush (SMR) TECHNOLOGY | When there is no data, mark data as n/a in the legend and tooltip. | LEGEND Action: LABEL | SHOULD |
Shopify (SHP) TECHNOLOGY | Set negative bars to 60% opacity | TRANSPARENCY Action: SET | SHOULD |
Shopify (SHP) TECHNOLOGY | Include tooltips that show x-axis and y-axis values | TOOLTIPS Action: ADD | SHOULD |
SONOS (SNS) TECHNOLOGY | Avoid large gaps between bars and sections in radial bar charts | BAR_GAP Action: AVOID | — |
The Dallas Morning News (DMN) JOURNALISM | Do not left-align labels for horizontal bar charts. | LEFT_ALIGN Action: AVOID | MUST |
U.S. Web Design System (USD) GOVERNMENT | Add a clear, plain-language summary (subtitle) explaining what the chart intends to communicate Rationale: Users may not understand some narrative objectives from a graphic alone; provide a plain-language explanation of what the chart intends to communicate. | HEADINGS Action: ADD | SHOULD |
U.S. Web Design System (USD) GOVERNMENT | Link the original data source for the line chart. | DATA_SOURCE Action: INCLUDE | SHOULD |
U.S. Web Design System (USD) GOVERNMENT | Consider hiding the graphic from screen readers and provide an accessible data table when the dataset is simple | UNSPECIFIED Action: CONSIDER | MAY |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Place the primary y-axis on the left when overlaying a line chart on a bar chart | DUAL_AXES Action: PLACE | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Do not include too many variables. | UNSPECIFIED Action: AVOID | MUST |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Do not use bar charts to compare heights when axes are on different scales | DUAL_AXES Action: AVOID | MUST |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Choose either an axis label or a data (direct) label, not both | LABELS Action: SELECT | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Order legend elements to match the sequence of bars for easy reference Rationale: for easy reference | LEGEND Action: ORDER | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Ensure there is sufficient space between groups of horizontal bars so groups are easily differentiated Rationale: in order to easily differentiate between the groups | SPACING Action: ENSURE | SHOULD |
US Agency for International Development | Office of HIV/AIDS (OHA) GOVERNMENT | Align chart text consistently | LABELS Action: CONSISTENT | SHOULD |
US Agency for International Development | Office of HIV/AIDS (OHA) GOVERNMENT | Avoid dual axes plots | DUAL_AXES Action: AVOID | SHOULD |
Chart | Consensus Representative | Confidence | Actions |
|---|---|---|---|
Line Chart USE · LINE_CHART | Use line charts to compare several data sets or to show changes over time | Confidence 100% · 15 orgs · 5 industries | |
Line Chart LIMIT · LINES | do not use more than 4 lines | Confidence 94% · 15 orgs · 4 industries | |
Line Chart STYLE · LINES | Consider styling lines using dashes or varied opacities | Confidence 86% · 12 orgs · 5 industries | |
Line Chart USE · AXIS_ZERO | Do not truncate the axis; use/start the axis at zero when the chart's point is visible with the axis at 0 | Confidence 67% · 8 orgs · 5 industries | |
Line Chart USE · DIRECT_LABELS | Label lines directly instead of using a separate legend when possible | Confidence 51% · 7 orgs · 3 industries | |
Line Chart USE · DATA_POINTS | Optionally show data points as dots on line charts | Confidence 51% · 7 orgs · 3 industries | |
Line Chart TRUNCATE · AXIS | Cut the y-axis (do not extend the y-axis to zero) to reveal subtle but significant changes | Confidence 52% · 6 orgs · 4 industries | |
Line Chart LIMIT · COLOR_COUNT | Do not use different colors to show periodical variation for the same data category | Confidence 46% · 6 orgs · 3 industries | |
Line Chart AVOID · LINES | Avoid lines that are too thick | Confidence 47% · 5 orgs · 4 industries | |
Line Chart AVOID · LINE_CHART | Do not use line charts to show and compare categorical data | Confidence 41% · 5 orgs · 3 industries | |
Line Chart USE · COLOR | Use a contrasting color | Confidence 41% · 5 orgs · 3 industries | |
Line Chart HIGHLIGHT · LINES | Highlight the most important aspect of the story in line charts | Confidence 37% · 4 orgs · 3 industries | |
Line Chart USE · AXIS | Make the chart axes clear; add labels when the chart name isn't sufficient | Confidence 37% · 4 orgs · 3 industries | |
Line Chart USE · GRIDLINES | Provide enough gridlines and use logical increments | Confidence 32% · 3 orgs · 3 industries | |
Line Chart CONSIDER · ALTERNATIVE_CHART | Use small multiples when displaying many categories | Confidence 32% · 3 orgs · 3 industries | |
Line Chart AVOID · DATA_POINTS | Avoid using data markers on line charts unless there are few points, irregular intervals, or flow data | Confidence 26% · 3 orgs · 2 industries | |
Line Chart AVOID · DUAL_AXES | Do not use dual axes to compare the evolution of different variables (multiple lines). | Confidence 26% · 3 orgs · 2 industries | |
Line Chart PLACE · LEGEND | Include a legend when there are multiple data series in a line chart | Confidence 26% · 3 orgs · 2 industries |
USE||SHAPE| Organization | Summary | Target | Strength |
|---|---|---|---|
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Use a 2:1 aspect ratio for the plot area | SPACE_RATIO Action: ENSURE | SHOULD |
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Use interactions to let users pick relevant categories when displaying many categories Rationale: to pick out what might be of most relevance to the end user | INTERACTIVITY Action: USE | SHOULD |
Consumer Financial Protection Bureau (CFP) GOVERNMENT | Label lines directly or use different patterns for each line | LINES Action: LABEL | SHOULD |
Delish (Kraft Heinz Food) (KHZ) FOOD | Do not overcrowd the chart with unnecessary gridlines | GRIDLINES Action: LIMIT | MUST |
Government of Canada (CAN) GOVERNMENT | Provide zoom in/out capability so users can focus on particular points in time on the chart | INTERACTIVITY Action: ADD | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Set the y-axis scale so the trend is visible and avoid scales that make the trend too flat or too exaggerated Rationale: so that we can see the trend | SCALE Action: SET | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Omit the legend when the chart shows only one category Rationale: A good title will suffice to understand the chart | LEGEND Action: AVOID | — |
Humanitarial Data Exchange (HDX) NON-PROFIT | Change date format to a user-friendly format. Rationale: Technical data formats such as the ISO standard (YYYY-MM-DD) might not be obvious for everyone, especially considering regional differences in writing the date. | DATE_FORMAT Action: USE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Order the legend to match the order of the end points | LEGEND Action: ORDER | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Consider merging smaller categories into an 'others' class so there are exactly four categories to improve readability Rationale: to have only four categories and ease reading | CATEGORIES Action: CONSIDER | MAY |
Humanitarial Data Exchange (HDX) NON-PROFIT | Do not plot more than 4 categories on a multiple-lines chart; if you must, use a small multiple. | CATEGORIES Action: LIMIT | MUST |
Humanitarial Data Exchange (HDX) NON-PROFIT | Do not place labels far from the lines (e.g., on top or bottom of the chart) because it forces readers to cross-reference legend and lines Rationale: readers will need to do extra work cross-referencing between the legend and the line | LONG_LABELS Action: AVOID | MUST |
Justice Innovation Lab (JIL) NON-PROFIT | Add reference lines or annotations for important events or points of interest where applicable. Rationale: for important events or points of interest | LINES Action: ADD | SHOULD |
Justice Innovation Lab (JIL) NON-PROFIT | Add marker points when the data sample is small to avoid implying continuity Rationale: to avoid the implication that a line represents more continuous data | DATA_POINTS Action: ADD | SHOULD |
Liferay (LFR) TECHNOLOGY | Use 2px borders to identify line charts Rationale: to identify line charts | BORDER Action: USE | SHOULD |
London City Intelligence (LDN) GOVERNMENT | Limit gridlines to the minimum needed to show the range and groupings of values Rationale: to show range and groups of values | GRIDLINES Action: LIMIT | SHOULD |
London City Intelligence (LDN) GOVERNMENT | Highlight data with a thematic colour and mark and label key dates and values | COLOR Action: HIGHLIGHT | SHOULD |
London City Intelligence (LDN) GOVERNMENT | Omit the legend because data are labelled directly Rationale: data is labelled directly | LEGEND Action: AVOID | MUST |
London City Intelligence (LDN) GOVERNMENT | Set axis text size to 16pt on the X-axis when including months and years Rationale: to accommodate including months as well as years on the X-axis | TYPOGRAPHY Action: SET | SHOULD |
National Institutes of Health (NIH) GOVERNMENT | Make x-axis labels horizontal to maximize readability Rationale: to maximize readability | HORIZONTAL_LABELS Action: ENSURE | SHOULD |
National Institutes of Health (NIH) GOVERNMENT | Make axis intervals equally spaced | SPACING Action: ENSURE | SHOULD |
National Institutes of Health (NIH) GOVERNMENT | Do not apply smoothing to trend lines Rationale: Interpolating lines distorts the data and can lead users to misinterpret the visual. | TREND_LINE Action: AVOID | MUST |
NZZ Visuals (NZZ) JOURNALISM | leave padding above the highest and below the lowest data point when truncating an axis and ensure the chart line uses the upper and lower halves of the chart | SPACE_RATIO Action: ENSURE | SHOULD |
Office for National Statistics (ONS) GOVERNMENT | Add comparison data (e.g., national average, five-year rolling average, or previous year) to provide context | TREND_LINE Action: ADD | SHOULD |
Office for National Statistics (ONS) GOVERNMENT | Add annotations to highlight significant events or data points Rationale: to highlight significant events or data points | LABELS Action: ADD | SHOULD |
RedHat (RHT) TECHNOLOGY | Consider creating and extending a best-fit (trend) line in both directions to project trends into the past or future, noting such projections may be uncertain Rationale: to project trends into the past or future | TREND_LINE Action: CONSIDER | MAY |
Salesforce (SLF) TECHNOLOGY | Ensure values are compared using similar units and a consistent scale | UNITS Action: ENSURE | SHOULD |
Semrush (SMR) TECHNOLOGY | Limit categories to 5–7 to avoid clutter and confusion Rationale: to prevent the chart from becoming cluttered and confusing | CATEGORIES Action: LIMIT | SHOULD |
Semrush (SMR) TECHNOLOGY | When hovering over the chart, show a detailed tooltip | TOOLTIPS Action: ADD | SHOULD |
Semrush (SMR) TECHNOLOGY | Show tooltips that display 'n/a' for missing data and, with many categories, show dots and values for all items under the cursor in the chart's category order. | TOOLTIPS Action: USE | SHOULD |
Semrush (SMR) TECHNOLOGY | Ensure tooltip category order matches the chart's category order | TOOLTIPS Action: ENSURE | SHOULD |
Shopify (SHP) TECHNOLOGY | Use larger time granularities such as yearly or quarterly | DATE_FORMAT Action: USE | SHOULD |
Sprout Social (SPR) SOCIAL MEDIA | Do not use inconsistent intervals (do not skip months, quarters, or other data points) | AXIS Action: AVOID | MUST |
Sprout Social (SPR) SOCIAL MEDIA | Right-align data labels and numerical values to the y-axis. | LABELS Action: RIGHT_ALIGN | SHOULD |
Sprout Social (SPR) SOCIAL MEDIA | Center data labels and place them above the corresponding data points | LABELS Action: CENTER | SHOULD |
U.S. Web Design System (USD) GOVERNMENT | Use discrete dash or datapoint styles to distinguish lines when high-contrast color selection is not possible | COLOR_PALETTE Action: STYLE | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Set the y-axis scale so the line height occupies roughly two-thirds of the chart area | SCALE Action: SET | SHOULD |
VTEX (VTX) TECHNOLOGY | Use grids so the audience can trace from the data to the axis Rationale: to help your audience trace their finger from the data to the axis | GRIDS Action: USE | SHOULD |
VTEX (VTX) TECHNOLOGY | Use clear, concise axis labels (abbreviate occasionally). | LABELS Action: USE | SHOULD |
VTEX (VTX) TECHNOLOGY | Avoid gridlines that visually compete with the data Rationale: prevent the grid from visually competing with the data | GRIDLINES Action: AVOID | SHOULD |
Chart | Consensus Representative | Confidence | Actions |
|---|---|---|---|
Donut Chart LIMIT · SEGMENTS | Use donut charts for datasets with a small number of categories (2–5). | Confidence 100% · 11 orgs · 6 industries | |
Donut Chart AVOID · DONUT_CHART | Do not place a multi-segment doughnut (with a legend to the right or beneath) in the same section as a single-segment doughnut. | Confidence 94% · 10 orgs · 6 industries | |
Donut Chart ENSURE · SUM_TO_100 | Choose either percentages or integer values to compare parts to the whole based on user needs and use case | Confidence 82% · 9 orgs · 5 industries | |
Donut Chart USE · DONUT_CHART | Use a donut chart to show a single percentage or numerical value | Confidence 70% · 7 orgs · 5 industries | |
Donut Chart CONSIDER · ALTERNATIVE_CHART | Consider using a bar chart when comparing one category to another | Confidence 57% · 5 orgs · 5 industries | |
Donut Chart USE · DIRECT_LABELS | Label segments directly. | Confidence 47% · 5 orgs · 3 industries | |
Donut Chart ORDER · CLOCKWISE | Display values in a clockwise direction | Confidence 45% · 4 orgs · 4 industries | |
Donut Chart USE · DONUT_CENTER | Place the chart value inside the chart circle for single animated segment doughnuts | Confidence 40% · 4 orgs · 3 industries | |
Donut Chart USE · LEGEND | Include a legend to comply with accessibility guidelines. | Confidence 35% · 4 orgs · 2 industries | |
Donut Chart USE · COLOR | Set the donut chart's unused area color to #EDEDED. | Confidence 29% · 3 orgs · 2 industries | |
Donut Chart SET · SEGMENTS | Set the outer segments as static and have them represent thresholds for the use case | Confidence 29% · 3 orgs · 2 industries |
| Organization | Summary | Target | Strength |
|---|---|---|---|
AVIVA (AVV) FINANCE | Use an animation that, when the chart first appears in the viewport, animates the doughnut clockwise to complete the circle | ANIMATION Action: USE | SHOULD |
AVIVA (AVV) FINANCE | When the key is to the right of the doughnut, set the block to consume six columns of the grid | COLUMNS Action: SET | MUST |
AVIVA (AVV) FINANCE | Place two doughnut charts with keys side-by-side using the full 12-column grid | COLUMNS Action: PLACE | MAY |
AVIVA (AVV) FINANCE | Use doughnut charts only on white backgrounds. | UNSPECIFIED Action: USE | SHOULD |
AVIVA (AVV) FINANCE | Set the numerical or percentage value in single animated-segment doughnuts to h1 semi-bold with color #5c596d | HEADINGS Action: SET | SHOULD |
AVIVA (AVV) FINANCE | Set the body copy under the numeric/percentage value to 16px in single animated segment doughnuts | TYPOGRAPHY Action: SET | SHOULD |
AVIVA (AVV) FINANCE | Allow placing elements (title, total, CTA/text-link, or copy) inside the donut's key lock-up | UNSPECIFIED Action: PLACE | MAY |
AVIVA (AVV) FINANCE | Place no more than three doughnut charts side by side when needed | CHART_TYPE Action: LIMIT | MAY |
AVIVA (AVV) FINANCE | Show the full dataset first, then use subsequent doughnut charts to highlight a single segment from the first chart. | SEGMENTS Action: HIGHLIGHT | SHOULD |
AVIVA (AVV) FINANCE | Show a legend only for the single highlighted segment in doughnut charts | LEGEND Action: LIMIT | MUST |
AVIVA (AVV) FINANCE | Do not change the blank segment's color; keep it as #ccc for single animated-segment doughnuts | COUNT Action: SET | MUST |
AVIVA (AVV) FINANCE | Do not place a legend (key) to the right or beneath alongside doughnuts that have numerical/percentage values inside them | LEGEND Action: AVOID | MUST |
AVIVA (AVV) FINANCE | Require a 3px divider between each doughnut segment to meet accessibility standards Rationale: to ensure the component meets accessibility standards | STROKE_WIDTH Action: SET | MUST |
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Adjust the donut chart's hole size (space ratio) | SPACE_RATIO Action: ENSURE | SHOULD |
Consumer Financial Protection Bureau (CFP) GOVERNMENT | Use a white outline or stroke to create contrast between slices Rationale: to create contrast between the slices | BORDER Action: USE | SHOULD |
Elastic UI (ELC) TECHNOLOGY | When there are more than six slices, group smaller/overflow slices into a single "Other" category Rationale: grouping could end up being the largest category and therefore obscure the meaning of the chart | SEGMENTS Action: GROUP | SHOULD |
Elastic UI (ELC) TECHNOLOGY | Start slices at the 12 o'clock position with the largest slice at 12 and the remaining slices ordered counterclockwise in descending order | ORDERING Action: CONSIDER | SHOULD |
Elastic UI (ELC) TECHNOLOGY | Follow the natural order of categories (e.g., low to high or good to bad). | SEGMENTS Action: ORDER | SHOULD |
Elastic UI (ELC) TECHNOLOGY | Do not enlarge or explode slices Rationale: leads to errors in understanding | SEGMENTS Action: AVOID | MUST |
Elastic UI (ELC) TECHNOLOGY | Do not use too many colors in a single chart because it hinders understanding. Rationale: will hinder understanding | COLOR_COUNT Action: LIMIT | MUST |
London City Intelligence (LDN) GOVERNMENT | Label the donut chart to indicate what the entire donut represents | HEADINGS Action: USE | SHOULD |
London City Intelligence (LDN) GOVERNMENT | ensure the donut's ring-to-hole proportion is neither too skinny nor too thick | SPACE_RATIO Action: ENSURE | SHOULD |
London City Intelligence (LDN) GOVERNMENT | Use a single colour and include labels to highlight the narrative in the text Rationale: to highlight narrative in text | COLOR_COUNT Action: LIMIT | SHOULD |
RedHat (RHT) TECHNOLOGY | Use the chart center to highlight a data point | DATA_POINTS Action: USE | SHOULD |
RedHat (RHT) TECHNOLOGY | Provide 3px of padding between segments | SPACING Action: SET | MUST |
RedHat (RHT) TECHNOLOGY | Show a tooltip on hover that displays the segment name and its value. | TOOLTIPS Action: USE | SHOULD |
RedHat (RHT) TECHNOLOGY | Round the total numeric value to at most two decimal places and limit it to 14 characters; style it using 24px font in standard text color. | PRECISE_NUMBER Action: SET | SHOULD |
RedHat (RHT) TECHNOLOGY | Data set label must be at most 24 characters | LONG_LABELS Action: AVOID | MUST |
RedHat (RHT) TECHNOLOGY | Center labels within the donut | LABELS Action: CENTER | SHOULD |
RedHat (RHT) TECHNOLOGY | Place labels outside the donut when they exceed the maximum character count and leave the center empty | LONG_LABELS Action: PLACE | SHOULD |
RedHat (RHT) TECHNOLOGY | Allow using percentages or whole numbers to represent utilization | UNITS Action: USE | MAY |
RedHat (RHT) TECHNOLOGY | Display the percentage of data utilized in the tooltip for a utilization donut chart | TOOLTIPS Action: ADD | — |
RedHat (RHT) TECHNOLOGY | State each segment's name and its utilization value | SEGMENTS Action: LABEL | SHOULD |
RedHat (RHT) TECHNOLOGY | Provide 3px of padding between each segment. | SPACING Action: SET | SHOULD |
RedHat (RHT) TECHNOLOGY | State the threshold name, the segment name, and the value being represented. | LABELS Action: USE | SHOULD |
Semrush (SMR) TECHNOLOGY | Start displaying values at a 90-degree angle | UNSPECIFIED Action: START | SHOULD |
Semrush (SMR) TECHNOLOGY | Wrap long labels to the next line for clarity Rationale: for clarity | LONG_LABELS Action: AVOID | SHOULD |
Semrush (SMR) TECHNOLOGY | Always name (label) the main metric. | LABELS Action: USE | MUST |
Semrush (SMR) TECHNOLOGY | Display name and value in tooltips | TOOLTIPS Action: ADD | SHOULD |
Semrush (SMR) TECHNOLOGY | Display values less than or equal to 1% as 1% on the chart | PRECISE_NUMBER Action: AVOID | SHOULD |
The Economist (ECN) JOURNALISM | When linking lines get too crowded, add small colour blocks to labels to key them | LABELS Action: ADD | SHOULD |
The Urban Institute (UBI) NON-PROFIT | Aggregate smaller categories into an "other" or "miscellaneous" category Rationale: to make pie charts with many categories legible | SEGMENTS Action: GROUP | SHOULD |
The Urban Institute (UBI) NON-PROFIT | Consider using 25° increments in the donut chart (they create right angles and a straight center line familiar to readers). | UNSPECIFIED Action: CONSIDER | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Omit the legend and instead label slices directly | LEGEND Action: OMIT | MUST |
Chart | Consensus Representative | Confidence | Actions |
|---|---|---|---|
Stacked Bar Chart USE · STACKED_BAR_CHART | Use a stacked bar chart to show and compare categorical data when there is more than one variable | Confidence 93% · 8 orgs · 3 industries | |
Stacked Bar Chart USE · COLOR | Use distinctly different colors to improve clarity | Confidence 83% · 6 orgs · 4 industries | |
Stacked Bar Chart AVOID · STACKED_BAR_CHART | Avoid stacked bar charts; prefer grouped bar charts because grouped bars are easier to compare from a common baseline | Confidence 66% · 5 orgs · 3 industries | |
Stacked Bar Chart LIMIT · SEGMENTS | Use stacked bar chart only with 5 or fewer segments | Confidence 66% · 5 orgs · 3 industries | |
Stacked Bar Chart ENSURE · SUM_TO_100 | Use stacked bar charts to show how parts contribute to a whole | Confidence 57% · 4 orgs · 3 industries | |
Stacked Bar Chart LIMIT · CATEGORIES | Limit stacked bar chart to two or three categories | Confidence 49% · 3 orgs · 3 industries | |
Stacked Bar Chart ORDER · SEGMENTS | Order subcategories consistently so each column has the same subcategory and color ordering | Confidence 49% · 3 orgs · 3 industries | |
Stacked Bar Chart USE · AXIS_ZERO | Use a zero baseline for bar charts | Confidence 49% · 3 orgs · 3 industries | |
Stacked Bar Chart LIMIT · COLOR_COUNT | Use variations of a single color for stacked bar chart segments for ordinal variables | Confidence 49% · 3 orgs · 3 industries | |
Stacked Bar Chart CONSIDER · ALTERNATIVE_CHART | Recommend using a stacked bar chart as an alternative to multi-tier pie (sunburst) charts | Confidence 41% · 3 orgs · 2 industries |
CONSIDER||ORDERING| Organization | Summary | Target | Strength |
|---|---|---|---|
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Place the most important category at the bottom of the plot area and highlight it | SEGMENTS Action: PLACE | SHOULD |
Consumer Financial Protection Bureau (CFP) GOVERNMENT | Use a white line or stroke to create contrast between bar chunks Rationale: to create contrast between bar chunks | BORDER Action: USE | SHOULD |
Elastic UI (ELC) TECHNOLOGY | Use a horizontal layout when category labels need more space | HORIZONTAL_LABELS Action: USE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Use interactivity to allow users to focus/select and display only one category to improve readability Rationale: making it easier to read | INTERACTIVITY Action: USE | MAY |
Humanitarial Data Exchange (HDX) NON-PROFIT | Place the legend on top where it is most visible Rationale: gives key information to understand the chart; therefore must be placed where it is most visible | LEGEND Action: PLACE | MUST |
Humanitarial Data Exchange (HDX) NON-PROFIT | Ensure legend entries follow the same sequence as the chart | LEGEND Action: ORDER | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Add legends only when there are two or more categories | LEGEND Action: ADD | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Do not use acronyms or jargon in axis labels | ABBREVIATION Action: AVOID | MUST |
Humanitarial Data Exchange (HDX) NON-PROFIT | Add a vertical scroll bar to the chart container when the data list is long and space is limited | SCROLL_BAR Action: ADD | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Use date format DD Mmm YYYY for stacked bar charts | DATE_FORMAT Action: USE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Add direct labels on top showing the minimum and maximum values (0% and 100%) | DIRECT_LABELS Action: USE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Round numbers up or down in 100% stacked bar charts to ease reading Rationale: to ease reading | PRECISE_NUMBER Action: TRUNCATE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Include spelled-out names of acronyms below the chart when acronyms are used Rationale: so that reader can easily see it | ABBREVIATION Action: LABEL | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Use date format DD Mmm YYYY to make date values user-friendly and avoid confusion. Rationale: Using the three-letter abbreviation for month makes the date value user-friendly and avoids confusion. | DATE_FORMAT Action: USE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Do not use acronyms in charts; prefer full names. In text, spell out acronyms on first use and include the acronym in parentheses. | ABBREVIATION Action: AVOID | MUST |
Humanitarial Data Exchange (HDX) NON-PROFIT | Do not sort the data in alphabetical order Rationale: to stay 'neutral' | ORDERING Action: AVOID | MUST |
Humanitarial Data Exchange (HDX) NON-PROFIT | Do not use ambiguous numeric date formats like '01-04-2020'; use proper date formats. Rationale: Depending on the country, '01-04-2020' could be interpreted as 4 January 2020 or 1 April 2020; avoid confusion. | DATE_FORMAT Action: AVOID | MUST |
Justice Innovation Lab (JIL) NON-PROFIT | Ensure stacked bar segments are separated by at least 1 pt white space to improve readability. Rationale: to improve readability | BAR_GAP Action: ENSURE | SHOULD |
Justice Innovation Lab (JIL) NON-PROFIT | Use black or white text for data labels to ensure sufficient contrast with bar colors Rationale: ensure sufficient contrast between text and bar colors | LABELS Action: USE | SHOULD |
Liferay (LFR) TECHNOLOGY | Start stacked bar segments left-to-right for horizontal bars and bottom-to-top for vertical bars | SEGMENTS Action: START | MUST |
London City Intelligence (LDN) GOVERNMENT | Label each segment directly with its value Rationale: Comparing categories is tricky because baseline shifts | SEGMENTS Action: LABEL | SHOULD |
London City Intelligence (LDN) GOVERNMENT | If showing a single variable, set the background transparency to 100% | TRANSPARENCY Action: SET | SHOULD |
National Institutes of Health (NIH) GOVERNMENT | Display the total for each bar above the bar | DIRECT_LABELS Action: USE | SHOULD |
Office for National Statistics (ONS) GOVERNMENT | Avoid overcrowding a single bar with too many segments | SEGMENTS Action: AVOID | SHOULD |
Pajamas Design System (PAJ) TECHNOLOGY | Stacked columns can be symmetric or asymmetric; the number of stacks may vary across groups | SEGMENTS Action: CONSIDER | MAY |
Pajamas Design System (PAJ) TECHNOLOGY | use graded transparency to highlight differences in stacked variables and differentiate stacks from groups Rationale: to highlight differences in stacked variables while still differentiating stacks from groups | TRANSPARENCY Action: USE | MAY |
Pajamas Design System (PAJ) TECHNOLOGY | Use specific colors sparingly and follow general color guidelines for data visualizations. | COLOR Action: LIMIT | SHOULD |
Pajamas Design System (PAJ) TECHNOLOGY | Group and stack columns in the same chart when there are three dimensions of data | BAR Action: GROUP | MAY |
Semrush (SMR) TECHNOLOGY | Make the chart large enough to easily read the data Rationale: to easily read the data | CHART_SIZE Action: ENSURE | SHOULD |
Semrush (SMR) TECHNOLOGY | Do not include gaps between value segments in stacked bars | COLOR_PALETTE Action: AVOID | SHOULD |
Semrush (SMR) TECHNOLOGY | Ensure at least a 20% margin between bars to avoid clutter Rationale: to avoid clutter | BAR_GAP Action: ENSURE | SHOULD |
Semrush (SMR) TECHNOLOGY | Highlight a bar on hover to indicate focus or clickability Rationale: indicating focus or clickability | BAR Action: HIGHLIGHT | SHOULD |
Semrush (SMR) TECHNOLOGY | Choose contrasting colors for different categories | COLOR_PALETTE Action: SELECT | SHOULD |
SONOS (SNS) TECHNOLOGY | Use bold typography | TYPOGRAPHY Action: USE | SHOULD |
SONOS (SNS) TECHNOLOGY | Do not include gaps between sections in stacked bar charts | BAR_GAP Action: AVOID | MUST |
SONOS (SNS) TECHNOLOGY | Align the section label to the bottom-left corner and use regular font weight | HEADINGS Action: LEFT_ALIGN | SHOULD |
SONOS (SNS) TECHNOLOGY | Order the bars by size | BAR Action: ORDER | SHOULD |
SONOS (SNS) TECHNOLOGY | Place labels aligned outside the top bar for the stacked fan bar chart variant | LABELS Action: PLACE | SHOULD |
SONOS (SNS) TECHNOLOGY | Change the rotation of labels when the bar angle passes 90° for the stacked fan bar chart variant | ROTATED_LABELS Action: AVOID | SHOULD |
SONOS (SNS) TECHNOLOGY | Left-align the chart title to the outermost axis | HEADINGS Action: LEFT_ALIGN | SHOULD |
SONOS (SNS) TECHNOLOGY | Use a dotted circular axis | AXIS Action: USE | SHOULD |
The Economist (ECN) JOURNALISM | Label each segment value on stacked bars when there are few categories or labeling issues | SEGMENTS Action: LABEL | MAY |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Order legend elements in the same sequence as the bars | LEGEND Action: ORDER | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Sort the data by total value in descending order for stacked bar charts of categorical (non-ordinal) variables | DESCENDING Action: ORDER | SHOULD |
Chart | Consensus Representative | Confidence | Actions |
|---|---|---|---|
Scatterplot ENSURE · DATA_POINTS | Ensure you are counting the correct variable when showing correlations in a scatterplot | Confidence 100% · 5 orgs · 4 industries | |
Scatterplot SET · AXIS | Set a maximum value on the x and y axes to remove outliers and highlight the trend in the data | Confidence 100% · 5 orgs · 4 industries | |
Scatterplot USE · SCATTERPLOT | Use a scatterplot to show an x-y relationship between data points | Confidence 93% · 5 orgs · 3 industries | |
Scatterplot USE · COLOR | Allow using color alone to distinguish a categorical variable on bubble charts only in rare cases with compelling patterns and clear comprehension | Confidence 78% · 4 orgs · 3 industries | |
Scatterplot USE · AXIS_ZERO | Use a baseline of zero for the x-axis and y-axis | Confidence 78% · 4 orgs · 3 industries | |
Scatterplot USE · TRANSPARENCY | Use transparency to show point density when many points overlap in a scatterplot | Confidence 78% · 4 orgs · 3 industries | |
Scatterplot CONSIDER · TREND_LINE | Sometimes consider showing a trend (regression) line | Confidence 65% · 3 orgs · 3 industries | |
Scatterplot PLACE · HEADINGS | Summarize dimensions in a highly visible place (e.g., subtitle) to lower the barrier to entry | Confidence 57% · 3 orgs · 2 industries | |
Scatterplot USE · LABELS | When annotations are long and need more space, place labels outside the chart and use connection lines to link them to the points | Confidence 50% · 3 orgs · 1 industry |
AVOID||OVERPLOTTING| Organization | Summary | Target | Strength |
|---|---|---|---|
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Add a third measure to a scatterplot using color, shape, or size (e.g., bubble chart). | ALTERNATIVE_CHART Action: CONSIDER | MAY |
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Use white gridlines to help read point positions Rationale: to help read point positions | GRIDLINES Action: USE | SHOULD |
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Use subtle line thickness to indicate the state and end of time series (thicker at the start and thinner at the end) Rationale: to indicate the state and end of time series | LINES Action: STYLE | SHOULD |
Government of Canada (CAN) GOVERNMENT | Avoid using trend lines unless they accurately represent a strong correlation. | TREND_LINE Action: AVOID | MUST |
Justice Innovation Lab (JIL) NON-PROFIT | Use both marker shape and color to differentiate groups for categorical variables Rationale: to differentiate groups | SHAPE Action: USE | SHOULD |
Justice Innovation Lab (JIL) NON-PROFIT | Add annotations describing data points of interest when applicable. Rationale: to describe data points of interest | DATA_POINTS Action: ADD | SHOULD |
Justice Innovation Lab (JIL) NON-PROFIT | Label groups directly to avoid using a separate legend when possible Rationale: to avoid use of a separate legend | DIRECT_LABELS Action: USE | SHOULD |
Justice Innovation Lab (JIL) NON-PROFIT | Ensure the area of circular markers scales with the data value when using size/bubble charts | SCALE Action: ENSURE | MUST |
MailChimp (MCP) TECHNOLOGY | Use multiple marker shapes for different sets/categories and cycle through shapes in the order circle, square, triangle, diamond, upside-down triangle Rationale: so that the data can be more easily differentiated | SHAPE Action: USE | SHOULD |
NZZ Visuals (NZZ) JOURNALISM | Annotate data points directly when those labels do not obscure other important data | DATA_POINTS Action: LABEL | SHOULD |
NZZ Visuals (NZZ) JOURNALISM | Do not draw extra elements to highlight groups because they clutter the chart Rationale: it tends to unnecessarily clutter the chart | DECORATION Action: AVOID | MUST |
Salesforce (SLF) TECHNOLOGY | Do not show outliers unless color variations are identified | DATA_POINTS Action: AVOID | MUST |
Semrush (SMR) TECHNOLOGY | Provide clear labels for the X and Y axes and do not color the labels to keep the chart readable. Rationale: to keep the chart readable | AXIS Action: LABEL | SHOULD |
Semrush (SMR) TECHNOLOGY | Use a legend when datasets use different/varying colors | LEGEND Action: USE | SHOULD |
Semrush (SMR) TECHNOLOGY | Add a legend for charts with multiple datasets and favor a vertical layout for easier reading and comparing values Rationale: for easier reading and values comparing | LEGEND Action: ADD | SHOULD |
Semrush (SMR) TECHNOLOGY | Limit the number of datasets to keep the chart readable. Rationale: to keep the chart readable | SEGMENTS Action: LIMIT | SHOULD |
Semrush (SMR) TECHNOLOGY | Increase dots' opacity to 80% on hover | DATA_POINTS Action: HIGHLIGHT | SHOULD |
Semrush (SMR) TECHNOLOGY | Highlight X and Y axis values in tooltips | TOOLTIPS Action: HIGHLIGHT | SHOULD |
Semrush (SMR) TECHNOLOGY | Avoid coloring axis labels Rationale: can make the data harder to read | LABELS Action: AVOID | SHOULD |
Storymaps Arc GIS (AGS) TECHNOLOGY | Add a regression/trend line to show the relationship between the two variables Rationale: to show the relationship between the two variables | TREND_LINE Action: ADD | SHOULD |
Storymaps Arc GIS (AGS) TECHNOLOGY | Add a p-value to the scatterplot | PRECISE_NUMBER Action: ADD | SHOULD |
Storymaps Arc GIS (AGS) TECHNOLOGY | Show exactly one group per graph | CATEGORIES Action: LIMIT | SHOULD |
Storymaps Arc GIS (AGS) TECHNOLOGY | Show only one group per graph | CATEGORIES Action: LIMIT | SHOULD |
Storymaps Arc GIS (AGS) TECHNOLOGY | When showing more than one grouping, display them in two separate graphs unless the chart is for showing clustering relationships | ALTERNATIVE_CHART Action: CONSIDER | SHOULD |
The Economist (ECN) JOURNALISM | Make x and y axis ticks the same weight and colour; use black only for the zero baseline | AXIS Action: CONSISTENT | SHOULD |
The Economist (ECN) JOURNALISM | When color categories are hard to distinguish, consider highlighting the most significant part of the story | DATA_POINTS Action: HIGHLIGHT | MAY |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Use an arrowed line on connected scatterplots to show direction when a third ordered variable (often time) is assigned Rationale: TO INDICATE THE DIRECTION OF EVOLUTION | LINES Action: STYLE | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Use an appropriate measurement interval | UNSPECIFIED Action: USE | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Do not interpret correlation as causation. | UNSPECIFIED Action: AVOID | MUST |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | do not use scatterplots to display more than two numeric variables | UNSPECIFIED Action: AVOID | MUST |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Don't: in a scatterplot, we can not only see the values through individual data points but also patterns when the data are taken as a whole. | UNSPECIFIED Action: AVOID | MUST |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Don't assume a single characterization of relationships — they can be positive or negative, strong or weak, linear or nonlinear. | UNSPECIFIED Action: AVOID | MUST |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Do not use scatterplots to observe the relationship or correlation between two numeric variables | CHART_TYPE Action: AVOID | MUST |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Add a regression (trend) line to help the analysis Rationale: to help the analysis | TREND_LINE Action: ADD | MAY |
US Agency for International Development | Office of HIV/AIDS (OHA) GOVERNMENT | Use reference lines or areas to provide context. Rationale: to provide context | GRIDLINES Action: USE | SHOULD |
Chart | Consensus Representative | Confidence | Actions |
|---|---|---|---|
Pie Chart AVOID · PIE_CHART | Do not use a pie chart if aggregating all but the most important segment into "others" leaves the chart nonsensical | Confidence 96% · 12 orgs · 6 industries | |
Pie Chart USE · PIE_CHART | Use a pie chart to compare a set of values to a whole | Confidence 88% · 10 orgs · 7 industries | |
Pie Chart LIMIT · SEGMENTS | Do not show more than 5 pie chart segments | Confidence 78% · 9 orgs · 6 industries | |
Pie Chart ENSURE · SUM_TO_100 | Use pie charts to highlight how small or how large one part of a whole is. | Confidence 72% · 8 orgs · 6 industries | |
Pie Chart CONSIDER · ALTERNATIVE_CHART | Prefer bar, line, or stacked area charts over pie charts to show change over time | Confidence 46% · 5 orgs · 4 industries | |
Pie Chart ORDER · CLOCKWISE | Start the pie segment at the top (12 o'clock) and arrange segments clockwise | Confidence 46% · 5 orgs · 4 industries | |
Pie Chart USE · COLOR | Use pie charts only on white backgrounds. | Confidence 40% · 4 orgs · 4 industries | |
Pie Chart USE · DIRECT_LABELS | Place callouts outside the pie | Confidence 36% · 4 orgs · 3 industries |
LIMIT||COLOR_COUNTUSE||LEGEND| Organization | Summary | Target | Strength |
|---|---|---|---|
AVIVA (AVV) FINANCE | Animate the pie chart clockwise when it first appears, completing the circle | ANIMATION Action: START | SHOULD |
AVIVA (AVV) FINANCE | Allow the chart to have between 2 and 5 segments | SEGMENTS Action: ENSURE | MAY |
AVIVA (AVV) FINANCE | Ensure the legend's colours match the corresponding pie chart segments | LEGEND Action: ENSURE | MUST |
AVIVA (AVV) FINANCE | Place up to three pie charts side by side when needed; place keys below them in that case. | COLUMNS Action: PLACE | MAY |
AVIVA (AVV) FINANCE | Require a 3px divider (stroke) between each pie segment Rationale: to ensure the component meets accessibility standards | STROKE_WIDTH Action: SET | MUST |
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Do not use more than three categories in a pie chart | CATEGORIES Action: LIMIT | SHOULD |
Delish (Kraft Heinz Food) (KHZ) FOOD | Use color to highlight the most important category if there is one. | COLOR Action: HIGHLIGHT | SHOULD |
Delish (Kraft Heinz Food) (KHZ) FOOD | Make one color more prominent than the others | COLOR Action: HIGHLIGHT | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Sort the data and display values from largest to smallest | DESCENDING Action: ORDER | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Do not use 3D effects on pie charts | DECORATION Action: AVOID | MUST |
Office for National Statistics (ONS) GOVERNMENT | Do not use more than 6 categories in a pie chart Rationale: can make the chart difficult to interpret | CATEGORIES Action: LIMIT | MUST |
OPattern (OPR) TECHNOLOGY | Start the main pie slice at 12 o’clock | AXIS_ZERO Action: USE | SHOULD |
RedHat (RHT) TECHNOLOGY | Use pie charts for at most 5 data points | DATA_POINTS Action: LIMIT | MAY |
RedHat (RHT) TECHNOLOGY | Include each variable's current value in the legend | LEGEND Action: LABEL | SHOULD |
Sprout Social (SPR) SOCIAL MEDIA | Use a 1px stroke between pie sections when it improves clarity between similar colors Rationale: TO ADD VISUAL CLARITY BETWEEN SIMILAR COLORS | STROKE_WIDTH Action: USE | SHOULD |
TASO (TSO) NON-PROFIT | Do not use many segments or segments with values that are close together. Rationale: It'll make the chart particularly difficult to read. | LABELS Action: PLACE | MUST |
The Dallas Morning News (DMN) JOURNALISM | Set the pie diameter to 7 picas for one-column charts | CHART_SIZE Action: SET | SHOULD |
Chart | Consensus Representative | Confidence | Actions |
|---|---|---|---|
Area Chart USE · AREA_CHART | Use area charts to show multiple categories over time. | Confidence 100% · 9 orgs · 3 industries | |
Area Chart AVOID · AREA_CHART | Avoid overlapping area charts when there are more than two time series because they can obscure the data. | Confidence 77% · 6 orgs · 3 industries | |
Area Chart USE · AXIS_ZERO | Start the Y-axis at zero when there is more than one series | Confidence 77% · 6 orgs · 3 industries | |
Area Chart LIMIT · CATEGORIES | Limit time series in area charts to 8 or fewer | Confidence 51% · 4 orgs · 2 industries | |
Area Chart USE · COLOR | Use contrasting colours for each individual category. | Confidence 53% · 3 orgs · 3 industries |
| Organization | Summary | Target | Strength |
|---|---|---|---|
Cato Institute (CTO) NON-PROFIT | Make the title short. | HEADINGS Action: CONCISE | SHOULD |
Cato Institute (CTO) NON-PROFIT | Make subtitles short and capitalize the first word. | HEADINGS Action: CAPITALIZE | SHOULD |
Cato Institute (CTO) NON-PROFIT | Place the legend at the bottom of the chart | LEGEND Action: PLACE | SHOULD |
Government of Canada (CAN) GOVERNMENT | use lower opacity when series overlap so all series are visible Rationale: so all series can be seen | TRANSPARENCY Action: USE | SHOULD |
Government of Canada (CAN) GOVERNMENT | Set area fill to 15% opacity | TRANSPARENCY Action: SET | SHOULD |
Liferay (LFR) TECHNOLOGY | use 10% opacity for area chart background colors Rationale: to identify Area Charts | TRANSPARENCY Action: SET | SHOULD |
Liferay (LFR) TECHNOLOGY | Use the same elements as Line Charts for borders and shapes | BORDER Action: USE | SHOULD |
Material Design 2 (MTD) TECHNOLOGY | Use an area chart to summarize relationships between datasets and show how parts relate to the whole Rationale: to summarize relationships between datasets and show how individual data points relate to a whole | SUM_TO_100 Action: ENSURE | SHOULD |
National Institutes of Health (NIH) GOVERNMENT | Place the largest contributing series at the bottom of the area chart based on its value at the start of the time period shown. | AREA_STACK_ORDER Action: PLACE | SHOULD |
National Institutes of Health (NIH) GOVERNMENT | Use equally sized bins to summarize the distribution Rationale: to create a meaningful summary of the distribution; bins that are too large or too small may fail to show variation in frequency | BINS Action: USE | SHOULD |
RedHat (RHT) TECHNOLOGY | Consider stacking area charts to compare more than one continuous data sets. Rationale: to compare more than one continuous data sets | ALTERNATIVE_CHART Action: CONSIDER | MAY |
RedHat (RHT) TECHNOLOGY | Present the area fill below the data line | UNSPECIFIED Action: PLACE | — |
RedHat (RHT) TECHNOLOGY | Use the chart tooltip to drill into data for any data point on an area chart Rationale: to drill into the data related to any data point | TOOLTIPS Action: USE | SHOULD |
Semrush (SMR) TECHNOLOGY | Ensure the chart's axes are clearly labeled for easy understanding Rationale: for easy understanding of the axes | AXIS Action: LABEL | SHOULD |
Semrush (SMR) TECHNOLOGY | Display dots on line charts when there are few data points or the data are collected irregularly | DATA_POINTS Action: ADD | SHOULD |
Semrush (SMR) TECHNOLOGY | Highlight the nearest data point when hovering over the chart | DATA_POINTS Action: HIGHLIGHT | SHOULD |
Semrush (SMR) TECHNOLOGY | Show a dot when the chart has a single data point | DATA_POINTS Action: USE | SHOULD |
Semrush (SMR) TECHNOLOGY | Use a dashed line between known points for periods without data | LINES Action: STYLE | SHOULD |
Semrush (SMR) TECHNOLOGY | Display a tooltip showing 'n/a' when hovering over a dot that has no data, and, if possible, explain why | TOOLTIPS Action: ADD | SHOULD |
SONOS (SNS) TECHNOLOGY | Often better to use a line graph | ALTERNATIVE_CHART Action: CONSIDER | SHOULD |
SONOS (SNS) TECHNOLOGY | Use colored circular markers for each data point | DATA_POINTS Action: USE | SHOULD |
SONOS (SNS) TECHNOLOGY | Add white lines on top of each colored area to show overlaps between areas Rationale: to show where data overlaps | BORDER Action: ADD | SHOULD |
SONOS (SNS) TECHNOLOGY | Set legend text to regular weight and use circular swatches aligned to the top line of the vertical axis | LEGEND Action: SET | SHOULD |
The Urban Institute (UBI) NON-PROFIT | Directly label the series when possible | DIRECT_LABELS Action: USE | SHOULD |
The Urban Institute (UBI) NON-PROFIT | Order the segments of the chart in a logical fashion. | SEGMENTS Action: ORDER | SHOULD |
The Urban Institute (UBI) NON-PROFIT | Use round-number intervals (1, 2, 5, or 10) on the x-axis when plotting years | AXIS Action: LABEL | SHOULD |
The Urban Institute (UBI) NON-PROFIT | When space is limited, consider placing labels off to the right of the chart (matching series colors). | DIRECT_LABELS Action: USE | MAY |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Use the same colour for the line and the fill | COLOR_COUNT Action: LIMIT | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Make the stream graph interactive if possible | INTERACTIVITY Action: USE | MAY |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Use streamgraphs in interactive form rather than as static graphs | INTERACTIVITY Action: USE | SHOULD |
Chart | Consensus Representative | Confidence | Actions |
|---|---|---|---|
Map USE · COLOR | Use land text colour on zoomed-in maps showing only part of a national border instead of white | Confidence 100% · 10 orgs · 5 industries | |
Map USE · MAPS | Use a static map for simple stories | Confidence 80% · 8 orgs · 4 industries | |
Map AVOID · MAPS | Do not highlight any country on locator maps that show the Kashmir region along the India/Pakistan border | Confidence 79% · 7 orgs · 5 industries | |
Map CONSIDER · ALTERNATIVE_CHART | Consider choosing an alternative layout instead of a map because color scale comparisons are harder for humans than size comparisons. | Confidence 33% · 3 orgs · 2 industries | |
Map LIMIT · COLOR_COUNT | Use no more than 5 colors in choropleths | Confidence 33% · 3 orgs · 2 industries |
USE||MAP_PROJECTIONAVOID||OVERPLOTTING| Organization | Summary | Target | Strength |
|---|---|---|---|
Carnegie Mellon University (CMU) EDUCATION | Limit the map to only the regions present in the data | MAPS Action: LIMIT | SHOULD |
Carnegie Mellon University (CMU) EDUCATION | Avoid decorative shading or colors. | DECORATION Action: AVOID | SHOULD |
Delish (Kraft Heinz Food) (KHZ) FOOD | Make map outlines (borders) light | BORDER Action: ENSURE | SHOULD |
Delish (Kraft Heinz Food) (KHZ) FOOD | Avoid outlines that are too dark | BORDER Action: AVOID | MUST |
London City Intelligence (LDN) GOVERNMENT | Label the legend and map when possible Rationale: Differentiating colour can be tricky | LEGEND Action: LABEL | MAY |
London City Intelligence (LDN) GOVERNMENT | Avoid using choropleth maps because larger areas can imply higher values; use a symbol or hex map instead Rationale: larger areas can be perceived as having higher values | CHART_TYPE Action: AVOID | SHOULD |
National Institutes of Health (NIH) GOVERNMENT | Bin continuous measures into meaningful category value ranges for choropleth maps. | BINS Action: GROUP | SHOULD |
National Institutes of Health (NIH) GOVERNMENT | Consider categorizing bubble sizes into 4–5 sizes when bubbles bunch or values span a large range Rationale: due to bunching of bubbles or a large range between the minimum and maximum values represented | BINS Action: CONSIDER | MAY |
Office for National Statistics (ONS) GOVERNMENT | Use standardised rates rather than absolute values for choropleth maps Rationale: to avoid misleading interpretations | UNITS Action: USE | SHOULD |
Storymaps Arc GIS (AGS) TECHNOLOGY | Ensure a clear understanding of the story you are trying to tell with the map | UNSPECIFIED Action: ENSURE | SHOULD |
Storymaps Arc GIS (AGS) TECHNOLOGY | When interaction is needed, provide only the level of detail relevant to the story's purpose | INTERACTIVITY Action: LIMIT | SHOULD |
Storymaps Arc GIS (AGS) TECHNOLOGY | Avoid unnecessary decorative details that distract from the map's main focus | DECORATION Action: AVOID | MUST |
The Dallas Morning News (DMN) JOURNALISM | Use a 1.5pt stroke when the map only shows one level of roads | STROKE_WIDTH Action: SET | SHOULD |
The Dallas Morning News (DMN) JOURNALISM | If small roads clutter the map, consider drawing small roads at 0.5pt and 40% black; keep major roads white. | STROKE_WIDTH Action: CONSIDER | MAY |
The Dallas Morning News (DMN) JOURNALISM | Draw railroad tracks as layered rules with specified stroke widths and styles (e.g., 1.5pt 50K; dashed .35pt gap 6pt; .5pt 50K). | LINES Action: SET | SHOULD |
The Dallas Morning News (DMN) JOURNALISM | Use 50% black lines for state and country boundaries | BORDER Action: USE | SHOULD |
The Dallas Morning News (DMN) JOURNALISM | Include the state capital with a callout showing the city's name on ear maps Rationale: this is all the information that fits on that space | DIRECT_LABELS Action: USE | — |
The Dallas Morning News (DMN) JOURNALISM | Always place Dalworth at the bottom of the locator | LABELS Action: PLACE | SHOULD |
The Dallas Morning News (DMN) JOURNALISM | Always show a major road on locators with a 2.5pt stroke width | STROKE_WIDTH Action: SET | SHOULD |
The Dallas Morning News (DMN) JOURNALISM | Do not use rounded globes or continent shapes | SHAPE Action: AVOID | MUST |
The Economist (ECM) JOURNALISM | Track (label) country names out as appropriate to fill space Rationale: to fill space | LABELS Action: USE | SHOULD |
The Economist (ECM) JOURNALISM | When only one variable is shown, label it directly with a highlight box instead of using a key | DIRECT_LABELS Action: USE | SHOULD |
The Economist (ECM) JOURNALISM | Add a subtle coastline (border) on detailed maps when land areas need extra contrast | BORDER Action: ADD | MAY |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Use curved lines to show movement instead of straight lines | LINES Action: STYLE | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Use headed arrows in flow maps. | SHAPE Action: USE | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Make arrow widths proportional to flow rate | LINES Action: ENSURE | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | apply transparency to the colour of bubbles | TRANSPARENCY Action: SET | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Map bubble size to area, not to radius | DATA_POINTS Action: ENSURE | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Ensure the legend is present. | LEGEND Action: ENSURE | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Apply transparency to the dots (data points) | DATA_POINTS Action: TRANSPARENCY | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Order the pie chart values properly before charting | SEGMENTS Action: ORDER | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Do not show more than 5 categories on a pie chart | CATEGORIES Action: LIMIT | MUST |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Optionally encode an additional variable by mapping it to the pie chart circle size | CHART_SIZE Action: CONSIDER | MAY |
World Wide Fund for Nature (WWF) NON-PROFIT | Simplify maps and the information shown; prefer simpler presentations. | MAPS Action: SIMPLE | SHOULD |
World Wide Fund for Nature (WWF) NON-PROFIT | Use colour to draw attention to maps. Rationale: to draw attention to maps | MAPS Action: HIGHLIGHT | SHOULD |
World Wide Fund for Nature (WWF) NON-PROFIT | Use Georgia Regular or WWF for map typography (secondary copy may use Georgia or Open Sans). | TYPOGRAPHY Action: USE | SHOULD |
Chart | Consensus Representative | Confidence | Actions |
|---|---|---|---|
Small Multiples CONSIDER · ALTERNATIVE_CHART | Consider sparklines as an alternative to line charts when multiple lines need to be plotted | Confidence 100% · 7 orgs · 4 industries | |
Small Multiples USE · SMALL_MULTIPLES | Use sparklines to show how values change over time for multiple data sets | Confidence 90% · 6 orgs · 4 industries | |
Small Multiples CONSIDER · UNSPECIFIED | Consider arranging small-multiple charts in a grid, stacked vertically, or side-by-side horizontally. | Confidence 63% · 4 orgs · 3 industries | |
Small Multiples ENSURE · AXIS | Use the same axis units, axis ranges, and chart dimensions across charts in a small-multiples group to facilitate comparison | Confidence 45% · 3 orgs · 2 industries |
| Organization | Summary | Target | Strength |
|---|---|---|---|
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Use large font sizes for labels in metric charts | TYPOGRAPHY Action: USE | SHOULD |
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Ensure the scale is identical across worksheets | SCALE Action: ENSURE | SHOULD |
Elastic UI (ELC) TECHNOLOGY | Limit sparklines to a single series | LINES Action: LIMIT | SHOULD |
Elastic UI (ELC) TECHNOLOGY | Remove extraneous markings (ticks, labels, tooltips, grid) from sparklines | DECORATION Action: OMIT | SHOULD |
Elastic UI (ELC) TECHNOLOGY | Do not use more than 12 values in sparklines | DATA_POINTS Action: LIMIT | MUST |
Humanitarial Data Exchange (HDX) NON-PROFIT | Arrange small charts in a consistent grid system to make them easy to compare | GRIDS Action: USE | — |
Humanitarial Data Exchange (HDX) NON-PROFIT | Keep axis labeling very simple and show only the max and min values so readers can focus on the data trend Rationale: so that readers can focus on the data trend | LABELS Action: SIMPLE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Sort categories by their total values in either descending or ascending order | SEGMENTS Action: ORDER | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Do not use multiple-line charts with more than 4 categories. Rationale: More than four categories will require too many colours and the chart becomes difficult to read. | CATEGORIES Action: LIMIT | MUST |
Humanitarial Data Exchange (HDX) NON-PROFIT | Add a tooltip so readers can see the breakdowns Rationale: so that reader can see the breakdowns | TOOLTIPS Action: ADD | SHOULD |
Justice Innovation Lab (JIL) NON-PROFIT | Do not repeat axes for each chart in small multiples | AXIS Action: AVOID | MUST |
Justice Innovation Lab (JIL) NON-PROFIT | Order small multiples in a logical sequence (e.g., by quantitative, ordinal, or temporal variable) when possible | ORDERING Action: CONSIDER | SHOULD |
Justice Innovation Lab (JIL) NON-PROFIT | Ensure all charts in a small-multiples group are visible together without scrolling or page breaks | CHART_SIZE Action: ENSURE | SHOULD |
MailChimp (MCP) TECHNOLOGY | Ensure data in metric charts sum to 100% | SUM_TO_100 Action: ENSURE | MUST |
MailChimp (MCP) TECHNOLOGY | Ensure bars have heights (or widths) that are multiples of 8; multiples of 4 are allowed as an exception | BAR_HEIGHT Action: ENSURE | MUST |
MailChimp (MCP) TECHNOLOGY | Limit metric charts to fewer than six categories | CATEGORIES Action: LIMIT | SHOULD |
Office for National Statistics (ONS) GOVERNMENT | Ensure every panel uses the same x and y scales | SCALE Action: ENSURE | SHOULD |
Office for National Statistics (ONS) GOVERNMENT | Limit the number of panels to 12 or fewer | SEGMENTS Action: LIMIT | SHOULD |
Office for National Statistics (ONS) GOVERNMENT | Arrange panels in a logical order to help users interpret the data Rationale: to help the user interpret the data | ORDERING Action: CONSIDER | SHOULD |
Office for National Statistics (ONS) GOVERNMENT | Avoid cluttering small multiples with too many panels | CATEGORIES Action: AVOID | MUST |
Office for National Statistics (ONS) GOVERNMENT | Do not use inconsistent axis scales between panels | AXIS Action: AVOID | MUST |
Office for National Statistics (ONS) GOVERNMENT | Do not omit key reference data that would help users compare panels Rationale: help users make comparisons between panels | UNSPECIFIED Action: AVOID | MUST |
Pinterest (PIN) SOCIAL MEDIA | Make sparklines moderately wider than they are tall to avoid spiky or flat profiles Rationale: to avoid a spiky or flat profile, which can lead to incorrect data interpretation | SPACE_RATIO Action: ENSURE | SHOULD |
RedHat (RHT) TECHNOLOGY | Do not label axis values in sparklines. | LABELS Action: AVOID | MUST |
SONOS (SNS) TECHNOLOGY | Place values aligned to the end when sections mostly begin after 180 degrees, unless the designer chooses otherwise while remaining consistent. | LABELS Action: PLACE | SHOULD |
SONOS (SNS) TECHNOLOGY | Place the chart title at the top-left of the graph | HEADINGS Action: LEFT_ALIGN | SHOULD |
SONOS (SNS) TECHNOLOGY | Do not present the multiple-donut-chart variant to data-illiterate audiences | CHART_TYPE Action: AVOID | MUST |
SONOS (SNS) TECHNOLOGY | Do not use the multiple donut chart variant when there is no comparison between data sets | CHART_TYPE Action: AVOID | MUST |
Chart | Consensus Representative | Confidence | Actions |
|---|---|---|---|
Table CONSIDER · TABLE_CELL | Consider adding charts in table cells when space is available to show the main-data column | Confidence 100% · 5 orgs · 4 industries | |
Table CONSIDER · UNSPECIFIED | Consider using pagination for long or complex tables | Confidence 86% · 4 orgs · 4 industries | |
Table RIGHT_ALIGN · TABLE_CELL | Right-justify numbers in table cells | Confidence 78% · 4 orgs · 3 industries | |
Table LEFT_ALIGN · TABLE_CELL | Left-align table (table cells) | Confidence 57% · 3 orgs · 2 industries |
USE||TABLECONSIDER||ALTERNATIVE_CHARTUSE||COLORLIMIT||COLOR_COUNTSET||CHART_SIZEUSE||HEADINGS| Organization | Summary | Target | Strength |
|---|---|---|---|
AVIVA (AVV) FINANCE | Use up/down icons to indicate positive or negative values Rationale: to indicate positive or negative values | LABELS Action: USE | SHOULD |
AVIVA (AVV) FINANCE | Allow no more than one icon per table cell | TABLE_CELL Action: LIMIT | MUST |
AVIVA (AVV) FINANCE | Omit a separate indicator because the numeric indicator icon already conveys positive/negative Rationale: Numeric indicator icon usage conveys the positive/negative indication | DECORATION Action: OMIT | MAY |
AVIVA (AVV) FINANCE | Give headings concise, clear, meaningful labels | HEADINGS Action: CONCISE | SHOULD |
AVIVA (AVV) FINANCE | Ensure non-stackable tables scroll horizontally on mobile | SCROLL_BAR Action: ENSURE | SHOULD |
AVIVA (AVV) FINANCE | Use numeric indicators (with up/down arrows) to highlight funds' performance Rationale: to highlight funds' performance | PRECISE_NUMBER Action: USE | SHOULD |
AVIVA (AVV) FINANCE | Do not use show/hide controls in tables. | INTERACTIVITY Action: AVOID | MUST |
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Add interactive elements to the table so it connects to the rest of the dashboard Rationale: to connect it to the rest of the dashboard | INTERACTIVITY Action: ADD | SHOULD |
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Ensure text is legible, ideally around 12 points | TYPOGRAPHY Action: ENSURE | SHOULD |
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Use dotted grey lines to separate items in the table | BORDER Action: USE | SHOULD |
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Place a bubble matrix as a visually striking centerpiece of the dashboard to engage the audience Rationale: to draw your audience into a story | DASHBOARD Action: PLACE | MAY |
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Avoid using scale to communicate quantity Rationale: Scale is an unreliable method of communicating quantity | SCALE Action: AVOID | SHOULD |
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Use a benchmark to provide additional visual cues for scale in a bubble matrix Rationale: to provide additional visual cues for scale | SCALE Action: USE | SHOULD |
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Ensure bubble size is scaled appropriately | SCALE Action: ENSURE | SHOULD |
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Avoid the bubble matrix when precision is needed; use a bar chart instead. | CHART_TYPE Action: AVOID | MUST |
Cato Institute (CTO) NON-PROFIT | Turn on the scroll bar for tables with seven or more rows | SCROLL_BAR Action: START | SHOULD |
Cato Institute (CTO) NON-PROFIT | Left-align text and numbers in table headers in the first (leftmost) column | HEADINGS Action: LEFT_ALIGN | SHOULD |
Cato Institute (CTO) NON-PROFIT | Right-align all text and numbers in every column except the first column. | COLUMNS Action: RIGHT_ALIGN | SHOULD |
DHL CARGO | Highlight important information in rows, columns, or cells by adding backgrounds or borders. | TABLE_CELL Action: HIGHLIGHT | SHOULD |
DHL CARGO | Make the spacing between columns equal | SPACING Action: ENSURE | SHOULD |
DHL CARGO | Make the spacing between rows equal | SPACING Action: ENSURE | SHOULD |
DHL CARGO | Highlight important columns with a Postyellow border | COLUMNS Action: HIGHLIGHT | SHOULD |
DHL CARGO | Highlight important table cells with a background color | TABLE_CELL Action: HIGHLIGHT | SHOULD |
DHL CARGO | Do not format the spacing between columns inconsistently. | SPACING Action: AVOID | MUST |
DHL CARGO | Do not format the spacing between rows inconsistently. | SPACING Action: AVOID | MUST |
Government of Canada (CAN) GOVERNMENT | Consider adding interactivity (filters, sort functions) to tables so users can manipulate and view key data Rationale: so users can manipulate and view key pieces of the data set | INTERACTIVITY Action: CONSIDER | MAY |
Government of Canada (CAN) GOVERNMENT | Include brief but informative titles on tables | HEADINGS Action: ADD | SHOULD |
Government of Canada (CAN) GOVERNMENT | Use striped tables to improve readability Rationale: to improve readability | DECORATION Action: USE | SHOULD |
Government of Canada (CAN) GOVERNMENT | Include sorting icons or a checkbox column in data tables | INTERACTIVITY Action: USE | SHOULD |
Government of Canada (CAN) GOVERNMENT | Highlight active table rows with fill #F2F5F6 when checkboxes are present | ROWS Action: HIGHLIGHT | SHOULD |
Government of Canada (CAN) GOVERNMENT | Add interactive elements (pagination, filters, search bars, icon buttons, sorting icons) to data tables | INTERACTIVITY Action: ADD | SHOULD |
Government of Canada (CAN) GOVERNMENT | Do not include a checkbox column unless there are actions to perform on a specific row of data | COLUMNS Action: AVOID | MUST |
Humanitarial Data Exchange (HDX) NON-PROFIT | Ensure the audience is familiar with this type of data visualization before using it. | CHART_TYPE Action: ENSURE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Sort the x and y axes so the most important value appears at the top-left Rationale: so that the most important number (highest or lowest data, depending on your key messages) is displayed on top left | AXIS Action: ORDER | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Allow data labels to have a white shadow to improve readability on dark or light backgrounds Rationale: to ease reading on dark or light colour background | DECORATION Action: USE | MAY |
Humanitarial Data Exchange (HDX) NON-PROFIT | Consider using humanitarian icons to make text more user-friendly Rationale: to make the text more user-friendly | DECORATION Action: CONSIDER | MAY |
Humanitarial Data Exchange (HDX) NON-PROFIT | Ensure the legend follows the same direction as the data (e.g., highest number on top to match sorting). | LEGEND Action: ENSURE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Use an acronym for long row names and include the full name in the footer | ABBREVIATION Action: USE | MAY |
Humanitarial Data Exchange (HDX) NON-PROFIT | Simplify the table as much as possible so the content is prominent and use proper alignment based on the content Rationale: to make the content prominent | UNSPECIFIED Action: SIMPLE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | When possible, simplify and round numbers and use short-form units 'k', 'M', and 'B' for thousand, million, and billion. | UNITS Action: USE | MAY |
Humanitarial Data Exchange (HDX) NON-PROFIT | Use only one short-form unit per column so numbers are comparable Rationale: to make the numbers easily comparable | UNITS Action: USE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Use the short form that appears as majority. | ABBREVIATION Action: USE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Use the most user-friendly date format: DD Mmm YYYY | DATE_FORMAT Action: USE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Add the date format in the header when using alternative date formats (e.g., YYYY-MM-DD) | DATE_FORMAT Action: ADD | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Sort the data by the column that is the main message | ORDERING Action: CONSIDER | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Add a filter tool to every column so users can interactively explore different answers Rationale: so that users can play and get different answers based on their needs | COLUMNS Action: ADD | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Visualize the main data using a bar chart when space is available | BAR Action: USE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Use light grid lines | GRIDLINES Action: USE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Do not mix units; use a single consistent unit (e.g., round 730M to 0.7B if using B) | UNITS Action: AVOID | MUST |
Humanitarial Data Exchange (HDX) NON-PROFIT | Do not use YYYY-MM-DD or YYYY-DD-MM date formats without a description in the header | DATE_FORMAT Action: AVOID | MUST |
Humanitarial Data Exchange (HDX) NON-PROFIT | Do not use alternating background in tables | DECORATION Action: AVOID | MUST |
Royal Statistical Society (RSS) EDUCATION | Ensure the number of digits is consistent for the same variable within each table row or column | PRECISE_NUMBER Action: CONSISTENT | SHOULD |
Royal Statistical Society (RSS) EDUCATION | allow the number of digits to differ across variables Rationale: if the table contains small and large numbers | PRECISE_NUMBER Action: CONSIDER | MAY |
Royal Statistical Society (RSS) EDUCATION | reduce the font size for less relevant numbers when shown alongside more important data Rationale: to improve clarity | TYPOGRAPHY Action: SET | SHOULD |
Royal Statistical Society (RSS) EDUCATION | Avoid unnecessary numeric precision in tables; use fewer digits to improve reading and comparison Rationale: a lower number of digits might facilitate reading and comparison | PRECISE_NUMBER Action: AVOID | MUST |
Royal Statistical Society (RSS) EDUCATION | Do not use landscape orientation unless unavoidable | LAYOUT Action: AVOID | MUST |
Royal Statistical Society (RSS) EDUCATION | Do not use different fonts or colours for decorative purposes | TYPOGRAPHY Action: AVOID | MUST |
Storymaps Arc GIS (AGS) TECHNOLOGY | Categorize data by underlying structure (e.g., agency, location, rank). | UNSPECIFIED Action: GROUP | SHOULD |
Storymaps Arc GIS (AGS) TECHNOLOGY | Use alphabetical order when there is no natural order. | ORDERING Action: CONSIDER | SHOULD |
Storymaps Arc GIS (AGS) TECHNOLOGY | List table columns in a logical order based on calculation sequence (e.g., inputs before derived columns) | COLUMNS Action: ORDER | SHOULD |
Storymaps Arc GIS (AGS) TECHNOLOGY | Use thin gridlines every three to five entries to help readability. Rationale: to help readability | GRIDLINES Action: USE | SHOULD |
Storymaps Arc GIS (AGS) TECHNOLOGY | Use shading to highlight a column or an entry | COLUMNS Action: USE | SHOULD |
Storymaps Arc GIS (AGS) TECHNOLOGY | Avoid busy gridlines or alternating gray rows that distract from the data. Rationale: distract from the data | GRIDLINES Action: AVOID | SHOULD |
Storymaps Arc GIS (AGS) TECHNOLOGY | Do not use colors purely for decorative purposes | DECORATION Action: AVOID | MUST |
Storymaps Arc GIS (AGS) TECHNOLOGY | Do not add guides (such as gridlines or alternating gray) to two- or three-column tables. | GRIDLINES Action: AVOID | MUST |
The Dallas Morning News (DMN) JOURNALISM | Place units only in the first | UNITS Action: PLACE | SHOULD |
The Economist (ECN) JOURNALISM | Use colour highlighting with inverted text to emphasize key details Rationale: to pull out key details | COLOR Action: HIGHLIGHT | SHOULD |
The Economist (ECN) JOURNALISM | Use alternating row colours to help with reading Rationale: to help with reading | ROWS Action: USE | SHOULD |
The Economist (ECN) JOURNALISM | Use small labelled bar charts to visualize table data when visualization would be helpful | BAR Action: USE | SHOULD |
The Urban Institute (UBI) NON-PROFIT | Make tables full width of 6.25 inches in PDF products | CHART_SIZE Action: SHOULD | SHOULD |
The Urban Institute (UBI) NON-PROFIT | Do not have empty columns or rows in tables | COLUMNS Action: AVOID | SHOULD |
The Urban Institute (UBI) NON-PROFIT | Add a 1pt black border beneath all column headings and the last row in a table. | BORDER Action: ADD | SHOULD |
The Urban Institute (UBI) NON-PROFIT | Do not use borders within tables by default Rationale: to increase readability | BORDER Action: AVOID | SHOULD |
The Urban Institute (UBI) NON-PROFIT | Set vertical column borders to 1 pt and black | BORDER Action: SET | SHOULD |
The Urban Institute (UBI) NON-PROFIT | Set horizontal row borders to 1 pt, round dot style, light gray color (217 217 217). | BORDER Action: SET | SHOULD |
The Urban Institute (UBI) NON-PROFIT | Use headline-style capitalization for table headings | HEADINGS Action: CAPITALIZE | SHOULD |
The Urban Institute (UBI) NON-PROFIT | Keep table text concise and use active voice | TABLE_CELL Action: CONCISE | SHOULD |
The Urban Institute (UBI) NON-PROFIT | Subtitles are optional and may be used to list units or add contextual information in Urban tables and figures. Rationale: to list units or add contextual information | HEADINGS Action: CONSIDER | MAY |
The Urban Institute (UBI) NON-PROFIT | Use sentence capitalization in tables | TABLE_CELL Action: CAPITALIZE | SHOULD |
The Urban Institute (UBI) NON-PROFIT | Use sentence capitalization for column headings; spanner headings use headline capitalization; supra-spanner headings use small caps. | HEADINGS Action: CAPITALIZE | SHOULD |
The Urban Institute (UBI) NON-PROFIT | Keep similar table cells at similar widths, except when cells or column headings are lengthy Rationale: to accommodate lengthy cells or column headings | TABLE_CELL Action: CONSISTENT | SHOULD |
The Urban Institute (UBI) NON-PROFIT | All tables must include a source line | DATA_SOURCE Action: INCLUDE | MUST |
The Urban Institute (UBI) NON-PROFIT | Use an asterisk (*) to indicate statistical significance | SPECIAL_CHARACTER Action: USE | SHOULD |
The Urban Institute (UBI) NON-PROFIT | Define all abbreviations or symbols in notes. | ABBREVIATION Action: LABEL | SHOULD |
The Urban Institute (UBI) NON-PROFIT | Use symbols in this order for table notes: *, †, ‡, §, ||, # when symbols are used | SPECIAL_CHARACTER Action: ORDER | SHOULD |
Chart | Consensus Representative | Confidence | Actions |
|---|---|---|---|
Treemap ENSURE · SUM_TO_100 | Ensure the visualization allows comparing relative sizes of groups and the distribution of values within a group | Confidence 100% · 3 orgs · 3 industries | |
Treemap USE · DIRECT_LABELS | Use the components of the treemap to label data directly. | Confidence 100% · 3 orgs · 3 industries | |
Treemap USE · TREEMAP | Use treemaps to show hierarchical data as nested rectangles | Confidence 90% · 3 orgs · 2 industries | |
Treemap AVOID · TREEMAP | Do not use treemaps to show relationships between categories; only use treemaps for part-to-whole when parts sum to a meaningful whole | Confidence 80% · 3 orgs · 1 industry |
| Organization | Summary | Target | Strength |
|---|---|---|---|
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Use white outlines to separate sub-groups within color groups Rationale: to separate groups within color groups (sub-groups) | BORDER Action: USE | SHOULD |
National Institutes of Health (NIH) GOVERNMENT | Use horizontal text for category labels to maximize readability Rationale: to maximize readability | HORIZONTAL_LABELS Action: USE | SHOULD |
National Institutes of Health (NIH) GOVERNMENT | Consider using a clustered bar chart or column chart when there are few categories, categories are ordinal, or a direct and precise comparison is needed. | ALTERNATIVE_CHART Action: CONSIDER | MAY |
Salesforce (SLF) TECHNOLOGY | Sort parent rectangles by size, placing larger ones at the left and/or bottom of the treemap. | SEGMENTS Action: ORDER | SHOULD |
SONOS (SNS) TECHNOLOGY | Use a legend when values are very small | LEGEND Action: USE | SHOULD |
SONOS (SNS) TECHNOLOGY | Avoid large gaps between treemap segments | SPACING Action: AVOID | SHOULD |
SONOS (SNS) TECHNOLOGY | Make the point size of labels and values proportional to the size of their segment | LABELS Action: ENSURE | SHOULD |
Storymaps Arc GIS (AGS) TECHNOLOGY | Place the largest treemap block at the top-left and arrange remaining blocks left-to-right so smallest are on the right Rationale: because people tend to read tree maps clockwise | SPACE Action: PLACE | SHOULD |
Storymaps Arc GIS (AGS) TECHNOLOGY | Combine categories so the treemap displays 6–10 categories | CATEGORIES Action: COMBINE | SHOULD |
Chart | Consensus Representative | Confidence | Actions |
|---|---|---|---|
Bubble Chart AVOID · BUBBLE_CHART | Do not use bubble charts with large datasets or when there are too many bubbles. | Confidence 100% · 5 orgs · 3 industries | |
Bubble Chart USE · BUBBLE_CHART | Use a bubble chart to visualize patterns and relationships and encode additional dimensions with bubble size and color. | Confidence 62% · 3 orgs · 2 industries | |
Bubble Chart USE · LEGEND | Use legends to map bubble sizes to the values of the third variable | Confidence 62% · 3 orgs · 2 industries |
USE||DIRECT_LABELS| Organization | Summary | Target | Strength |
|---|---|---|---|
Delish (Kraft Heinz Food) (KHZ) FOOD | Ensure the metric used for bubble size is positive when using bubbles for a third metric Rationale: circles can’t be a negative size | UNSPECIFIED Action: ENSURE | MUST |
Humanitarial Data Exchange (HDX) NON-PROFIT | Regroup data into a series | UNSPECIFIED Action: GROUP | MAY |
Humanitarial Data Exchange (HDX) NON-PROFIT | Add a time dimension when a play button or time slider is added | INTERACTIVITY Action: CONSIDER | MAY |
Humanitarial Data Exchange (HDX) NON-PROFIT | Add a line chart to the bubble chart to compare the x and y variables Rationale: to compare the x and y variables | LINE Action: ADD | MAY |
Humanitarial Data Exchange (HDX) NON-PROFIT | Use a logarithmic scale when outliers obscure lower-valued data points Rationale: Can display a large range of values; however, some readers may not be familiar with logarithmic scales and they can be easy to misinterpret. | LOGARITHMIC_SCALE Action: USE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Label the axis to indicate that a log scale is used to avoid misleading readers Rationale: to ensure you do not mislead readers | AXIS Action: LABEL | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Add a button to let users switch between linear and logarithmic scales Rationale: so that your user can switch from linear to logarithmic scale | INTERACTIVITY Action: ADD | SHOULD |
National Institutes of Health (NIH) GOVERNMENT | Ensure axis intervals are equally spaced | AXIS Action: ENSURE | SHOULD |
National Institutes of Health (NIH) GOVERNMENT | When a bubble chart uses a log or log-log scale, indicate that in the chart title or the axis titles | HEADINGS Action: ADD | SHOULD |
Semrush (SMR) TECHNOLOGY | Limit bubble charts to no more than 3-4 sets to avoid clutter Rationale: they can become cluttered | SEGMENTS Action: LIMIT | SHOULD |
Semrush (SMR) TECHNOLOGY | Show both vertical and horizontal gridlines | GRIDLINES Action: USE | SHOULD |
Semrush (SMR) TECHNOLOGY | Make the X and Y axis labels clear | LABELS Action: CLEAR | SHOULD |
Semrush (SMR) TECHNOLOGY | Clarify what the bubble size means | LABELS Action: CLEAR | SHOULD |
Semrush (SMR) TECHNOLOGY | Add a legend when there are multiple data sets and include clear values for each dataset | LEGEND Action: ADD | SHOULD |
Semrush (SMR) TECHNOLOGY | Increase bubble opacity to 80% on hover | TRANSPARENCY Action: SET | SHOULD |
Semrush (SMR) TECHNOLOGY | Ensure tooltips show X and Y values, values that determine bubble size, and use colors when multiple datasets are present | TOOLTIPS Action: ENSURE | SHOULD |
Semrush (SMR) TECHNOLOGY | When bubbles intersect, show values only for the hovered bubble and do not show intersection values | TOOLTIPS Action: ENSURE | SHOULD |
Semrush (SMR) TECHNOLOGY | Set bubble minimum size to 11px by 11px when outliers are present Rationale: to prevent small values from being lost under the large ones (outliers) | DATA_POINTS Action: SET | SHOULD |
Semrush (SMR) TECHNOLOGY | Display zero values at the origin | AXIS_ZERO Action: USE | SHOULD |
Semrush (SMR) TECHNOLOGY | Omit points that have no data and indicate this in the legend | DATA_POINTS Action: OMIT | SHOULD |
Semrush (SMR) TECHNOLOGY | Automatically scale the chart when a bubble is near the axes | SCALE Action: ENSURE | — |
Semrush (SMR) TECHNOLOGY | Include explanatory details about what influences bubble size with the chart | TOOLTIPS Action: ADD | SHOULD |
Semrush (SMR) TECHNOLOGY | Do not use more than 4 sets because they can become cluttered Rationale: they can become cluttered | SEGMENTS Action: LIMIT | MUST |
Semrush (SMR) TECHNOLOGY | Do not use captions/labels for bubbles, especially on dense charts Rationale: to avoid clutter | LABELS Action: AVOID | MUST |
Semrush (SMR) TECHNOLOGY | Do not color axis labels Rationale: this can make the data harder to read | LABELS Action: AVOID | MUST |
Semrush (SMR) TECHNOLOGY | Do not limit the number of datasets to maintain chart readability. | UNSPECIFIED Action: AVOID | MUST |
SONOS (SNS) TECHNOLOGY | Arrange bubbles into clustered groups | DATA_POINTS Action: GROUP | SHOULD |
SONOS (SNS) TECHNOLOGY | Do not leave gaps between bubbles | SPACING Action: ENSURE | MUST |
The Economist (ECN) JOURNALISM | Can be used with column or thermometer charts | ALTERNATIVE_CHART Action: CONSIDER | MAY |
The Economist (ECN) JOURNALISM | If bubbles are inappropriate due to number range or presence of positive/negative values, use equal-sized number blocks | ALTERNATIVE_CHART Action: CONSIDER | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Limit the number of data points plotted in a bubble chart | DATA_POINTS Action: LIMIT | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Use transparency when drawing bubbles | TRANSPARENCY Action: USE | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Do not size circles by their radius or diameter; size them by the circle's area instead. | UNSPECIFIED Action: AVOID | MUST |
Chart | Consensus Representative | Confidence | Actions |
|---|---|---|---|
Heatmap USE · COLOR | Use continuous color palettes when creating heat maps | Confidence 100% · 6 orgs · 5 industries | |
Heatmap USE · HEATMAP | Use a heatmap to show the relationship between two variables | Confidence 53% · 3 orgs · 3 industries |
| Organization | Summary | Target | Strength |
|---|---|---|---|
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Use white outlines to separate the data. Rationale: to separate the data | BORDER Action: USE | SHOULD |
Justice Innovation Lab (JIL) NON-PROFIT | Include a legend that maps numeric values to the color scale | LEGEND Action: USE | SHOULD |
Justice Innovation Lab (JIL) NON-PROFIT | Set spacing between heat-map segments to at least 1 pt white space to improve readability Rationale: to improve readability | SPACING Action: SET | SHOULD |
Justice Innovation Lab (JIL) NON-PROFIT | Include numeric data labels for each heatmap cell when there is sufficient space | DIRECT_LABELS Action: USE | SHOULD |
Liferay (LFR) TECHNOLOGY | Use a single color value and white for the time-spots in the heatmap | COLOR_COUNT Action: LIMIT | MUST |
Liferay (LFR) TECHNOLOGY | Use at most seven different circle (bubble) items in the chart Rationale: to improve the activities readability | CATEGORIES Action: LIMIT | MAY |
Salesforce (SLF) TECHNOLOGY | Do not vary colors without reason | COLOR_COUNT Action: LIMIT | MUST |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Include values (direct labels) in heatmap cells for static versions when fine differences between variables matter | DIRECT_LABELS Action: USE | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Include a legend to support the understanding of the chart Rationale: to support the understanding of the chart | LEGEND Action: USE | SHOULD |
Chart | Consensus Representative | Confidence | Actions |
|---|---|---|---|
Stacked Area Chart USE · STACKED_AREA_CHART | Use a stacked area chart to represent multiple time series and maintain legibility | Confidence 100% · 4 orgs · 3 industries | |
Stacked Area Chart AVOID · STACKED_AREA_CHART | Do not use a stacked area chart to show fine differences between values | Confidence 83% · 3 orgs · 3 industries |
| Organization | Summary | Target | Strength |
|---|---|---|---|
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Ensure values are distinguishable using clear color coding | COLOR Action: ENSURE | SHOULD |
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Limit colors to two to three, with one dominant | COLOR_COUNT Action: LIMIT | SHOULD |
BBC Audiences Tableau Style Guide (BBA) JOURNALISM | Place the main category at the bottom of the stacked area chart | AREA_STACK_ORDER Action: ENSURE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Minimize data overlap when using multiple area charts | OVERPLOTTING Action: AVOID | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Prefer a simple line chart instead of a stacked area chart because it is easier to read and avoids colour overlaps Rationale: A simple line chart might be easier to read and less distracting, without colour overlaps | ALTERNATIVE_CHART Action: CONSIDER | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Do not display more than 3 categories | CATEGORIES Action: LIMIT | MUST |
Humanitarial Data Exchange (HDX) NON-PROFIT | Do not compress overlapping data or more than three categories into a single area chart; use small multiple area charts instead | OVERPLOTTING Action: AVOID | MUST |
Humanitarial Data Exchange (HDX) NON-PROFIT | Use small multiples or a multiple line chart instead of a stacked area chart | ALTERNATIVE_CHART Action: CONSIDER | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Show the total by creating a separate bar chart with a different y-axis scale Rationale: to show the total | BAR Action: USE | SHOULD |
Humanitarial Data Exchange (HDX) NON-PROFIT | Do not add interactivity because it requires too many clicks Rationale: requires too many clicks | INTERACTIVITY Action: AVOID | MUST |
SONOS (SNS) TECHNOLOGY | Size the chart to the full width of the page | CHART_SIZE Action: SET | MAY |
SONOS (SNS) TECHNOLOGY | Set the vertical axis to dashed style with regular weight | AXIS Action: SET | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Order the values to tell the best story Rationale: to tell the best story | AREA_STACK_ORDER Action: ORDER | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Do not apply opacity to colours of the filled areas | TRANSPARENCY Action: AVOID | MUST |
Chart | Consensus Representative | Confidence | Actions |
|---|---|---|---|
Box Plot USE · BOX_PLOT | Use boxplots to summarize distributions (median, interquartile range, outliers) though they give little detail about specific data values. | Confidence 100% · 3 orgs · 2 industries |
| Organization | Summary | Target | Strength |
|---|---|---|---|
Delish (Kraft Heinz Food) (KHZ) FOOD | Use transparency to help show overlapping dots Rationale: to help show overlapping dots | TRANSPARENCY Action: USE | SHOULD |
Delish (Kraft Heinz Food) (KHZ) FOOD | Do not use a single box-and-whisker plot when you have only a single data set; consider a histogram or other chart type instead | CHART_TYPE Action: AVOID | MUST |
National Institutes of Health (NIH) GOVERNMENT | Order x-axis categories intentionally; use natural order for ordinal axes; for nominal categories, consider ordering by mean or median to show ranking Rationale: to show this ranking | ORDERING Action: CONSIDER | SHOULD |
Royal Statistical Society (RSS) EDUCATION | Use a horizontal orientation for box plots to enable more accurate visual comparison Rationale: since it is easier for the human eye to follow an imaginary vertical line than an imaginary horizontal line | AXIS Action: USE | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Order groups when they lack an inherent order (for example, sort groups by median). | SEGMENTS Action: ORDER | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Avoid using boxplots when showing the distribution for a single group; use a histogram instead. | CHART_TYPE Action: AVOID | MUST |
Chart | Consensus Representative | Confidence | Actions |
|---|---|---|---|
Dot Plot USE · DOT_PLOT | Use the Q for dot plots and arrow charts for online | Confidence 100% · 3 orgs · 3 industries |
| Organization | Summary | Target | Strength |
|---|---|---|---|
Delish (Kraft Heinz Food) (KHZ) FOOD | Use transparency to help show overlapping dots Rationale: to help show overlapping dots | TRANSPARENCY Action: USE | SHOULD |
NZZ Visuals (NZZ) JOURNALISM | Right-align y-axis category labels. | LABELS Action: RIGHT_ALIGN | SHOULD |
NZZ Visuals (NZZ) JOURNALISM | Add guidance by integrating chart symbols into the legend text when the legend is complicated | LEGEND Action: ADD | SHOULD |
Salesforce (SLF) TECHNOLOGY | Do not use dot plots for very large or extremely dense data sets Rationale: too many (or too-large) dots can make a dot plot hard to read | CHART_TYPE Action: AVOID | MUST |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Use a dot plot as an alternative to grouped bar charts or slope charts | ALTERNATIVE_CHART Action: CONSIDER | MAY |
Chart | Consensus Representative | Confidence | Actions |
|---|---|---|---|
Histogram USE · AXIS_ZERO | Start histograms from a zero baseline | Confidence 100% · 3 orgs · 3 industries |
AVOID||HISTOGRAM| Organization | Summary | Target | Strength |
|---|---|---|---|
Justice Innovation Lab (JIL) NON-PROFIT | Use a histogram to show the distribution of values across equally-sized bins, with the y-axis showing count or relative frequency. | CHART_TYPE Action: USE | SHOULD |
Justice Innovation Lab (JIL) NON-PROFIT | Do not have gaps between histogram bars | BAR_GAP Action: AVOID | MUST |
Justice Innovation Lab (JIL) NON-PROFIT | Carefully select the bin width or bandwidth for histograms because it influences distribution shape and visibility of trends Rationale: as this influences distribution shape and affects visibility of trends | BINS Action: SELECT | SHOULD |
National Institutes of Health (NIH) GOVERNMENT | Avoid using 3D effects in histograms to reduce ambiguity about bar tops Rationale: Reduce ambiguity about where the “top” of the bar is | DECORATION Action: AVOID | SHOULD |
National Institutes of Health (NIH) GOVERNMENT | Do not omit histogram bins with no data because this can be deceiving Rationale: as this can be deceiving | BINS Action: ENSURE | MUST |
National Institutes of Health (NIH) GOVERNMENT | Place direct labels outside the top of the bars. | DIRECT_LABELS Action: USE | SHOULD |
Semrush (SMR) TECHNOLOGY | Ensure the chart title explains the axes | HEADINGS Action: ENSURE | SHOULD |
Semrush (SMR) TECHNOLOGY | Use a single color (or similar shades) to keep the histogram simple Rationale: for simplicity | COLOR_COUNT Action: LIMIT | SHOULD |
Semrush (SMR) TECHNOLOGY | Consider using a horizontal histogram when range names are long or there are many ranges | ALTERNATIVE_CHART Action: CONSIDER | MAY |
Semrush (SMR) TECHNOLOGY | Set the upper part of histogram bars to have a 2px border radius for vertical histograms | BORDER Action: SET | SHOULD |
Semrush (SMR) TECHNOLOGY | Use different colors carefully to highlight specific ranges because they can make the chart easier to read Rationale: make the chart easier to read | COLOR Action: USE | SHOULD |
Semrush (SMR) TECHNOLOGY | Organize histogram values in a logical order (e.g., largest to smallest or chronologically for months). | ORDERING Action: CONSIDER | SHOULD |
Semrush (SMR) TECHNOLOGY | Ensure bars are at least 2px high for visibility next to very large values Rationale: to ensure visibility next to very large values | BAR_HEIGHT Action: ENSURE | SHOULD |
Semrush (SMR) TECHNOLOGY | Consider using a logarithmic scale to balance the representation of data ranges Rationale: help balance the representation of data ranges | LOGARITHMIC_SCALE Action: CONSIDER | MAY |
Semrush (SMR) TECHNOLOGY | Omit the legend for histograms | LEGEND Action: AVOID | MUST |
Semrush (SMR) TECHNOLOGY | Display a single bar when the data is a single range | BAR Action: USE | SHOULD |
Semrush (SMR) TECHNOLOGY | Ensure tooltips show zero when the data are all zero | TOOLTIPS Action: ENSURE | SHOULD |
Semrush (SMR) TECHNOLOGY | Do not reorder histogram bars by size | ORDERING Action: AVOID | MUST |
Semrush (SMR) TECHNOLOGY | Avoid incorrect scaling to prevent misleading impressions of value proportions. Rationale: Incorrect scaling can create illusions of proportion, making one value seem half as large as another when it's not. | SCALE Action: AVOID | MUST |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Use an appropriate number of bins | BINS Action: USE | SHOULD |
United Nations High Commissioner for Refugees (UNR) GOVERNMENT | Do not use unequal bin sizes in histograms | BINS Action: AVOID | MUST |
Chart | Consensus Representative | Confidence | Actions |
|---|---|---|---|
Metric Chart USE · METRIC_CHART | Use a Metric chart to convey a single numerical value. | Confidence 100% · 3 orgs · 1 industry |
CONSIDER||ALTERNATIVE_CHART| Organization | Summary | Target | Strength |
|---|---|---|---|
AVIVA (AVV) FINANCE | Keep labels short and to a minimum (consider mobile) | LABELS Action: CONCISE | SHOULD |
AVIVA (AVV) FINANCE | Limit labels to at most 50 characters | LABELS Action: LIMIT | MUST |
AVIVA (AVV) FINANCE | Allow up to 4 labels | LABELS Action: LIMIT | MAY |
AVIVA (AVV) FINANCE | Keep label styling consistent, appearing on the same line using either Regular or Semi-bold | LABELS Action: CONSISTENT | SHOULD |
AVIVA (AVV) FINANCE | Do not place metric charts on dark accent colours | COLOR_COUNT Action: LIMIT | MUST |
AVIVA (AVV) FINANCE | Ensure headings are marked up in an appropriate hierarchy | HEADINGS Action: ENSURE | MUST |
Elastic UI (ELC) TECHNOLOGY | Ensure titles, subtitles, and chart text are clearly described and self-explanatory; be specific but not verbose | HEADINGS Action: ENSURE | SHOULD |
Elastic UI (ELC) TECHNOLOGY | Use subtitles or Unit Text to clarify choices and prior calculations Rationale: to clarify this and to inform the user of the choices and calculations that have been made prior | HEADINGS Action: CONSIDER | MAY |
Elastic UI (ELC) TECHNOLOGY | Limit the number of digits shown; use abbreviated numbers like $3M instead of $3,000,000 | PRECISE_NUMBER Action: LIMIT | SHOULD |
Elastic UI (ELC) TECHNOLOGY | Use color for aesthetic or functional reasons Rationale: aesthetic or functional | COLOR Action: USE | MAY |
Elastic UI (ELC) TECHNOLOGY | Associate a color scale (palette) based on the value range to provide a qualitative indicator of values Rationale: to give a qualitative indicator of your value in that range | COLOR Action: CONSIDER | MAY |
Elastic UI (ELC) TECHNOLOGY | Use a progress bar to show a metric as progress or a quantity within a range | BAR Action: USE | MAY |
Elastic UI (ELC) TECHNOLOGY | Use the length of a bar to represent progress Rationale: one natural representation of progress | BAR Action: USE | SHOULD |
Elastic UI (ELC) TECHNOLOGY | Ensure the progress bar starts at zero to make its length easier to read Rationale: To simplify the readability of the length | AXIS_ZERO Action: USE | MUST |
Elastic UI (ELC) TECHNOLOGY | Axis should start at zero | AXIS_ZERO Action: USE | SHOULD |
Elastic UI (ELC) TECHNOLOGY | Represent the variable's trend by plotting an overlay (trend) on the metric background | TREND_LINE Action: ADD | MAY |
Elastic UI (ELC) TECHNOLOGY | Metrics may be shown individually or arranged in a grid | UNSPECIFIED Action: CONSIDER | MAY |
Elastic UI (ELC) TECHNOLOGY | Align progress bars vertically to compare values Rationale: to compare values | BAR Action: CONSIDER | MAY |
Elastic UI (ELC) TECHNOLOGY | Align progress bars horizontally when there are multiple vertical metrics so values can be compared Rationale: to compare values | BAR Action: PLACE | MAY |
Elastic UI (ELC) TECHNOLOGY | Allow mixing columns and rows in the data array and mixing different types of metrics to create a grid. | GRIDS Action: CONSIDER | MAY |
Elastic UI (ELC) TECHNOLOGY | Do not display multiple secondary visual representations (e.g., progress bar and trend) at the same time; treat them as decorations. Rationale: to limit the visual complexity and improve the understandability of the data | DECORATION Action: AVOID | MUST |
Elastic UI (ELC) TECHNOLOGY | Do not use longer text or very precise multi-digit numbers in metric charts Rationale: they can nullify the scope of the chart | PRECISE_NUMBER Action: AVOID | MUST |
Elastic UI (ELC) TECHNOLOGY | Avoid using a zero baseline in metric charts | AXIS Action: TRUNCATE | SHOULD |
Elastic UI (ELC) TECHNOLOGY | Avoid using negative values in metric charts; if negatives may appear, provide visual guidance to help users Rationale: to facilitate the user in understanding what is happening | UNSPECIFIED Action: AVOID | MUST |
Elastic UI (ELC) TECHNOLOGY | Consider using a bar chart to put metrics that share the same scale on the same chart to simplify comparison. Rationale: IN ORDER TO SIMPLIFY THE COMPARISON AMONG THEM | BAR Action: CONSIDER | MAY |
Elastic UI (ELC) TECHNOLOGY | Do not use the metric chart; use tables with conditional formatting instead | CHART_TYPE Action: AVOID | MUST |
National Institutes of Health (NIH) GOVERNMENT | Include the percent complete label at the inside end of the blue portion of the bar | BAR Action: LABEL | SHOULD |
National Institutes of Health (NIH) GOVERNMENT | Ensure progress bars use consistent sizing when more than one is shown | BAR Action: ENSURE | SHOULD |
National Institutes of Health (NIH) GOVERNMENT | Consider omitting the x-axis (or only show 0% and 100% labels). Rationale: to avoid cluttered charts | AXIS Action: AVOID | MAY |
Salesforce (SLF) TECHNOLOGY | Do not present data without a reference point. | UNSPECIFIED Action: AVOID | MUST |
Salesforce (SLF) TECHNOLOGY | Do not use a too-small polar gauge when space is limited | CHART_TYPE Action: AVOID | MUST |
Salesforce (SLF) TECHNOLOGY | Add a reference point (target or average value) to give context | TREND_LINE Action: ADD | SHOULD |
The Dallas Morning News (DMN) JOURNALISM | Keep intro copy and footnotes under 20 words (130 characters) | UNSPECIFIED Action: LIMIT | SHOULD |
The Dallas Morning News (DMN) JOURNALISM | Add a beige box for fever charts that have only one line | DECORATION Action: ADD | SHOULD |
© 2025 All Rights Reserved.
.