Request a demo

Accessibility

Accessible charts for municipal websites: a publishing checklist

Help municipal staff publish accessible charts with readable data, clear labels and useful descriptions, then keep every version accurate when figures change.

On this page

Accessible charts for municipal websites give residents access to the chart's information through readable text and data, as well as the graphic. Publish an explanation of what the chart shows, provide the figures in an appropriate accessible format and check that labels remain clear. When figures change, update those versions together.

Chart accessibility covers several parts of WCAG 2.1 AA, including text alternatives, use of color and contrast. Use these publishing checks alongside an accessibility evaluation of the finished page or interactive dashboard.

What should staff request before publishing a chart?

Ask the department supplying the chart for the underlying figures and the message it is meant to communicate. A picture alone does not give the website editor enough information to prepare or verify an equivalent explanation.

Use this handoff checklist:

Ask the department forCheck before publishing
The figures used in the chartCategories, totals and rounding agree with the graphic.
The reporting period and unitsResidents can tell whether figures describe a fiscal year, calendar year, count, percentage or amount.
A short explanation of the main findingThe wording describes what the figures support, without guessing at causes.
The source document or data pageThe link opens the specific supporting material.
Relevant limitationsMissing values, revised figures and changes in measurement are explained.
The person responsible for updatesSomeone can confirm corrections and approve the next version.

Keep this information with the publishing request. Staff should not have to reconstruct it from axis labels or an old attachment when the next update arrives.

What text should accompany accessible municipal charts?

Give readers a short explanation of the chart's subject and its meaningful comparisons or trends. Include the period and units so the explanation makes sense on its own. Keep a source link nearby.

W3C's complex-image guidance (opens in a new tab) describes a short text alternative that identifies the image and a longer description carrying its essential information. The longer description can include values and relationships shown visually. For the short image field, follow the municipal website alt text guide.

Write the longer explanation as normal page content where residents can read it. Ask the department to check whether it communicates the same conclusion as the chart. A sentence that names only the subject leaves the reader to discover the finding elsewhere.

Be precise about comparisons. Keep proposed figures distinct from adopted figures, and actual results distinct from targets. If the chart compares different reporting periods, explain that difference before drawing a conclusion. These are editorial checks, not permission to infer a cause from a rising or falling line.

How should the chart's data table work?

Use a real table with identified headers, not a picture of cells or a set of values aligned with spaces. Keep the table close to the chart, or provide a clearly labeled link to the equivalent data when the amount of information requires another page or file.

W3C's table examples (opens in a new tab) show how header cells identify the meaning of the data. Bold text alone does not create that relationship. Ask the website provider which editor controls create headers and whether the published table preserves them.

For a small chart, a simple table is usually easier to review than a complicated layout with merged headings. Keep units in the column headings or nearby explanation. Explain missing or suppressed values rather than letting a blank cell imply zero.

Compare each displayed category and value against the chart before publishing. Have someone familiar with screen reader testing check whether a resident can identify which header belongs to a value. If the provider must repair the table structure, send the page URL and identify the affected table.

How do you check chart labels and colors?

Residents should be able to identify a line, bar or segment without relying only on its color. WCAG's use-of-color guidance (opens in a new tab) calls for another visual cue, such as text or shape, when color carries meaning. Direct labels can make a chart easier to follow than a separate color key.

Ask the chart creator to check contrast too. WCAG 2.1 Success Criterion 1.4.11 (opens in a new tab) specifies at least 3:1 contrast against adjacent colors for parts of graphics required to understand the content. It includes an exception when a particular presentation is essential to the information. The test depends on which visual parts convey that information.

Text has a separate rule: Success Criterion 1.4.3 (opens in a new tab) generally requires 4.5:1 for ordinary text and 3:1 for large text. A chart's small axis labels do not become large text because the overall image is large.

Check the chart at its actual size on the public page, including on a phone. If labels become cramped or unreadable, ask for a simpler layout or a larger presentation. A data table does not make an unreadable chart a good experience for residents using the visual version.

What changes when a chart is interactive?

Test the tasks the chart lets residents perform, including changing a date range, choosing a category and finding a value. An embedded dashboard needs review within the page where residents will use it.

WCAG's keyboard guidance (opens in a new tab) requires functionality to be operable through a keyboard interface, apart from its stated path-dependent exception. Use the municipal keyboard accessibility checklist to begin checking the controls, then ask the provider to evaluate screen reader operation and any information revealed only on hover.

Change one filter and compare the chart with its table, explanation and download. Do they describe the same selection? If a download contains the full data set instead, label that difference. Ask the provider to make the active selection understandable and ensure residents can reach equivalent information without relying on the pointer.

Do not assume a chart is accessible because its software offers an accessibility setting. Verify the version residents receive, with its actual labels, filters and data.

What should happen when the figures change?

Treat the chart and its alternatives as one update. The person checking the new figures should also review the explanation, table, source link and reporting period. An old description can contradict an otherwise correct replacement graphic.

Before closing the publishing request:

  1. Match the chart and table to the approved source figures.
  2. Read the explanation again. Confirm that its comparisons still hold.
  3. Check the short image alternative and any linked data files.
  4. Open the public page on a phone and a larger screen. Confirm the intended version appears.
  5. For interactive content, repeat the filter and keyboard checks after the update.

Build these checks into routine municipal website accessibility updates. Start with one chart staff already need to publish: obtain its data, write its explanation and check the finished page together. That creates a repeatable process for the next report.

Frequently asked questions

Does every chart need both a table and a written description?

Choose alternatives that preserve the information the chart communicates. The Scottish Government's chart guidance (opens in a new tab) describes a table, a detailed explanation or both, depending on the content. A short table can supply exact figures, while a written explanation can communicate a pattern that would be difficult to find by reading every cell. Review the reader's task before deciding that either one is enough.

Can staff publish a spreadsheet instead of a table on the page?

A spreadsheet may be appropriate for a large data set, but the file needs its own accessibility review. The Government Analysis Function's publishing guidance (opens in a new tab) recommends HTML tables for data presented on a page and allows a linked HTML table or accessible spreadsheet when a table is too large. Label the download clearly and keep a useful explanation beside the chart.

Is a screenshot of a spreadsheet an accessible data table?

No. A screenshot remains an image; it does not supply navigable table cells and headers. Massachusetts's data visualization guidance (opens in a new tab) calls for an actual table in the document or web page. Ask the provider how staff can create a structured table in the editor, then check the published result with assistive technology.

Should staff put every chart value in the alt text field?

Usually a longer explanation or table is a better home for detailed data. W3C's complex-image guidance (opens in a new tab) separates a short identification from a longer equivalent of the image's essential information. Keep the short alternative useful, connect it to the detail and avoid forcing residents to listen to a long sequence of values without table navigation.

Make public information easier to use.

See Muniway's accessibility approach for local government websites and content.

Explore website accessibility