Beyond Dark Mode: 11 Practical Tips for Designing Themes That Stay Legible (and On-Brand) in Any UI

designer working on UI theme color system tokens dark mode on laptop

Themeable interfaces are everywhere: design systems ship with multiple color modes, SaaS dashboards offer “compact density,” and products increasingly support user-selected contrast settings. For graphic designers, this shifts the job from crafting a single “perfect” layout to building a visual identity that survives many combinations: light/dark, high contrast, tinted backgrounds, user-generated content, and OS-level accessibility overrides.

This roundup collects practical, field-tested tips for designing brand-forward UI themes that remain readable, consistent, and production-friendly. Each item includes actionable guidance you can apply in Figma and in collaboration with developers.

1) Start with “contrast tokens,” not colors

Instead of defining your system as “Primary Blue = #1D4ED8,” define roles and contrast intent: Action/Primary on Surface, Text/Primary on Surface, Border/Subtle on Surface. Then map those to actual hex values per theme.

  • Why it works: you can swap surfaces (white, near-black, tinted, or photo-backed) without breaking legibility.
  • Actionable setup: create tokens for: surface, surface-elevated, text-primary, text-secondary, text-inverse, border-subtle, focus, action-primary, action-primary-hover.
  • Real-world example: many mature systems (e.g., Material, Polaris, Fluent) use role-based tokens so the same component can render across modes with fewer exceptions.

2) Audit your palette with “contrast budgets”

Most teams treat contrast as a pass/fail checkbox. A better approach is to set a contrast budget per text size and usage. For example:

  • Body text (14–16px): aim for 7:1 when possible, minimum 4.5:1.
  • Small UI labels (12–13px): treat 4.5:1 as a baseline; avoid “light gray on gray” patterns.
  • Large headlines (24px+): you can accept lower contrast, but only if the background is stable and not patterned.

Tip: check contrast on all states—default, hover, pressed, disabled, selected. Disabled states are common failures: designers reduce opacity and accidentally drop below readable contrast.

3) Design for “tinted dark mode,” not pure black

Pure black (#000) often increases eye strain and can make brand colors look harsh or neon. Many successful UIs use a very dark gray or a hue-tinted dark surface (e.g., #0B1220 with a subtle blue cast) to keep identity consistent.

  • Practical recipe: choose a base dark surface around L* 5–10 (perceptual lightness), then adjust text and borders with small steps (e.g., 8–12 points difference in L* between levels).
  • Common pitfall: reusing the same border color in light and dark modes; in dark mode, borders often need slightly higher contrast than you expect because dark surfaces visually “swallow” thin lines.

4) Use “semantic ramps” for status colors (not one-off greens/reds)

Status colors (success, warning, error, info) are where theme systems often collapse—especially for charts, badges, and callouts. Build a ramp for each semantic color: 8–12 steps from very light tint to deep shade.

  • How to implement: define at least these tokens: success-surface, success-border, success-text, success-icon, and mirror them for warning/error/info.
  • Accessibility note: never rely on color alone—pair with icons, labels, and patterns where appropriate (e.g., error icon + “Error” label).
  • Example: an error banner in light mode might use a pale red surface with dark red text; in dark mode, the error surface might be a very deep maroon, with lighter red text.

5) Treat focus states as brand moments (and test them)

Focus rings and keyboard navigation are often an afterthought, yet they’re a consistent cross-app signature. Make focus visible and intentional.

  • Rule of thumb: aim for a focus ring that’s at least 2px and clearly distinct from hover/selected borders.
  • Theme tip: use a dedicated focus token rather than reusing the primary brand color; some brand colors fail on dark surfaces or conflict with status colors.
  • Quick test: tab through a prototype on a dimmed screen. If focus is hard to track, users will struggle—especially in data-heavy tools.

6) Make typography mode-aware: weight, spacing, and smoothing

Dark mode can make type appear bolder due to halation (light text on dark background). You can compensate without changing your brand font.

  • Adjustments that help: slightly reduce font weight (e.g., 400 → 350 if variable fonts allow), increase letter spacing by 1–2%, or raise line height slightly for long-form text.
  • Example: a 14px UI label that looks crisp in light mode may feel “clogged” in dark mode; a tiny tracking increase can restore clarity.

7) Build a “density ladder” for component spacing

Theme isn’t only color. Many products now offer density settings (comfortable/compact). Designers can prevent chaos by defining a spacing scale that snaps components to predictable increments.

  • Actionable ladder: set 3 densities with consistent deltas, e.g., padding steps of 16/12/8 and row heights of 48/40/32.
  • Real-world payoff: tables, sidebars, and forms become instantly themeable without bespoke layouts.

8) Plan for “image and media unpredictability”

User-generated images, thumbnails, and embedded content can destroy a theme’s harmony—especially dark mode—by introducing bright rectangles and clashing colors.

  • Mitigation strategies: apply neutral backplates, use subtle scrims behind text overlays, and define media container borders that adapt by theme.
  • Example: a photo grid in dark mode often needs a slightly lighter container surface so images don’t float in pure black void.

9) Use “paired neutrals” to preserve depth and hierarchy

A common dark mode failure is flattening: everything becomes the same dark gray. Depth cues—cards, modals, tooltips—need a deliberate neutral system.

  • Practical neutral set: define at least 5 surfaces: base, raised, overlay, sunken, and inverse (for chips on colored surfaces).
  • Test method: screenshot key flows (settings, dashboards, forms) and blur them. If hierarchy disappears when blurred, your surfaces are too similar.

10) Validate with real data and real reading, not just mock screens

Theme legibility issues often appear in “dense reality”: long names, multi-line addresses, noisy charts, and error-heavy forms.

  • Checklist: test a table with 50+ rows; test a form with validation errors; test a dashboard with 6+ charts; test empty states and edge states.
  • Data point to keep in mind: reading comfort and accessibility aren’t just compliance—they’re usability. Publications frequently discuss how design choices affect attention and readability in digital environments; for broader context on interface and reading habits, see reporting and analysis from The Guardian.

11) Ship a “theme QA kit” so your system stays intact

The best theme design can still degrade during implementation. A lightweight QA kit keeps everyone aligned.

  • Include: contrast targets, token naming rules, state definitions (hover/pressed/focus/disabled), and examples of “do/don’t.”
  • Automate what you can: add linters for token usage, enforce semantic tokens instead of raw hex values, and build a Storybook (or equivalent) page to review components across themes.
  • Workflow tip: set a release gate: no component merges unless it’s reviewed in light, dark, and high-contrast settings.

Roundup: a quick “theme-ready” checklist you can use today

  • Define role-based tokens (text, surface, border, action, focus) before choosing final colors.
  • Set contrast budgets per text size and state; avoid opacity-only disabled states.
  • Prefer tinted dark surfaces over pure black for comfort and brand consistency.
  • Build semantic ramps for status colors with surface/border/text/icon tokens.
  • Make focus rings visible, consistent, and theme-aware.
  • Adjust typography subtly for dark mode (weight/spacing/line height).
  • Create density tiers that scale padding and component heights predictably.
  • Protect layouts from unpredictable media with containers and scrims.
  • Use paired neutrals to preserve depth and hierarchy in every mode.
  • Test with realistic data: tables, forms, charts, and error-heavy flows.
  • Maintain quality with a theme QA kit and automated token enforcement.

Conclusion: design a visual identity that survives settings you don’t control

Modern graphic design in digital products is increasingly about resilience: your brand needs to look like itself under dark mode, high contrast, compact density, and content you can’t predict. The most reliable path is to think in systems—semantic tokens, contrast budgets, ramps, and repeatable QA. Do that, and your “look” won’t just be a coat of paint; it becomes a durable visual identity that holds up everywhere your interface lives.

Leave a Reply

Your email address will not be published. Required fields are marked *