/*
 * The design tokens. Every colour, space and type value the signup surface uses is declared HERE and
 * referenced as a custom property elsewhere, so a raw hex value anywhere outside this file is a
 * finding a reviewer can see without opening a design tool.
 */
:root {
  --rome-color-surface: #fbf9f7;
  --rome-color-ink: #1c1a19;
  --rome-color-ink-muted: #5a5450;
  /*
   * The border of every text input and of the fieldset, and therefore a NON-TEXT CONTRAST value
   * (WCAG 2.1 AA 1.4.11) rather than a decorative one: the input's fill is the same literal as the
   * page surface, so this line IS the visual boundary a user needs to perceive to operate the
   * field. It was #d8d1ca, which measures 1.44:1 against #fbf9f7 by the relative-luminance formula
   * - under the 3:1 floor. #938e89 measures 3.09:1 against the page surface and 3.25:1 against
   * white. axe-core cannot decide this: jsdom computes no layout, so colour-contrast comes back
   * INCOMPLETE and apps/web/src/__tests__/a11y.test.ts asserts that it does rather than reading the
   * green as coverage. This value was computed by hand and is owed a real-engine check.
   *
   * THE OTHER HALF IS NOT FIXED HERE AND IS NOT THIS VALUE'S TO FIX: the input fill
   * (--rome-color-accent-ink) is the same literal as --rome-color-surface, so the field's
   * CLICKABLE AREA is still marked only by this one-pixel outline. Choosing a distinct field
   * surface is a palette decision for whoever owns these tokens, not a contrast arithmetic fix.
   */
  --rome-color-line: #938e89;
  --rome-color-accent: #6b3f2a;
  --rome-color-accent-ink: #fbf9f7;
  --rome-color-danger: #8a2b20;

  --rome-space-1: 0.5rem;
  --rome-space-2: 1rem;
  --rome-space-3: 1.5rem;
  --rome-space-4: 2.5rem;

  --rome-radius: 0.25rem;
  --rome-measure: 28rem;
  --rome-font-body: ui-serif, Georgia, "Times New Roman", serif;
  --rome-font-size-body: 1rem;
  --rome-font-size-title: 1.75rem;
  --rome-font-size-small: 0.875rem;
  --rome-focus-ring: 0.1875rem;
}
