Window Impact - Everyday Interface Patterns

A static delivery window impact notice shows July 10 morning, July 11 afternoon, Different zone, and Not rescheduled status.

Program

Delivery window impact notices should show the visible consequence of an address change without rescheduling anything.

delivery_window_impact.html

Visuals: captured from real browser rendering

<section class="window-impact" aria-labelledby="window-impact-title"><h2 id="window-impact-title">Delivery window impact</h2><dl>
  <div><dt>Old window</dt><dd>July 10 morning</dd></div>
  <div><dt>New window</dt><dd>July 11 afternoon</dd></div><div><dt>Reason</dt><dd>Different zone</dd></div>
  <div><dt>Status</dt><dd><span class="badge">Not rescheduled</span></dd></div></dl>
  <p class="check">Learner check: the window impact is visible without rescheduling delivery.</p>
  <p class="note">Static delivery impact only; no scheduling service, carrier API, order mutation, calendar lookup, inventory lookup, storage, route, API, network, script, form submit, analytics, timers, or live reschedule runs.</p></section>
<style>
  .window-impact { display: grid; gap: 10px; max-width: 38rem; border: 1px solid #1d4ed8; padding: 12px; background: #eff6ff; }
  .window-impact dl { display: grid; gap: 8px; margin: 0; }
  .window-impact dl div { display: grid; grid-template-columns: 8rem 1fr; gap: 8px; }
  .window-impact dt { color: #475569; }
  .window-impact dd, .check, .note { margin: 0; }
  .badge { border-radius: 999px; background: #dbeafe; padding: 2px 8px; }
  .note { color: #475569; }
</style>

Label the window impact.
The section is labelled by its visible heading.
Show old delivery window.
The old window is exact pinned data.
Show new window and reason.
The new window and reason are exact pinned data.
Render not-rescheduled status.
The status badge says delivery is not rescheduled.
Check window readback.
The check says the window impact is visible without rescheduling delivery.
Check window honesty.
Old window, new window, reason, status, and no live reschedule.

step flow step(1) labels the source, step(2) shows the old window, step(3) shows new window and reason, step(4) shows not-rescheduled status, step(5) checks the delivery impact readback, and step(6) checks the honesty note.

window readback The section heading names the delivery window impact surface.

window rows Old window, New window, Reason, and Status values are exact pinned data.

no live reschedule The lesson should not imply scheduling services, carrier APIs, order mutations, calendar lookups, inventory lookups, storage, routes, APIs, networks, scripts, form submits, analytics, timers, or live reschedules.