Themes — Light, Dark, and High Contrast

Switch between the three built-in themes from any page; how persistence and system preference work.

Three built-in themes

Taskin ships three themes. The button in the top-right of the navigation bar cycles between them — one click each:

ThemeWhen to useToggle glyph
Light (default)Standard daytime use. Ski Blue accents on white.
DarkLow-light environments. Brand colors brightened for accessible contrast on dark surfaces.
High ContrastMaximum readability — pure black/white text, thicker borders, fully saturated brand colors. Targets WCAG AAA contrast for low-vision users.

How to switch themes

  1. Look at the top-right of any page — there's a small circular button next to the language switcher (on phones, open the ☰ menu first).
  2. Click it once. The whole site recolors instantly to the next theme in the cycle.
  3. The page tooltip and the button's screen-reader label both name the current theme and the next one, so you always know what tapping again will do.

System preference and persistence

  • First visit: Taskin reads your OS preference (prefers-color-scheme: dark). If your system is set to dark mode, the site starts in dark. Otherwise it starts in light.
  • After your first manual choice: we remember it. Your selection is stored in your browser's local storage (key taskin_theme) and survives refreshes and tab restores. It's per-browser, so signing in on a different device starts fresh.
  • Privacy: the theme choice never leaves your device. We don't sync it with your account.

For developers

Each theme is a block of CSS custom properties infrontend/src/NewApp.css, selected by a[data-theme="…"] attribute on the<html> element. TheuseTheme hook (frontend/src/hooks/useTheme.js) reads/writes that attribute and persists to local storage; the<ThemeToggle> component in the Navbar wraps the hook's cycle() action. Every styled component consumes var(--color-*) tokens, so adding a new theme is just another [data-theme="…"] block — no per-component fixes required.

If you're building a custom integration and want to set the theme programmatically, the hook's setTheme('dark')/ setTheme('hc') / setTheme('light')calls are stable. Any other string is silently ignored.