Field + Light
Yellow signals caution, warning, and attention. Yellow alerts indicate potential problems. Yellow status shows degraded but functional state. Yellow highlights draw attention without triggering alarm. The color occupies middle ground between green safety and red danger. Traffic lights use yellow for "prepare to stop"—transition warning before red halt. System monitoring uses yellow for "needs attention but not critical"—degraded performance, approaching limits, minor issues. Yellow warnings say "fix soon before it becomes red." The effectiveness depends on not crying wolf. Too many yellow alerts create alert fatigue. Users learn to ignore yellow if it rarely precedes actual problems. But too-conservative yellow thresholds mean jumping from green directly to red without transition warning. Calibrate yellow to provide useful advance notice without generating noise.
Yellow warns without alarming. It signals "pay attention" without requiring immediate action. The middle-severity indication sits between green (ignore) and red (act now).
Monitoring systems use yellow for degraded states. Service responding but slow: yellow. Error rate elevated but below critical: yellow. Capacity usage high but not exhausted: yellow. The yellow indicates trending toward problems.
Effective yellow warnings provide actionable advance notice. Yellow appears before red becomes inevitable. The warning window allows preventive intervention. Without yellow, systems jump from fine to failed without warning.
Yellow often indicates transitional states. Startup phase shows yellow. Shutdown in progress shows yellow. Migration occurring shows yellow. The color indicates neither fully operational (green) nor failed (red).
Transitional yellows should be temporary. Persistent yellow suggests stuck transition. The color should resolve to green (success) or red (failure) within expected timeframe.
Status displays should distinguish temporary yellow from sustained yellow. Brief yellow during deployment is expected. Prolonged yellow during normal operation indicates problem.
Yellow signifies construction and maintenance. Construction warnings are yellow. Maintenance mode indicators use yellow. The color sets expectation of temporary reduced service.
Scheduled maintenance uses yellow to indicate planned degradation. Users expect reduced capability. The yellow preparation reduces surprise and frustration.
But maintenance yellow should have definite end. Open-ended maintenance creates uncertainty. The yellow period should be bounded with clear expected green restoration.
Yellow communicates caution without panic. Unlike red's urgency, yellow says "be careful" not "stop everything." The moderate tone allows continued operation with increased awareness.
Form validation uses yellow for warnings. Email format unusual but valid: yellow note. Password strength weak but acceptable: yellow indicator. The caution allows proceeding while highlighting concern.
Yellow should never block progress. Blocking actions despite yellow indication confuses users. Red blocks; yellow warns. The behavior should match color meaning.
Yellow highlights direct attention. Important but non-urgent items show yellow. The highlighting makes elements stand out without implying danger.
Search results use yellow highlighting for matched terms. The yellow draws eyes to relevant portions. Notes and annotations use yellow to indicate human-added emphasis.
Excessive yellow highlighting dilutes effect. Everything highlighted means nothing stands out. Selective yellow maintains attention-directing value.
Operating "in the yellow" means acceptable but concerning. Yellow financial performance shows profit but below expectations. Yellow resource usage indicates high but not critical utilization.
Performance dashboards show yellow approaching thresholds. CPU usage at 75%: yellow. Disk space at 80%: yellow. The yellow indicates approaching red zones requiring attention.
Yellow zones should trigger investigation, not immediate action. The investigation reveals whether trending toward red or stable in yellow. The analysis determines appropriate response.
Yellow tape marks restricted areas. Caution tape prevents casual access while allowing authorized entry. The yellow marking creates soft boundary.
Software licensing uses yellow for compliance warnings. License approaching expiration: yellow. Usage approaching limits: yellow. The warning provides time to renew before red violation.
Yellow compliance warnings should provide adequate notice. Last-minute yellow creates emergency situation. Sufficient lead time allows orderly resolution.
Yellow has positive associations with sunlight and optimism. Cheerful interfaces use yellow accents. Friendly notifications might use yellow. The warm color creates positive emotional response.
But yellow optimism conflicts with yellow caution. Same color means different things in different contexts. Clear design language distinguishes cheerful yellow from cautionary yellow.
Context determines yellow interpretation. Yellow in status monitoring is cautionary. Yellow in social features is friendly. The usage context clarifies meaning.
Yellow can have poor contrast against white backgrounds. Light yellow disappears on white. The visibility problem requires darker yellow or alternative background.
Yellow-on-black has good contrast but harsh appearance. The combination is legible but visually strident. Softer combinations balance visibility and comfort.
Color-blind users might not distinguish yellow from white or other colors. Yellow warnings should combine with icons or text. Multi-channel signaling ensures accessibility.
Yellow represents partial or intermediate states. 50% complete tasks might show yellow. Partially successful operations use yellow. The middle state sits between incomplete (red or gray) and complete (green).
Progress indicators sometimes use yellow for in-progress state. Gray for not started, yellow for running, green for complete. The yellow indicates active execution.
But yellow progress can ambiguously mean "in progress" or "problematic progress." Clear labeling distinguishes smooth execution from troubled execution both showing yellow.
Excessive yellow creates "yellow fatigue"—users ignore yellow warnings after seeing too many. The warning color loses impact when ubiquitous.
Yellow threshold tuning reduces fatigue. Tighten criteria to show yellow only for significant concerns. Too-sensitive yellow generates noise. Too-insensitive yellow provides no advance warning.
Alert hygiene requires addressing yellow before it becomes red. Yellow that persists without resolution trains users to ignore it. The responsive handling maintains yellow credibility.
"Sunshine metrics" provide transparency without judgment. Yellow highlighting on public dashboards shows areas needing attention without implying failure.
Government transparency initiatives use yellow for performance below targets. The visibility encourages improvement without punitive red marking. The gentle signaling supports continuous improvement culture.
Yellow transparency should couple with improvement support. Highlighting problems without providing resources creates frustration. The yellow identification should enable corrective action.