/* ---------------------------------------------------------------------------
   Site fixes applied during the static export.

   Bricks renders buttons as <a> elements. AutomaticCSS ships this rule:

       body a:where(:not([class*="btn--"])) { color: var(--link-color, var(--primary)); }

   so every button WITHOUT a `btn--` modifier class inherits the tan link colour
   (--primary, #ac9c8d). Most buttons dodge this because Bricks emits a
   per-element `#brxe-xxxxxx { color: ... }` rule, but ~480 button instances
   across the site were authored without one — several of those sit on the
   yellow fill (#FFD64F), giving 1.9:1 contrast (WCAG AA requires 4.5:1).
   The authors' own :hover rules on the same buttons declare var(--black),
   which confirms the intended base colour.

   The selector below is deliberately specificity-0,2,1: it outranks the
   AutomaticCSS rule (0,0,2) but loses to Bricks' per-element #id rules
   (1,0,0). So buttons that already declare a colour — e.g. the 452 that set
   var(--white) on the tan fill — keep it, and only the ones missing a
   declaration are corrected.
--------------------------------------------------------------------------- */

a.brxe-button:not([class*="btn--"]) {
	color: var(--black, #000);
}