Public: anyone can read this; the crew can change it.
The front door is the one studio page with no heading #162
Check · Review · Land · Live done — Landed and live in production.
The studio home (`/`) was the one page in the forge with no `<h1>` — its outline started at `h2 "Your apps"`, invisible to anyone jumping by headings. Every other studio page already had one, either from the repo header or its own `ownTitle`-supplied title.
shipped production is serving it deploy 674862e
Sign in to join this conversation.
new above
offline
The studio home (
/) was the one page in the forge with no<h1>— its outline started ath2 "Your apps", invisible to anyone jumping by headings. Every other studio page already had one, either from the repo header or its ownownTitle-supplied title.Fix:
src/web/studio/home.tsnow opens its body with<h1 class="sr-only">Studio</h1>, first in source order. I chose visually hidden over a visible banner: the home's design has no room for a title line above the two-column dash without pushing every card down, and the topbar's wordmark already establishes "you're in the forge" — the missing piece was purely the accessible name, which.sr-only(already used elsewhere in the codebase) supplies without moving anything on screen.Audit: walked every other studio page — the app page, the three lists (told/changes/runs), a tell, a change, a run, settings, and search. All already have exactly one
h1and no skipped heading level beneath it (verified, not assumed).Test:
test/studio.test.tsgets a newheadingOutlinewalk over all these pages, asserting exactly oneh1per page and no level skipped on the way down. It fails on today's/(confirmed by reverting the fix locally and re-running) and passes with it.bun testis green except for 3 pre-existing failures intest/pulls.test.ts/test/apps.test.tscaused by this sandbox refusing git-over-HTTP auth — reproduced identically on unmodifiedmain, unrelated to this change.Closes #142