[NewWorldVenture]

A11Y-001: the kitchen display (/display) is the open "/display at narrow widths" item. The defect is not about width or theme.

The defect

The display paints a time-of-day gradient behind every tile. It is on by default (ambient: true in lib/display/ambient.ts). Each theme has bright stops:

• pink-300 at dawn;
• sky-300 in the morning;
• orange-400 in the evening;
• amber-400 and cyan-400 in others.

Most of the display's text is text-white/50–/60 (50 of its 66 text-white/NN classes were below /70).

axe could not see it. The wash is a fixed -z-10 layer, so axe measured against the page's body colour instead:

• dark theme: "passes";
• light theme at 390 px: "1.04:1, white on #f6f7fc", which is not what is on screen either.

Measured from the pixels instead: a seeded local household, Chromium, the evening theme. Every visible text leaf is recorded with its computed colour, all text is then made transparent, and the background is sampled under each text box. The darkest-to-lightest pixel is the worst case. The text colour is composited over it as the browser would.

Text below AA (worst pixel)	main	This branch
390 px	16 of 17 leaves, 1.4–3.4:1 (e.g. "Bubaly Kitchen" 1.66, the setup card's body 2.10, "Saturday, October 10" 2.98)	3 of 17, all over the featured recipe's photo (see "Not covered")
1280 px	16 of 22 leaves, 1.85–3.71:1 (e.g. "Today's Schedule" 2.70, "Nothing scheduled today" 2.59)	1 of 22, the featured recipe's label over its photo

The fix

• A scrim. The display's own ink (#0b1020) lies at 75% over the wash and its glows (a new fixed -z-10 layer after them, only when ambient is on). Each theme keeps its hue, at a quarter of the strength.
• Text opacity. Body text on the display, and on its reconnect and error screens, is text-white/70 or more: 50 classes went from /25–/60, plus the timer input's placeholder. Hover states that were already /70–/100 are unchanged.
• The floating hints pill ("✅ 20 chores due today — who's on it?") is bg-black/70, not /45, so it holds 4.5:1 even over a white photo pixel.

The non-ambient display (a solid #0b1020) and the photo backdrop mode are otherwise unchanged.

Tests

tests/the-kitchen-display-text-is-readable-on-its-ambient-wash.test.ts reads, from the source:

• every colour a theme's wash or glow can put behind a tile (lib/display/ambient.ts);
• the scrim (display-grid.tsx);
• every bare text-white/NN on the display (components/display/*.tsx, the page and its error screen).

It then composes, the way the browser does:

• the faintest text, on a bg-white/10 tile (the strongest tint behind body text), over each theme's brightest colour: 4.5:1 at worst required;
• solid white on the setup card's bg-white/15 button, over the same colours;
• the hints pill over a white pixel.

Non-vacuity: dawn's and morning's bright stops are found, ambient is on by default, there is a scrim, and there are more than 40 text classes. The control is the same text without the scrim, under 3:1.

Check	main	This branch
The new test	3 of its 4 source cases fail (the control passes)	5/5
The 39 display suites	—	859/859
Pixel measurement above (author-run, local production builds, not committed)	16/17 and 16/22 below AA	3/17 and 1/22, all on the recipe photo
tsc / eslint	—	0 / clean

Not covered: text over photographs

The featured recipe tile puts its label ("Featured Recipe", white/70), its name and its category over the recipe photo. The photo's overlay (from-black/80 via-black/25 to-transparent) leaves bright plate pixels behind the label: 1.00 and 2.34 at the worst pixel at 390 and 1280 px. At 390 px the text block covers most of the short tile, so holding 4.5:1 against every pixel would take about 70% black over nearly the whole photo. That is a design decision, so I have left it for you. The options are:

• a stronger, taller scrim;
• a solid band behind the text;
• a smaller title at narrow widths;
• a text halo.

The photo backdrop mode (background: 'photos') has the same question.

The hints pill's new value is verified by the arithmetic in the test. A pixel reading of it was inconclusive, because the pill fades between hints.

No migration, configuration or dependency change.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TRY21ZKsFrfB3qtoP972A4

---

Generated by Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
bubaly	Ignored		Oct 11, 2026 6:02am UTC

[NewWorldVenture]

Audit follow-up on 06754d5 — bounded repair/test work for the existing owner.

P2: the ambient contrast test omits nested surfaces and hover states. The 10px timer duration text (white/70) is on a white/10 button, white/20 hovered, inside the display-grid white/6 tile. Using the same morning #7dd3fc stop and 75% black scrim, composing all layers predicts about 4.27:1 idle and 3.43:1 hovered. The 14px semibold setup-guide label is white on white/15, white/25 hovered, inside its own white/7 card; it is outside the grid. That predicts about 5.72:1 idle and 4.41:1 hovered. These are source-derived bounds, not observed pixel failures.

Please extend the existing test to derive and compose the actual parent/child layers and interactive states, adjust both controls to clear 4.5:1, and verify the timer picker and setup-guide interactions in the bright ambient themes. Preserve keyboard/focus behavior and existing handlers. The loading text's animate-pulse also changes effective opacity, so do not treat the bare white/70 class as a full-animation guarantee.

Scrim ordering and pointer exclusion look coherent. Photo/recipe contrast remains the separately acknowledged open scope. Return the repair commit and exact-head tests; distinguish arithmetic checks from rendered measurements. No deployment or production changes.

[NewWorldVenture]

Re 01:21Z (nested surfaces and hover states), at d77aae16e, which sits on a merge of current main (cf3b79c0c, no conflicts). Handlers, keyboard and focus are unchanged.

What changed

• The timer duration and "Add timer" text go to full white. The finished timer's pulse moves to an aria-hidden layer under steady text, so the words no longer fade.
• The setup guide's hover tint goes from white/25 to white/20. The loading text and the schedule's "now" row and badge, which a new sweep found, are raised.
• The contrast test now reads the JSX with the TypeScript parser and follows each component to where it is mounted (grid tile white/6, setup card white/7). It composes every text in five states: idle, hovered (on the element and any ancestor), focused, and the faintest frame of a looping animation, taken from Tailwind's own keyframes. A control fed the pre-fix classes reproduces your 4.27/3.43 and 5.72/4.41 exactly.

Arithmetic, worst stop sky-300 under the 0.75 scrim (before → after)

Control	Idle	Hovered
Timer duration	4.27 → 6.73	3.43 → 5.13
Setup guide	5.72 → 5.72	4.41 → 5.01
Add timer		3.95 → 5.13

The finished label goes from 2.89 to 6.34, loading text from 3.19 to 5.31, the now-row time from 4.41 to 5.25, and the Now badge from 3.37 to 4.90.

Rendered. A new spec drives the real DisplayShell, setup card and KitchenTimers on the compiled CSS, in Chromium at 1280×900, DPR 2, dark. It measures glyph pixels against the same pixels without text, in all nine wash themes. Morning: duration 6.75 idle and 5.14 hovered, guide 5.79 and 5.05 hovered, and every theme clears 4.5. Run on the pre-fix code, it measures 4.25 and 3.41 for the duration and 4.44 for the guide hovered. A behaviour case checks that Tab, Enter and Space start and reopen a timer and that Got it dismisses the card.

Checks: tsc exit 0; eslint --no-ignore on the 7 changed files; npm run i18n:gate clean; 24 related vitest files (330 tests); the new spec 11/11. The new unit cases fail 5 of 11 against the pre-fix components. An independent review found nothing blocking.

Not covered: the page's own radial tint is in the rendered spec only. Rendering is dark theme at one viewport. Text over photos stays out of scope as before.

---

Generated by Claude Code