Phone Fallback Notice - Everyday Interface Patterns

A static fallback notice shows old phone ending 0142, fallback available, sign-in until confirmed, and Safety notice status.

Program

Fallback notices should show that the old phone remains available until confirmation without changing auth state.

old_phone_fallback_notice.html

Visuals: captured from real browser rendering

<section class="phone-fallback" aria-labelledby="phone-fallback-title"><h2 id="phone-fallback-title">Old phone fallback notice</h2><dl>
  <div><dt>Old phone</dt><dd>ending 0142</dd></div>
  <div><dt>Fallback</dt><dd>Available</dd></div><div><dt>Sign-in</dt><dd>Until confirmed</dd></div>
  <div><dt>Status</dt><dd><span class="badge">Safety notice</span></dd></div></dl>
  <p class="check">Learner check: the fallback is visible without changing sign-in state.</p>
  <p class="note">Static old phone fallback notice only; no account switch, auth session change, SMS service, notification send, storage, route, API, network, script, event listener, form submit, analytics, timer, or live fallback change runs.</p></section>
<style>
  .phone-fallback { display: grid; gap: 10px; max-width: 38rem; border: 1px solid #b45309; padding: 12px; background: #fffbeb; }
  .phone-fallback dl { display: grid; gap: 8px; margin: 0; }
  .phone-fallback dl div { display: grid; grid-template-columns: 8rem 1fr; gap: 8px; }
  .phone-fallback dt { color: #475569; }
  .phone-fallback dd, .check, .note { margin: 0; }
  .badge { border-radius: 999px; background: #fde68a; padding: 2px 8px; }
  .note { color: #475569; }
</style>

Label the fallback notice.
The section is labelled by its visible heading.
Show old phone row.
The old phone is exact pinned data.
Show fallback and sign-in rows.
The fallback and sign-in values are exact pinned data.
Render safety notice status.
The status badge says this is a safety notice.
Check fallback readback.
The check says the fallback is visible without changing sign-in state.
Check fallback honesty.
Old phone, fallback, sign-in, status, and no live fallback change.

step flow step(1) labels the source, step(2) shows the old phone, step(3) shows fallback and sign-in rows, step(4) shows safety notice status, step(5) checks the fallback readback, and step(6) checks the honesty note.

fallback readback The section heading names the old phone fallback notice surface.

fallback rows Old phone, Fallback, Sign-in, and Status values are exact pinned data.

no live fallback change The lesson should not imply account switches, auth session changes, SMS services, notification sends, storage, routes, APIs, networks, scripts, event listeners, form submits, analytics, timers, or live fallback changes.