With clients · Chapter 22
Checking against the CI
A website that has been looked after for three years nearly always drifts: a blue a touch too light, a font somebody added for a form. The check against the CI finds such things.
Checking a site
- Open Collect
Collect in the header.
- Choose Check against the CI
Under What should happen?.
- Choose the client
It needs a published version; the check runs against the one that applies.
- Give the sources and click Collect
Website, GitHub repository or PDF style guide, as in the chapter Collecting.
What the result says
Under “Checked against 2026”, each colour found stands beside the nearest colour of the CI, measured as ΔE 2000:
| Verdict | Distance | Usually means |
|---|---|---|
| Matches. | below ΔE 1 | all in order |
| Nearly right, ΔE … The CI colour is probably meant. | below ΔE 8 | a wrong shade in a style sheet |
| Not in the CI | above | a foreign colour; its share of everything found stands beside it |
Fonts that do not occur in the CI carry “Not in the CI.” The share helps you weigh it up: a foreign colour at one per cent is a margin, one at thirty is a problem.
Checking code through the API
The same check runs for programs, in a build pipeline for instance, under POST /api/v1/clients/{client}/audit and over MCP with the tool audit.
- Colour values: up to 500 per request, as
#RGB,#RRGGBB, without#,rgb()orhsl(). The verdicts aresame,near(with the colour meant),foreignandunreadable. nexbrand does not read names such asred. - A style sheet: up to 500,000 characters. Its colours join the list, and every CSS rule that sets both text and background colour is checked against forbidden colour pairs of the rules and against 4.5:1. nexbrand resolves
var()through the sheet's own custom properties. - A project: with
project, its palette applies.
Pavo saysIn a style sheet nexbrand only sees pairs within one CSS rule. A ground that an element inherits from outside or that another class sets stays invisible; look for yourself where it matters.