Read the page
It opens the URL in a real browser, walks the rendered DOM, and records the computed value of every element it meets.
- h148px / 1.04
- p15px / #8b8b93
- button38px tall
- sectiontext-align: center
Point it at a URL. It opens the page, reads every rendered element against your design contract, and files what it found.
Every finding carries the element it came from, the value it measured, and the one token that would fix it.
Read the page, hold it against the contract, recompose what drifted, and file every step of it.
It opens the URL in a real browser, walks the rendered DOM, and records the computed value of every element it meets.
Your tokens, your ratios, your spacing steps. The contract lives as a file in your repo, and every scan reads it.
Where a value drifted, it names the token that belongs there and shows both, so you approve a swap.
Every pass lands in the catalogue with its score, its findings and the diff, so the next reader starts from the record.
It found nine grey values on a page we had already signed off. Not opinions - the computed values, listed.
SSarah BennettHead of Brand DesignThe findings come back as token swaps. I read them in a pull request instead of a comment thread.
OOwen ClarkeFront-end LeadWe scan the landing page before the campaign spend starts. Twice now that has been a morning, not a relaunch.
PPriya RamanDirector of MarketingPaste a URL. The first scan is free and comes back in under a minute.
Run a scan