Color: Does Meaning Depend on Color?

Color can organize a page, draw attention, and make information easier to understand. Accessible color does not mean avoiding color. It means making sure color is not carrying the message by itself—and making sure foreground and background colors are readable together.

These are two different checks: meaning and contrast. A page needs both.

The question that matters

If the color disappeared, would the meaning still be clear—and would the content still be readable?

A Practical Workflow

Start with the default.
Canvas, Word, Google Docs, and other tools provide default text and link styles. Keep them unless color serves a real purpose.
Ask whether color carries meaning.
If a learner must identify a status, category, instruction, or data series by color, add a second cue such as visible words, labels, symbols, patterns, or position.
Check contrast.
Test the actual foreground and background color pair. Looking at the colors is not a reliable test.
Check the whole state.
Test links, highlighted text, chart labels, buttons, form errors, and other meaningful graphics—not only body text.
Respect different displays and preferences.
Avoid locking in custom text and background colors when the default theme works. Preview the content in the environments available to you, including dark or high-contrast modes when possible.

Four rainbow palettes: typical color vision and simulations of three color vision deficiencies. — Color-vision simulations are only illustrations; they do not reproduce every person's experience. The practical lesson is that the same palette may not remain distinguishable for every viewer.

Run Both Checks

Check 1: Is meaning available without color?

Color may reinforce information, but it should not be the only way to find it.

Not enough: “Items in red are late.”
Better: Add the visible word Late and an icon or symbol.
Not enough: A chart legend identifies data series only by colored swatches.
Better: Label the series directly or add patterns, shapes, or line styles.

Check 2: Is there enough contrast?

Under WCAG 2.2 Level AA, the usual minimums are:

4.5:1 for normal-sized text.
3:1 for large text—at least 18 point, or 14 point when bold.
3:1 for meaningful graphics and the visual boundaries or states needed to identify and operate controls.

These ratios measure relative lightness, not whether two colors have different names.

See the Difference

In the revised schedule, the day is written in every relevant cell. Shape and color can still make the pattern easier to scan, but neither is required to understand it.

Assignments and due days identified with words and optional colored symbols
Activity	Week 1	Week 2	Week 3	Week 4
Discussion	Monday	Monday	Monday	Monday
Quiz	—	Wednesday	—	Wednesday
Final project	—	—	—	Friday

Why this works: A learner can get the due-day information from the text. The symbols and colors are helpful redundancies, not gatekeepers.

Quick Check

A grade table uses green for “submitted” and red for “missing.” What is the strongest revision?

Choose brighter shades of green and red.: Brighter colors do not make color-only meaning accessible, and brightness does not guarantee sufficient contrast.
Add the visible words “Submitted” and “Missing,” keep color as an optional cue, and check contrast.: Correct: The words communicate the status without color, while the contrast check addresses readability.
Remove every color from the table.: Color can remain as a helpful cue. It simply should not be the only cue.

Apply It Where You Work

Open only the panel you need. The controls vary, but the two checks stay the same.

Canvas

Keep the default text and link colors when they meet your purpose.
If you apply a custom text or background color, run the Accessibility Checker from the Rich Content Editor and correct any contrast warning.
Do not identify instructions, deadlines, categories, or feedback by color alone.
Do not remove the default visual treatment that distinguishes links from ordinary text.
Preview the saved page. Some formatting behaves differently after editing or when a different display mode is active.

See the Canvas guide to the Rich Content Editor Accessibility Checker (opens in a new tab).

Important: The Canvas palette image below is a useful example of how color pairs can be evaluated, but interfaces and themes change. Do not treat any screenshot as a permanent approved-color list; check the actual pair you use.

Older Canvas palette chart marking text and background color pairs that pass contrast requirements.

Word, PowerPoint, and Google Workspace

Use the application's built-in theme and text styles when possible.
Do not use highlighting, font color, or a colored shape as the only way to mark required, missing, selected, or important information.
Run the available accessibility checker. Remember that an automated checker may not understand what a color means.
When sharing a document or slide deck, inspect the exported version too. Colors can change during conversion to PDF or when viewed on another display.

Charts, Graphs, and Diagrams

Label lines, bars, slices, regions, or nodes directly whenever possible.
When a legend is necessary, pair color with a shape, pattern, line style, abbreviation, or number.
Check contrast between adjacent data elements when the difference is needed to understand the graphic.
Provide an accessible text explanation or data table when the visual carries substantial information.

The final step connects to the separate resource on complex image descriptions: color fixes do not replace an equivalent explanation of a complex chart or diagram.

Optional Video: Color Contrast

This 4-minute, 26-second video reviews color contrast in Canvas content, images, and graphics.

Use Subtitles/CC to turn on captions.
Use Settings to adjust playback speed.
If the video does not load, watch Color Contrast on YouTube (opens in a new tab).

Fix a UDOIT Finding

Use the matching ULEARN guide for current UDOIT and Canvas repair steps:

Automated contrast results are useful evidence, but they do not replace checking whether instructions, status, and meaning remain available without color.

Before You Publish

Every instruction, status, category, and data series is understandable without color.
Normal text has at least 4.5:1 contrast; large text has at least 3:1.
Meaningful graphics and the visual parts needed to identify controls have at least 3:1 contrast.
Links and controls remain visually identifiable.
The saved or exported version has been checked—not only the editing view.
The page does not force unnecessary foreground and background colors that interfere with user display preferences.

For the standards behind these checks, see WCAG: Use of Color (opens in a new tab), WCAG: Contrast (Minimum) (opens in a new tab), and WCAG: Non-text Contrast (opens in a new tab).