Design system/Foundations

Foundations

Shared visual, content, and accessibility guidance for every Blue Horizon experience.

01 · Foundations

Color palette

A clear, reassuring blue foundation with purposeful accents for actions, status, and emphasis. Select any swatch to copy its hex value.

Core blues
Primary blue#0085CA
Cornflower#44B4EB
Light blue#8DC8E8
Lightest blue#B9D3DC
Dark blue#004F71
Deep navy#003057
Primary blue action#009EDC
Action blue hover / link#0078B6
Charcoal#212121
White#FFFFFF
Dark gray#757575
Semantic accents
Primary submit orange#FF9705
Legacy orange · moderate risk#ED8B00
Success green#84BD00
Error red#E4002B
Teal#009CA6
Purple#830065
Additional legacy accents & states
Yellow#F3E500
Pink#DB0A5B
Light gray#DDDDDD
Success surface · legacy#DAEBB3
Warning surface · legacy#FBF7B3
Error surface · legacy#FACCD5
Use accents by meaningThe legacy palette reserves red for errors, high-risk biometrics, and destructive actions; orange for moderate risk; yellow for low risk; purple for visited links; and teal for limited accents. Keep accents small, and do not place teal next to blue or green.
02 · Foundations

Typography

Arial keeps the system practical across the legacy web experiences. The supplied scale uses a 1.2 modular ratio with 12, 14, or 16 px base options; this specimen shows the 16 px scale.

Display
39.81 / 700
Only 1 per page - main title or concept
Heading 2
27.65 / 700
Used for major sections of a page
Heading 3
19.2 / 700
Used to segment ideas within a section
Body
16 / 400
Good typography makes information easier to scan and understand. Keep line lengths comfortable and use plain, direct language.
Small
13.33 / 400
Updated October 2026 · Supporting information
Use sentence case for headings and content. Reserve uppercase labels for compact actions and interface metadata. The legacy scale uses a 1.2 ratio and supports 12, 14, and 16 px body bases.
03 · Foundations

Layout & shape

An open spacing rhythm and soft corners create structure without making dense healthcare information feel heavy.

Spacing scale

Base unit: 4 px

04—48
4
8
12
16
24
32
48

Corner radius

Use shape to signal hierarchy

10 px base
4 px
9 px
16 px
Inputs and buttons use a 9–10 px radius.
Cards use a 12 px radius.
Platform guidance

Mobile design guidance

Design for the task and available space first. Keep the Blue Horizon identity consistent while using platform conventions when building native Android and Apple apps.

Shared mobile principles

Use for responsive web and native experiences

All platforms
  • LAYOUTAdapt to the content width
    Stack related content into one column when space is limited. Let navigation, cards, and forms reflow instead of shrinking desktop layouts.
  • PRIORITYKeep the main task and next step visible
    Shorten supporting copy, preserve clear headings, and avoid fixed bars that cover content or the keyboard.
  • TARGETSMake touch controls comfortable and separated
    For the web version, use at least 44 × 44 CSS px for primary touch controls as this system’s baseline; increase where practical and prevent neighboring hit areas from overlapping.
  • CONTENTAllow text and controls to grow
    Support larger text, longer localized labels, wrapping, and portrait or landscape layouts without clipping.
  • DATAReformat dense information deliberately
    Prefer a concise result card on phones. If a table must remain tabular, give it a labeled horizontal scroll region and keep important context visible.

Platform references

Respect each platform’s own sizing units and interaction patterns

Native apps
Keep units distinctCSS px, Android dp, and Apple pt are platform-specific units. Treat the values above as separate platform recommendations, not direct conversions. A shared visual system can align intent while native implementations use their platform’s units and controls.

Mobile review checklist

Review the complete flow at narrow and enlarged layouts

CheckTap every control with a finger; test keyboard and screen-reader navigation; enlarge text; rotate the device; check safe areas and on-screen keyboard; confirm focus, errors, and sticky elements never hide the current task.
AvoidRelying on hover, tiny icon-only actions, fixed-width content, unexplained swipe gestures, or a “mobile” layout that only scales down desktop UI.
09 · Start here

How to use this system

Use the shared foundations first, then choose a documented component or pattern. If a case is missing, record the need and propose an extension instead of creating a one-off style.

01 · START

Use the tokens

Choose a semantic token such as action, surface, or feedback before reaching for a raw brand color.

02 · COMPOSE

Follow the pattern

Reuse the established order, responsive behavior, and content model for common member tasks.

03 · EXTEND

Share the exception

Document the user need, accessibility impact, and proposed reusable change with the system owner.

Content and layout conventions

Small choices that keep interfaces clear across products

PreferSentence case, short headings, explicit field labels, familiar healthcare terms, and dates written so the month is unambiguous.
AvoidColor-only instructions, unexplained abbreviations, placeholders used as labels, and forms that jump between columns on narrow screens.
Links are destinations; buttons are actionsVisited links use purple. Make link text describe its destination; avoid vague labels such as “Learn more.” Align form controls and actions to a common left edge, and keep the main action first in keyboard and reading order.

See provider search pattern · Visited link example

10 · Quality bar

Accessibility

Target WCAG 2.2 AA for product experiences. The ratios below are calculated from the listed sRGB colors and apply to normal text; still review the rendered component and every state before release.

Documented text pairings

Normal text target: 4.5:1 · large text target: 3:1

Color contrast
TextBackgroundRatioResult
#003057#FFFFFF13.46:1Pass
#004F71#FFFFFF8.91:1Pass
#0078B6#FFFFFF4.81:1Pass
#0085CA#FFFFFF4.03:1Fail
#212121#FF97057.42:1Pass
#212121#009EDC5.31:1Pass
#FFFFFF#E4002B4.85:1Pass
#212121#84BD007.10:1Pass
Do not use primary blue or cornflower as small text on white. Prefer action blue (#0078B6) for text links. Ratios are not a substitute for checking focus indicators, disabled states, non-text contrast, or text over gradients.

Interaction checklist

Required in every shipped flow

  • KEYBOARDAll controls are reachable and operable
    Keep a visible focus indicator; do not trap focus.
  • FORMSLabels and errors are programmatically connected
    Use persistent labels, `aria-describedby`, and `aria-invalid` when needed.
  • DIALOGFocus enters the dialog and returns to its trigger
    Provide a clear close action and support Escape.
  • STATUSMeaning is not conveyed by color alone
    Include text and a meaningful icon or shape.
  • ZOOMContent reflows at narrow widths and 200% zoom
    Tables may scroll horizontally inside a named region.
  • MOTIONRespect reduced-motion preferences
    Keep movement brief and nonessential.
11 · Experience patterns

Patterns

Patterns combine individual components into predictable journeys. These initial patterns are derived from the member and provider reference material.

Member sign-in

Keep the secure task focused and recoverable

Authentication
1Ask for the member ID
Keep the label visible; give a short hint about where to find it.
2Collect the password
Mask by default, provide an explicit show/hide control, and support password managers.
3Recover without blame
Place password recovery near sign-in and explain errors in plain language.

Provider search

Make results useful before they become dense

Search & results
1Set the search context
Ask for specialty and location with clear labels and accessible autocomplete behavior.
2Show useful filters
Keep the applied filter count and a clear way to remove filters visible.
3Present scannable results
Show provider name, specialty, location, distance, and network status; include empty and loading states.
Pattern library is a starting pointClaims, biometrics, account creation, and benefit-selection flows need product, clinical, privacy, and security review before their rules are considered standard.
12 · Adoption

Tokens & release process

The downloadable files make the current values reusable. This release is a preview; agree on ownership and a source-of-truth workflow before distributing it as a stable package.

Bring tokens into a project

Use the CSS custom properties and framework-free starter components

Preview v1.0
/* Load before component styles */
@import url("./tokens.css");
@import url("./components.css");

<button class="bh-button bh-button--secondary" type="button">
  Find a doctor
</button>
  • OWNER TBDName a design-system owner and code owner
    Route requests, reviews, and release decisions to named maintainers.
  • POLICY TBDConfirm browser, accessibility, and security policies
    The reference files do not define these release requirements.
  • AUTOMATION TBDChoose a token source of truth
    Generate CSS and JSON from one source to prevent drift.
  • CHANGELOGVersion changes and publish migration notes
    Label breaking changes and support a deprecation window.
Community input

Request an addition

Suggest a foundation, component, pattern, or improvement. A clear problem statement helps the design-system team review the request.

Tell us what is missing

Your request stays in this browser until you download or copy it.

Design-system intake

Do not include member, patient, or other sensitive personal information. This form does not send or store submissions.

Copied to clipboard