/* -----------------------------------------------------------------------
   rebuild-contrast.css - contrast fixes Josh asked for (DECISIONS V17).

   The consultation form (in the header on every route, and on /contact-us/)
   draws its fields dark - rgb(45,42,45) - and leaves the placeholder at the
   browser's default #757575: 3.1:1 on that fill, under WCAG AA's 4.5:1. The
   placeholders are the only labels these fields have, so they get #c8c8c8
   (8.5:1) - clearly readable, yet still dimmer than the white text a visitor
   types (14.2:1), so a filled field still reads differently from an empty one.
   ----------------------------------------------------------------------- */
.tucson-divorce-law-consult::placeholder {
  color: #c8c8c8;
  opacity: 1; /* Firefox dims placeholders to 54% by default */
}

/* The phone menu - TinyNav's <select>, shown under 600px - is 12px grey #7a7a7a
   text on a transparent fill over the dark tan menu band (DECISIONS V19; Josh,
   2026-09-11: "make the menu with better contrast"). It gets the form fields'
   dark fill with white text (14.2:1) and a light border. `color-scheme: dark`
   makes Chrome draw the native arrow and the open option list for a dark control,
   so the arrow does not vanish into the new fill. The `#menu` id outranks the
   theme's own `#menu select { background:none; border:1px solid #000 }`
   (darky.css) - a bare `select.tinynav` loses to it on fill and border. */
#menu select.tinynav {
  color-scheme: dark;
  background-color: #2d2a2d;
  color: #fff;
  border-color: #c8c8c8;
}

/* The OPEN list is drawn by the browser, not the page, and not every browser
   honours `color-scheme` there: it stays white, while the options inherit the
   control's white text - white on white, only the highlighted row visible
   (Josh, 2026-09-11). The options get their own dark-on-white (15.9:1), so the
   list reads the same everywhere; the closed control stays white on dark. */
#menu select.tinynav option {
  color: #222;
  background-color: #fff;
}