Open Branding → General, set 2 hex colors (primary and accent), and click Save. The new colors apply to your widget, public reports, and PDF exports on the next page view.

What the 2 colors control

Primary is the loud one: buttons, the score ring, the call-to-action. Accent is the quiet one: hover states, link underlines, badge backgrounds. The pair replaces our default colors on every page a prospect sees. Your own dashboard stays neutral, so nothing looks jarring while you work.

Think of it like picking a flag. 2 colors, used consistently, do all the work.

How LemAudit applies them

Both hex values are saved to your brand record. They are sent out as 2 CSS variables (`--brand-primary`, `--brand-accent`), which the widget and the public report page read. We also pick a text color, white or dark, for each one. That way text on top stays easy to read and you never pick a third color.

The change applies on the next page load. To force-refresh the widget on a client site, hard-reload the host page (Ctrl+Shift+R). For the PDF export, the next generated PDF picks up the colors; existing downloaded PDFs do not change.

Worked example

A green-and-orange agency entered #1f7a5a (primary) and #f5b800 (accent). The widget's submit button turned green; the score ring used the same green; the orange showed up as a hover underline on the public report. They tested contrast on a 60-year-old prospect's screen — both passed WCAG AA against white. Total time: 2 minutes.

When this isn't right

Avoid very pale colors (pastel pink, light yellow) for the primary — buttons fail contrast and look broken. If you use the multi-brand panel, set colors per brand there instead of overwriting the main set. For full theme replacement (dark mode, gradient buttons, custom typography), fork the open-source widget repo or contact support — LemAudit does not expose CSS overrides directly.