• highaccessibility: enlarged phone text clips help and pushes pause offscreensrc/style.css:36

  Now: At 200% text size the nonwrapping header, intro metadata and keyboard footer exceed the phone width; the pond clips the How to play label, and Pause is entirely offscreen at 320px.

  Change to: Add wrapping and an automatic/minimum height to the narrow-screen .site-header, let .intro-meta wrap its children, and wrap .footer-controls within the viewport. Preserve the enlarged text and 44px buttons; let the pond move down when the header needs another row.

  Why: The brief requires desktop/mobile usability, and the review bar disallows horizontal overflow or clipped control text. Enlarging text must not remove access to pause or instructions.

  Chromium, 320×844: load dist/index.html through HTTP, run document.documentElement.style.fontSize="200%" in DevTools (text enlargement, not native browser zoom), and wait for ResizeObserver.

  Before starting, document.documentElement.scrollWidth is 343px for a 320px viewport; #intro-help spans x=195..349.40625 while #pond clips at x=310, cutting 39.40625px off How to play.

  Click Start hopping: document scrollWidth becomes 394px and #pause spans x=349.671875..393.671875, entirely beyond the right viewport edge; .footer-controls spans x=-68.09375..388.09375.

  Expected: complete labels and usable controls within 320px, with vertical reflow if needed.

  The same 200% fixture at 390px also overflows during play.

  Normal-size taste@1 layout passed; this failure is the enlarged-text state.

  whole reproduction

• mediumaccessibility: mobile control instructions lose contrast over the foreground reedssrc/style.css:90

  Now: #tip-detail uses muted 13px text over the unbacked Canvas scenery. On the 390px system-font fallback, its first letter overlaps a bright foreground reed and the rendered contrast drops to 3.31:1. The existing accessibility test fails in this state.

  Change to: Give .game-tip a solid --color-page background with modest vertical padding, keeping its existing inset and responsive text wrapping; alternatively darken only the scenery directly behind the entire helper area until every helper-text background reaches 4.5:1.

  Why: The brief requires readable contrast and clear onboarding. The keyboard instructions are essential interface text, and normal-size text must meet 4.5:1.

  Chromium 155.0.8059.12, 390×844, prefers-reduced-motion: reduce, default system-font fallback: load the production export and click Start hopping. #tip-detail reads "Or arrows / WASD to aim, Space to hop" at 13px/400 with rgb(177,196,187) foreground.

  The delivered tests/accessibility.mjs, run unchanged against an identical isolated build, reports "CONTRAST 390px playing #tip-detail: 3.31:1" and fails at line 60.

  Its sampled text rectangle is x=67.8125,y=748,width=254.359375,height=15; worst rendered background is rgb(64,108,75).

  Inspect the first O at approximately x=68,y=753: it sits on the foreground reed (raw Canvas rgb(70,115,79), before the vignette).

  Expected minimum 4.5:1.

  The taste@1 entry-page pass does not measure this gameplay text over Canvas.

  whole reproduction

• lowtaste: primary actions combine a border with raised and blurred shadowssrc/style.css:52

  Now: The warm primary action has a light 1px border plus a 3px solid lower shadow and a second blurred shadow, repeating the edge treatment on Start and the modal primary actions.

  Change to: Set .primary border to 0; retain its warm fill, existing pressed/unpressed lower edge, padding and minimum heights.

  Why: taste@1 chrome disallows a border and shadow on one surface. Removing the redundant outline keeps the intentional raised arcade-button feedback and the current layout.

  At 390×844 and 1440×900, load the production entry and inspect #start. taste@1 chrome reports "border and shadow together: 1 (#start)".

  Computed source values are border:1px solid #f4deb1 and box-shadow:0 3px 0 #b89c59,0 6px 18px #0b272933; the screenshot shows both the pale top/side outline and the ochre lower edge.

  Open Pause or How to play to see the same .primary treatment.

  Expected: one edge/elevation treatment while the button remains visibly actionable.

• lowfidelity: the requested light trails are absent from the hop animationsrc/art.ts:188

  Now: The frog follows a hop arc, and collection produces an outward particle burst, but there is no fading light trail along movement. Ambient flies have stationary radial glows; the background is repainted every frame.

  Change to: Reuse the existing warm particle palette to leave a short, fading trail along the hop path, and suppress that trail when renderer.reduced is true. Keep the current pad silhouettes, composition and hop timing.

  Why: The brief explicitly includes "light trails" among its requested subtle animations. Existing glow and landing feedback satisfy other effects but omit this visual detail.

  At 390×844 with reduced motion off, start a fresh round and hop from the center pad (12) to the firefly immediately above it (7).

  Inspect the 250ms flight frame by frame: sampled departure and midpoint frames show only the frog at its current position, with no fading marks behind it; after landing, the +10 collection burst appears instead.

  The rendering branch at src/art.ts:188-193 draws one interpolated frog and no trail; src/main.ts:221 skips hop events before renderer.burst is called.

  Expected: a brief visible light trail during the hop, absent only with reduced motion enabled.

  whole reproduction

Failed in the task.