Colors
Your palette read off the rendered page and its stylesheets, each swatch carrying the evidence line for where it was found.
Check 09 of 14.
What happens
Observed color candidates from captured HTML and linked CSS, retaining declaration counts, selectors, properties and source references. These declarations alone do not establish visible prominence or approved brand roles. When the run's own screenshots are available to the pixel-check path, their separate evidence records whether a candidate appears in those images.
Calls it makes
No call of its own — reads the website leg's captures and their linked CSS, plus a pixel sample of the screenshots leg's own images.
The facts a reader needs
| Language model | None. |
| Cost | No charge — the pixel sample runs against screenshots already captured for the screenshots leg. |
| Depends on | Reads the website leg's captures. |
| When it is absent | Colors set only by images or by script at runtime will not appear. A colour with no screenshot evidence — no screenshots this run, or a decode failure — renders exactly as before this check existed: no verification chip, never a fabricated match. |
Who supplies it
- Firecrawl — The site capture — and with it logos, colors, typography and screenshots.
- Public web sources (no account, no key) — Everything below runs with no key at all, and always has.
Logos
Every mark on your site at usable size, each with the page it came from — and a clear label on any we had to fill in from elsewhere.
Typography
The typefaces actually declared and loaded, split into headings and body — resolved through CSS variables, so you get font names and never variable names.