Checks

This site was built from a written spec. Each line below is something the site says about itself, with the check that tests it and the result for this build. Select a result to see the check’s code. The last three are things we say about Tenseon that can’t be proven yet, and what would prove them.

Build a597fd19b6 · 2026-11-13 · 10 of 10 site checks passing3 not proven yet

Checks for this website and claims about Tenseon
Check	Claim	Result
W-01	The home page weighs under 150 KBHow we check: Compress every file the home page loads (the page, its styles, script, icons and fonts) with Brotli, the way a server sends them, and add up the bytes. A real browser also loads the page with an empty cache and checks the same set of files.	62.2 KB8 files, Brotli-compressed: index.html, assets/img/tenseon-favicon-32.svg, assets/img/tenseon-favicon-16.svg, assets/img/apple-touch-icon.png, assets/fonts/archivo.woff2, assets/fonts/sourceserif4-400.woff2, assets/css/site.css, assets/js/site.js. In a real browser (Chrome 157.0.8103.40, 2026-11-13): A cold load fetched 6 files, all included in the size count.
W-02	This site uses no cookies and no browser storageHow we check: A scan of the site’s scripts and headers finds no cookie or storage code, and no header that sets a cookie. Then a real browser visits every page and opens a check while recording any attempt to write a cookie or to use localStorage, sessionStorage, IndexedDB or the cache storage. There must be none. This covers the pages and the check dialogs; the form is tested when it’s switched on.	0 cookies, 0 storageNo script uses cookies, localStorage, sessionStorage or IndexedDB, and no header sets a cookie. In a real browser (Chrome 157.0.8103.40, 2026-11-13): No attempt to use a cookie or browser storage, no cookie headers, and nothing stored after visiting all 10 pages and opening a check on each page that has one.
W-03	Nothing on this site loads from anyone elseHow we check: Every file a page asks for must come from tenseon.com: no trackers, no font services, no CDNs. A real browser records every request while it visits every page and opens a check, with the site’s real security headers applied, and the headers themselves block anything from elsewhere.	0 off-site requestsEvery file every page loads comes from tenseon.com itself. In a real browser (Chrome 157.0.8103.40, 2026-11-13): 60 requests across 10 pages, all to this site, with the site’s security headers applied and no blocked requests.
W-04	Our text colours meet the WCAG AA contrast standardHow we check: The stylesheet lists every text and background colour pairing it uses. Work out the contrast ratio of each pair, in the light and dark themes. Each must be at least 4.5:1, and the check fails if a listed colour doesn’t exist. A list can miss a pairing, so the rendered text is also checked by the accessibility audit, W-07.	lowest 4.88:18 pairs of text and background colours, each checked in the light and dark themes (16 in all). Lowest: steel text on paper, light theme, at 4.88:1. AA needs 4.5:1.
W-05	Every page reads in full with JavaScript turned offHow we check: Load each page in a real browser with JavaScript off and compare all of its visible text, including the header and footer, with the normal page. Nothing may be missing.	In a real browser (Chrome 157.0.8103.40, 2026-11-13): All 10 pages show the same text, header and footer included, with JavaScript off.
W-06	If you ask your device to reduce motion, nothing movesHow we check: Load each page in a real browser set to reduce motion. Count the running animations for a second after it loads, after scrolling to the bottom, and with a check open. The count must be zero every time. This covers CSS and script animations; it can’t see motion drawn frame by frame.	In a real browser (Chrome 157.0.8103.40, 2026-11-13): 0 running animations on all 10 pages: sampled for a second after loading, after scrolling, and with a check open.
W-07	An automated accessibility audit finds no problemsHow we check: Run axe-core, an open-source accessibility checker, on every page against its WCAG 2.2 AA rules, at phone and desktop widths, in light and dark themes, and also with a check open and with the form showing its error messages. It must report zero violations. Automated checks catch only some problems. They don’t replace testing by hand with a keyboard and a screen reader, which we haven’t recorded yet.	In a real browser (Chrome 157.0.8103.40, 2026-11-13): 0 violations in 44 audits: 10 pages at phone and desktop widths in light and dark, plus a check open.
W-08	Our fonts are licensed for the webHow we check: Every font the stylesheet uses must ship with its SIL Open Font License, which permits web use. This checks the licence files are present for each font family; where the fonts came from is recorded in the source.	2 of 2 licensedArchivo and Source Serif 4, both under the SIL Open Font License 1.1, which allows web use. Licences ship at /assets/fonts/.
W-09	Every page has a title, a language and one main headingHow we check: Read every built page and check for exactly one h1, a language attribute, a title, a description, and alt text on every image.	10 pagesAll 10 pages have exactly one h1, a language, a title and a description, and every image has alt text.
W-10	Every “checked” mark on this site points to a real checkHow we check: Every mark on every built page must point to a defined check, and every check must be cited somewhere on the built site. This checks the links between claims and checks. It doesn’t prove we marked every claim we make.	13 markers13 claims are marked across 10 built pages; every mark links to its row on the checks page, and each one has a check or is openly marked not proven.
C-01	Our core software will be released under Apache 2.0How we check: The repositories will be public, each with the Apache 2.0 licence file.	No code is public yetNothing is published yet. Once repositories are public, this becomes a check that reads each one’s licence file.
C-02	Replacing a tool with Tenseon saves moneyHow we check: For each replacement: the customer’s bill before, the cost after (including our fee), and the difference, agreed with the customer in writing.	No replacements yetWe haven’t done one. When we have, the measured numbers go here, with the customer’s permission.
C-03	We will publish what each ticket costs to buildHow we check: The factory will record the compute cost and human review time of every ticket, and a public build log will list them.	No public build log yetThe build log isn’t public yet.