A safety label only works if the color means what the viewer thinks it means — and if the text on it can actually be read. Those are two different problems. The first is specification: pinning a “safety red” to an exact, reproducible color across paint, print, and screen. The second is contrast: making sure the legend on that red survives poor light and imperfect eyesight. This article covers the ANSI Z535 safety palette, how to translate it between color systems, and how to run a WCAG contrast check so your labels are both compliant and legible.
The ANSI Z535 safety colors
ANSI Z535.1 assigns specific meanings to a fixed set of safety colors. Using the right one is not decoration — it is how a viewer decodes urgency before reading a single word:
| Color | Signal word / meaning |
|---|---|
| Safety Red | DANGER — immediate hazard, death or serious injury |
| Safety Orange | WARNING — hazardous, could cause death or serious injury |
| Safety Yellow | CAUTION — minor or moderate injury; physical hazards |
| Safety Green | SAFETY / first aid, emergency egress, safe condition |
| Safety Blue | NOTICE / mandatory action, information |
The standard defines each color by Munsell notation and, in practice, cross-references to FED-STD-595 chips so a paint shop and a screen printer land on the same red. That reproducibility is the whole point — a “red-ish” placard is not a compliant DANGER placard.
Translating between color systems
Real projects live in several color systems at once: a spec written in RAL (European paint), a brand sheet in Pantone (spot ink), and a web mockup in hex/RGB. Converting between them is genuinely lossy, and it helps to know why:
- RAL and Pantone are physical swatch libraries tied to specific pigments and substrates. There is no exact formula between them — a “match” is the nearest chip, not an equality.
- RGB/hex is device-dependent light, not ink. The same hex looks different on two monitors, and many saturated Pantone/RAL colors sit outside the sRGB gamut, so the on-screen version is only an approximation.
The practical rule: specify the authoritative system for the deliverable (RAL for the powder coat, Pantone for the printed decal) and treat the hex as a preview only. Our color & specification tools handle the RAL–Pantone–hex cross-referencing so you can carry one intended color cleanly across every medium.
The other half: readable contrast
A perfectly specified safety yellow is useless if the black legend on it washes out. WCAG defines legibility as a contrast ratio between text and background, computed from relative luminance:
where L is the relative luminance of each color (a weighted, gamma-corrected sum of its R, G, B channels). The ratio runs from 1:1 (invisible) to 21:1 (black on white). The thresholds that matter:
WCAG 2 targets
4.5:1 minimum for normal body text (AA) · 3:1 for large text (≥18 pt, or 14 pt bold) and for graphical/UI elements · 7:1 for the stricter AAA level.
Worked check: black text (#000000, L = 0) on safety yellow (#FFD100, L ≈ 0.67) gives (0.67 + 0.05) / (0 + 0.05) ≈ 14:1 — excellent, which is exactly why caution signage is black-on-yellow. Flip it to white text on that same yellow and the ratio collapses to about 1.4:1: unreadable, and a common real-world mistake. The color was compliant; the pairing was not.
Run the pairing before you release the artwork. Paste your foreground and background values into our WCAG contrast checker and it returns the exact ratio plus a pass/fail against each WCAG level, so a label is legible for real viewers — including the roughly 1 in 12 men with a color-vision deficiency — not just on a designer’s calibrated screen.
A repeatable label workflow
Put the two halves together and a compliant safety label becomes a short checklist rather than a judgment call:
- Pick the signal color by hazard severity — DANGER red, WARNING orange, CAUTION yellow — per ANSI Z535.4 so the color carries the right meaning before the words are read.
- Specify it in the authoritative system for the medium (RAL for coatings, Pantone for printed decals), and record the hex only as a preview. Note that safety colors have a defined tolerance band; hold the production output inside it rather than eyeballing a match.
- Choose the legend color and test the pair for a WCAG contrast ratio of at least 4.5:1 (or 3:1 for large signal words). Black on yellow and white on red pass comfortably; the reverses do not.
- Sanity-check for color-vision deficiency — never rely on hue alone to distinguish two states; back it with a shape, word, or icon so the meaning survives for a red-green-deficient viewer.
Do this once, capture the values on the drawing, and every future revision inherits a color that is both meaningful and readable — no re-litigating the palette on each job.
Check your colors before they ship
Verify any text/background pair against WCAG AA and AAA with the free FicientDesign Contrast Checker, and pin your safety colors across RAL, Pantone, and hex with the color specification tools — compliant meaning and readable text in one pass.
Stop looking it up twice — run the numbers and keep the record.
This reference is free forever. When you need to actually calculate, document, and defend the result, do it in the app — then export a clean report you can hand to a reviewer.
- ✓46 engineering calculators, unlimited
- ✓Save & reload every calculation
- ✓Organize work into project folders
- ✓Branded, PE-stamped PDF reports
Free plan, no credit card. Upgrade only when it's paying for itself.