INBOX/adhd-friendly-dashboard-variants-v2 (1)/adhd-friendly-colour-variants/sunset-apricot/sunset-apricot-style-guide.md
2026-08-07 15:50:54 +02:00

7 KiB
Raw Blame History

Sunset Apricot UI Style Guide

A fresh apricot-orange system built around your exact colour #FF8C4F. It stays calm by pairing the warm primary with cool slate-blue secondary surfaces.

The exact anchor colour is #FF8C4F. Because it is lively, the rest of the interface stays quieter and cooler so the primary action remains clear without becoming overstimulating.

This system keeps the interface ADHD-friendly by using layered neutral surfaces, one clear primary colour, one quieter secondary colour and restrained supporting accents.


1. Core rules

  • Use neutral backgrounds and surfaces for most of the page.
  • Reserve the primary colour for the next important action.
  • Use the secondary colour for optional or supporting actions.
  • Use spacing and typography before adding colour.
  • Keep one main task visible at a time.
  • Avoid decorative motion and unexpected layout changes.
  • Never communicate status using colour alone.

2. Light mode

Token Value Purpose
--page #FFF9F4 Main page background
--page-accent #F8EBDD Subtle page depth
--surface #FFFFFF Cards and dialogs
--surface-alt #FFF2E7 Inputs and secondary regions
--surface-strong #F6DEC9 Selected and elevated elements
--text #382920 Main text
--muted #79695F Secondary text
--border #E6D2C3 Borders and dividers
--primary #FF8C4F Main action and brand colour
--primary-hover #E86F2F Primary hover and active state
--secondary #DDE7EA Secondary action
--secondary-hover #CDDADF Secondary hover state

3. Dark mode

Token Value Purpose
--page #030201 Main dark background
--page-accent #0C0705 Background depth
--surface #18110D Cards and dialogs
--surface-alt #251A15 Inputs and secondary regions
--surface-strong #3A291F Selected and elevated elements
--text #FBF2EC Main text
--muted #D0BFB5 Secondary text
--border #62493B Borders and dividers
--primary #FF9A63 Main action and brand colour
--primary-hover #FF8C4F Primary hover and active state
--secondary #425C66 Secondary action
--secondary-hover #55717C Secondary hover state

4. Colour roles

Primary

Use the primary colour for warm primary actions, active states and friendly emphasis.

Use it on:

  • the main button
  • active navigation
  • selected controls
  • important links
  • compact brand marks

The primary colour should answer:

What should I do next?

Secondary

Use the secondary colour for cool slate structure, optional actions and visual balance.

Use it on:

  • secondary buttons
  • optional actions
  • toolbars
  • supporting cards
  • inactive navigation

The secondary colour should answer:

What else can I do?

Supporting accents

Role Light Dark
Accent 1 #FFB285 #FFC5A4
Accent 2 #6E8E98 #89A4AE
Accent 3 #C79A67 #D2AE7B
Success #6D8A72 #95B09A
Danger #B86354 #DE9383

Use one supporting accent per component whenever possible.

Recommended page balance:

  • 70% neutral backgrounds and surfaces
  • 20% primary and secondary structure
  • 10% supporting accents and status colours

5. Typography

--font-body:
  "Atkinson Hyperlegible",
  "Segoe UI",
  Arial,
  sans-serif;

--font-ui:
  "Lexend",
  "Segoe UI",
  Arial,
  sans-serif;

Use Atkinson Hyperlegible for paragraphs, instructions, tables and form help.

Use Lexend for headings, buttons, navigation and labels.

Recommended settings:

  • body text: 18px
  • body line-height: 1.6
  • paragraphs: no wider than 70ch
  • labels and buttons: 1618px
  • left-aligned body text
  • concise headings
  • no long all-caps passages

6. Layout and spacing

Use an 8-pixel spacing rhythm.

4px   tiny adjustment
8px   closely related elements
16px  normal component spacing
24px  groups inside a section
32px  separation between sections
48px+ major page regions

Keep one purpose per card. Prefer spacing and surface changes over thick borders or multiple shadows.


7. Components

Primary button

background: var(--primary);
color: var(--on-primary);

Use one obvious primary button per task area.

Secondary button

background: var(--secondary);
color: var(--on-secondary);

Use for optional or reversible actions.

Inputs

background: var(--surface-alt);
border: 1px solid var(--border);
color: var(--text);

On focus:

border-color: var(--primary);
outline: 3px solid var(--focus);

Validation

  • Place the error beside the affected field.
  • Explain how to fix the problem.
  • Preserve the users entered data.
  • Use text or an icon as well as colour.

8. ADHD-friendly interaction rules

  • Present one main task at a time.
  • Reduce optional decisions near the primary action.
  • Keep related controls close together.
  • Use consistent button placement.
  • Avoid unexpected layout movement.
  • Respect prefers-reduced-motion.
  • Keep notifications short and actionable.
  • Use progressive disclosure for advanced options.

9. Accessibility checks

Before release:

  • test keyboard navigation
  • verify visible focus states
  • check text and button contrast
  • test at 200% zoom
  • connect labels to controls
  • test light and dark modes separately
  • use semantic HTML before ARIA

10. Quick tokens

:root {
  --page: #FFF9F4;
  --surface: #FFFFFF;
  --surface-alt: #FFF2E7;
  --text: #382920;
  --muted: #79695F;
  --border: #E6D2C3;
  --primary: #FF8C4F;
  --secondary: #DDE7EA;
}

html[data-theme="dark"] {
  --page: #030201;
  --surface: #18110D;
  --surface-alt: #251A15;
  --text: #FBF2EC;
  --muted: #D0BFB5;
  --border: #62493B;
  --primary: #FF9A63;
  --secondary: #425C66;
}

11. Final rule

When the interface begins to feel busy, remove emphasis before adding another colour. Neutral surfaces should make the primary action easy to find without demanding constant attention.


Typography sample card

Every login demo includes a sample content card so the heading, subheading and paragraph fonts can be compared in a realistic surface.

The demos load the fonts through the Google Fonts CSS API:

@import url(
  "https://fonts.googleapis.com/css2?family=Atkinson+Hyperlegible:wght@400;700&family=Lexend:wght@400;500;600;700&display=swap"
);

Recommended use:

  • Lexend for the card heading, subheading, labels and badges
  • Atkinson Hyperlegible for the paragraph and longer reading text

Example structure:

<article class="sample-card">
  <p class="sample-card__eyebrow">Typography sample</p>
  <h3>A calm and readable card heading</h3>
  <p class="sample-card__subheading">
    A concise subheading demonstrates Lexend at a smaller interface size.
  </p>
  <p class="sample-card__body">
    Lorem ipsum dolor sit amet, consectetur adipiscing elit.
  </p>
</article>