This is the checklist we use, written down so you can judge it and borrow it. It is our process, not customer results. No customer website has been handed over yet. The checks below have run on a made-up sample business for our Fast Launch kit, and on our own site, crtcai.com. Each check also says what it cannot see.
1. Open the page like a visitor, not just read the files
Our site has a small runner script that starts a local copy of the site and copies how Cloudflare Pages serves it: clean URLs, the security headers from the _headers file, and the 404 page. A scripted Chrome then opens pages and reports what it sees. It checks for sideways scrolling, console errors and failed requests, and takes screenshots. It cannot see anything that only exists on the live host, such as the real certificate, redirects set at the host, or contact-form delivery. Those get their own live steps below.
2. Three widths: 320, 390 and 1280 pixels
At each width we load the page and check that nothing forces a sideways scroll. 320 pixels is the narrowest phone layout, and it is also the width the web accessibility standard uses for its reflow rule: content should fit at 320 CSS pixels wide without two-way scrolling, which is the same as a 1280 pixel window at four times zoom (WCAG 2.2, 1.4.10 Reflow). 390 is our stand-in for a current phone, our choice rather than a survey result. 1280 is a laptop. The Fast Launch kit's own tests also use 390 and 1440 pixels. It cannot see every real phone, or any browser except Chrome.
3. Static checks on the files
A Python script checks every public page for a title, a description, a canonical address, a skip link, a main landmark, unique element IDs and working internal links. It also rejects wording we have banned from public pages, such as phrases that claim more automation than we deliver. A browser test covers the home page and the pay and store pages. A stamping script versions each CSS and JavaScript link, because our host caches those files for a day. They cannot see whether a page is clear or true; the next steps cover that.
4. Lighthouse for speed and basics
Lighthouse is a free tool from Google, built into Chrome DevTools and available on the command line, with audits for performance, accessibility, SEO and more (Chrome for Developers). We run it in mobile mode. It measures one simulated load, a lab result rather than what every visitor sees. Our rule for customer-facing claims: we quote a speed number only if a saved Lighthouse run backs it, and the number goes stale after 30 days.
5. Accessibility: tools first, then hands
An automated score is a start. The W3C says it plainly: tools can't do it all, some checks require manual intervention, and tools can give inaccurate results (W3C WAI). Our Fast Launch kit tests the mechanical parts: one main heading, a label on every form field, a skip link, a menu that works from the keyboard, text contrast at the WCAG AA level from the client's own colors, and tap targets at least 24 by 24 CSS pixels, the WCAG 2.2 minimum (WCAG 2.2, 2.5.8). What a script cannot judge, such as whether the tab order makes sense, takes a person tabbing through the page. This does not prove a site is accessible to everyone. We have not had one tested with people who use screen readers.
6. A claims check on the words
Risky sentences are the ones that carry a percentage or a multiplier, a promise of results, an absolute word, or a claim to stand in for a professional. We run a script over the page text. A risky sentence passes only if it matches an entry in our claims register that records evidence, how it was tested, its limits, a verification date and a named approval. An entry older than 90 days stops counting. Anything unmatched is reported as blocked and we reword it, usually by deleting the claim.
7. The go-live gate, then the live steps
Before a client site goes live, a gate script scans the files for leftover demo text, example addresses and 555-01xx sample phone numbers, and checks that the owner's written confirmation is recorded. The kit's tests prove the files. Our checklist lists what they do not prove, to be done live: real HTTPS on the client's own domain, the host applying its headers, a form message sent from a phone and received, and DNS changes made safely. That last one means exporting every DNS record first and leaving email records alone. Those live steps have not run for a customer, because there has not been one.
What we ran on these four articles
These guides went through the checks above before publication, on 14 November 2026:
- Browser runs at 320, 390 and 1280 pixels wide on all four articles and the articles index: no sideways scroll, no console errors, no failed requests.
- Lighthouse 13.6.0, mobile mode, against a local copy of the site: each article scored 100 in performance, accessibility, best practices and SEO. A local copy has no network delay, so this says nothing about speed on the live host, and a perfect score does not prove a page is accessible.
- Keyboard walk: tabbing from the top, the first stop on each page is the skip link, and every stop shows a visible focus outline.
- Claims check: the stripped text of each article found no risky sentences.
- Static checks: the Python gate and the asset-stamp check pass with these pages added.
Not tested: Safari, Firefox, real phones, a screen reader, and how the pages behave on the live host before they are deployed.
What this checklist does not do
- It runs in Chrome only.
- It is not a third-party audit. Our Truth Center says what an outside source shows, such as a live store listing, and what it does not.
Our Fast Launch Website ($499) is marked CRTC TESTED on our Truth Center: tested on sample data, with no customer delivery yet. For a plain-English look at your current site, ask for the free website check. It is a lighter report than this checklist.