Skip to content

fix(landing): rebuild the status pages feature page on the real renderer - #2690

Open
Makisuo wants to merge 5 commits into
mainfrom
t3/fix-status-page-feature-section
Open

Makisuo wants to merge 5 commits into
mainfrom
t3/fix-status-page-feature-section

fix(landing): keep the status page demo frames out of the tab order

cdabe67
Select commit
Loading
Failed to load commit list.
Maple Review Bot / Maple / review succeeded Nov 16, 2026 in 43s

Confidence 9/10 · No issues found

🟢 Confidence 9/10 · safe to merge. The only change since the last review makes the two demo frames inert and adds a screen-reader sentence; contained to static landing markup, no test covers the a11y attributes.
no findings · tests partial −1 · risk medium

Rebuilds the status pages feature demo on @maple/status-page's real renderPage output, inlined at build time into two stacked, script-less iframes. This head replaces the tab-index workaround with inert on both frames plus a visually hidden description; the markup is safe to merge.

  • LiveStatusPage renders demoPageHtml twice instead of a hand-built CSS status page
  • Both demo iframes are inert, with an sr-only sentence describing the demo
  • The stage is a fixed 830px (520px mobile) crop that crossfades operational to outage over 14s

Production impact

Production traffic of the changed files (last 7 days)
File Calls/day Busiest operations
apps/landing/scripts/screenshots/status-page-shots.ts 3.6k maple 3.6k/day, 2.0% err
apps/landing/src/lib/status-page-demo.ts 3.6k maple 3.6k/day, 2.0% err
What was checked
  • sr-only is a live utility across apps/landing (LiveUptime.astro:58), so the new sentence is not rendered visibly
  • Both frames keep sandbox="" and pointer-events: none, so the demo cannot run scripts or navigate
  • The reduced-motion animation: none sits in a later same-specificity rule, so an unanimated visit shows the outage frame

cdabe67 · Reply "won't fix" to dismiss a finding, or mention @maple-review-bot to ask about one.