What you have to do
Nothing. This page exists so you can check us the way we’d check you.
Our own report.
2seen.com · 18 readings · 144 checks on 8 pages · last run 2026-09-02 19:05 UTC · PASSED · v0.1.0-710dd69
Every site we deliver comes with the run that measured it. It would be strange to withhold ours.
The artifact
The run that measured the page you’re reading.
- readings against this exact version
- 18
- pages checked
- 8
- measured
- 2026-09-02 19:05 UTC
- result
- PASSED
Why 18 here and 14 on the audit page. They count different things. 14 is how many checks your site would get. This run used 15 of them, because this site also turns on a direction rule it would be wrong to impose on yours — a pinned header, for instance, is a perfectly good decision on most sites and is banned on this one. 3 of those ran twice, once at each screen width. That makes 18 readings. We run ours against the stricter set, and we tell you which set yours ran against.
| Gate | What it measures | Result |
|---|---|---|
| G01 | The page scrolls normally with a mouse wheel | passed on 8 page(s) |
| G01m | The page scrolls normally with a mouse wheel (on a phone) | passed on 8 page(s) |
| G02 | No empty bands, with animations running | passed on 8 page(s) |
| G02m | No empty bands, with animations running (on a phone) | passed on 8 page(s) |
| G03 | No dead columns next to full ones | passed on 8 page(s) |
| G04 | Nothing invisible to a visitor | passed on 8 page(s) |
| G04m | Nothing invisible to a visitor (on a phone) | passed on 8 page(s) |
| G05 | The page works with JavaScript off | passed on 8 page(s) |
| G06 | No errors in the browser console | passed on 8 page(s) |
| G07 | Contrast, keyboard access and alt text | passed on 8 page(s) |
| G08 | Every link and menu anchor goes somewhere | passed on 8 page(s) |
| G09 | Phone and email are tappable | passed on 8 page(s) |
| G10 | Nothing fixed sitting on top of text | passed on 8 page(s) |
| G10m | Nothing fixed sitting on top of text (on a phone) | passed on 8 page(s) |
| G11 | Images, favicon and share previews | passed on 8 page(s) |
| G12 | Language and voice fit the market | passed on 8 page(s) |
| G13 | Hover and focus states stay legible | passed on 8 page(s) |
| G14 | Every design token resolves | passed on 8 page(s) |
Automated gates measure what can be measured. They don’t replace judgement about whether the site is the right site.
Coverage
What the run found, and what it never looked at.
These four numbers are not one number. A finding and a crash are opposite kinds of bad news, and a report that adds them together is hiding one of them.
0 of 18 readings
Found a defect. The check looked and something was wrong. This is a result: it tells you what to fix.
0 of 18 readings
Crashed before they could look. Not a pass and not a finding either — that check produced no answer in either direction. It counts against the verdict all the same, because a tool that can’t fail isn’t verifying anything.
0 measurements
Skipped. Readings this run didn’t take. Whatever they would have said, this report doesn’t say it.
0 declared
Declared out of scope by the run itself. A different list from the one above: these are the things the run states it can’t speak for, written down so that reading only the green part still tells you what the green part covers.
Every gate ran on every page listed above.
The instrument
Why this is green, and why that isn’t the proof
This report is green because a red one would have stopped the deploy. That’s the rule here: if the site belonging to the people who sell verification doesn’t pass verification, it doesn’t go up.
Which means the green above proves the checks ran. It doesn’t prove they can fail — and that’s the only question worth asking about a measuring instrument.
For that, look at the run against the file we keep permanently broken. Eighteen readings, forty-two findings, and it has never been repaired.
The failing runAfter launch
What happens when we go red
Certificates expire. Links rot. A dependency changes underneath you. When a check on this site fails after launch, the finding appears on this page with the date it appeared and the date it was fixed.
Freshness
If the date above is old
This report is generated by the build, not by a live monitor. Nothing on this page is watching anything right now, and we’re not going to imply otherwise with a green dot.
The line at the bottom of every page carries the date of that run and the version it measured. What decides whether it still counts isn’t its age: it’s whether the version it measured is the version you’re reading. When it isn’t, this site shows you no result at all rather than a green one that has stopped being about this code.
The page the engine is measured against
The page the build system is measured against. It isn’t a client project and it isn’t a portfolio piece: it’s the reference the engine is checked against, and it’s here because the report above measured it.