{"id":868,"slug":"client-bjf-lighthouse-status-v2","title":"B&J — Lighthouse status (v2): NOT measurable from production host; needs a desktop DevTools session","kind":"reference","scope":"client-case-studies","status":"current","audiences":["kevin","candid-team","client-prospect"],"topics":["core-web-vitals","client-boucher-jones","case-study-source","kpi-candidates","data-gaps"],"reference_body":"## Why Lighthouse is not in this v2 ingest\n\nLighthouse cannot be run from the production host. `chromium`, `chromium-browser`, `google-chrome`, `chrome`, and `lighthouse` are all absent on CT 104, and **`CLAUDE.md` explicitly forbids installing them.** Verbatim:\n\n> *\"No screenshot pipelines. Visual verification is the human's job in a real browser. Don't install `playwright`, `puppeteer`, or chromium-for-testing.\"*\n\nRunning Lighthouse requires either installing Chromium (forbidden) or running it from a workstation.\n\n**Action for the case study:** run Lighthouse from a desktop browser DevTools session against `https://bjweb.candidcreative.ca/` (and 1–2 representative deep pages: `/agriculture`, `/resources/coloured-diesel-and-ontario-law`). Capture Performance / Accessibility / Best Practices / SEO scores. This unblocks the v1 [[client-bjf-data-gaps-needs-followup]] item #1.\n\n## What was structurally fixed in commit `3514d02` (2026-05-23 audit-closure)\n\nTwo specific Lighthouse failures flagged by a prior third-party audit are now resolved at the HTML/CSS level — a fresh Lighthouse run should reflect these:\n\n- **Color contrast.** `--color-text-tertiary` lifted from `#8a8884` → `#6c6a66` (~5.1:1 contrast on `--color-surface-page`, clears WCAG 2.1 AA for normal text).\n- **Link name.** Coverage-map polygon anchors now carry `aria-label=\"<county> — service area page\"`. Verified live: `aria-label=\"Waterloo Region — service area page\"`, `aria-label=\"Wellington County — service area page\"`, etc.\n\n**The other Lighthouse categories (Performance, Best Practices, SEO) have not been measured on this round.** Once a DevTools Lighthouse run happens, update [[client-bjf-kpi-candidates]] and supersede the relevant v1 status lines.","rationale_body":"Reframes the v1 Lighthouse `[Unknown — to be measured]` line: the host constraint is the reason, not absence of intent. The structural fix evidence stays in case the DevTools run is delayed.","metadata":null,"links":{"outgoing":[{"slug":"client-bjf-technical-seo-posture","title":"B&J technical SEO posture — old vs new, with explicit gaps to close pre-launch","kind":"reference","scope":"client-case-studies","link_type":"relates-to"},{"slug":"client-bjf-data-gaps-needs-followup","title":"B&J — known unknowns that need a human conversation or a tool query before publication","kind":"reference","scope":"client-case-studies","link_type":"relates-to"},{"slug":"client-bjf-kpi-candidates","title":"B&J KPI candidates — every defensible metric, with source and confidence","kind":"reference","scope":"client-case-studies","link_type":"relates-to"}],"incoming":[{"slug":"client-bjf-case-study-source-v2","title":"Boucher & Jones — case-study source material, v2 (technical facts, 2026-05-24)","kind":"reference","scope":"client-case-studies","link_type":"relates-to"},{"slug":"client-bjf-data-gaps-needs-followup","title":"B&J — known unknowns that need a human conversation or a tool query before publication","kind":"reference","scope":"client-case-studies","link_type":"relates-to"}]},"created_at":"2026-05-24T01:16:37.173Z","updated_at":"2026-05-24T01:16:37.173Z"}