Delivery Exception - Everyday Interface Patterns

A static delivery exception notice shows Delayed status, fixed date 2026-07-05, a Contact support button, and no carrier alert, notification delivery, or order update.

Program

Delivery exception notices should make the status and fixed date visible without claiming a live carrier alert or order update.

delivery_exception_notice.html

Visuals: captured from real browser rendering

<section class="delivery-exception" aria-labelledby="exception-title">
  <h2 id="exception-title">Delivery exception</h2>
  <p><strong>Status</strong> <span class="badge">Delayed</span></p>
  <p><strong>Date</strong> 2026-07-05</p>
  <button type="button">Contact support</button>
  <p class="note">Static exception notice only; no carrier alert, notification delivery, or order update runs.</p>
</section>
<style>
  .delivery-exception { display: grid; gap: 10px; max-width: 38rem; border: 1px solid #b45309; padding: 12px; background: #fff7ed; }
  .delivery-exception p, .note { margin: 0; }
  .delivery-exception button { justify-self: start; padding: 8px 12px; }
  .badge { border-radius: 999px; background: #ffedd5; padding: 2px 8px; }
  .note { color: #475569; }
</style>

Label the exception notice.
The section is labelled by its visible heading.
Show the exception heading.
The heading names the displayed delivery problem.
Show the delayed status.
The badge makes the pinned exception status visible.
Show the fixed exception date.
The date is fixed display text, not a live carrier alert.
Show the support affordance.
The button names a possible next action without contacting a service.
Check exception honesty.
Delayed status, fixed date, button, and no alert service.

exception status The Delayed status is pinned display text.

fixed date The date is fixed lesson data.

no alert service The lesson should not imply carrier alerts, notification delivery, or order updates.