Milestone Risk - Everyday Interface Patterns

A static risk notice shows Copy review needs owner for Beta review with a clear status readback and no reminder or project service.

Program

Milestone risk notices should call attention to exact pinned text without sending reminders or changing project data.

milestone_risk_notice.html

Visuals: captured from real browser rendering

<section class="risk-notice" aria-labelledby="risk-title">
  <h2 id="risk-title">Milestone attention</h2>
  <p><strong>Milestone</strong> Beta review</p>
  <p class="risk" role="status">Copy review needs owner</p>
  <button type="button">Review owner</button>
  <p class="note">Static risk notice only; no reminder service, project API, routing, storage, timer, or analytics runs.</p>
</section>
<style>
  .risk-notice { display: grid; gap: 10px; max-width: 38rem; border: 1px solid #b45309; padding: 12px; background: #fffbeb; }
  .risk-notice p, .note { margin: 0; }
  .risk { border: 1px solid #f59e0b; background: #fef3c7; padding: 8px; font-weight: 700; }
  .risk-notice button { justify-self: start; padding: 8px 12px; }
  .note { color: #475569; }
</style>

Label the risk notice.
The section is labelled by its visible heading.
Show the milestone context.
The milestone name is fixed display data.
Show the pinned risk message.
The risk message is exact lesson text.
Expose the risk readback.
The notice is exposed as status text.
Show the review affordance.
The button is type button and does not route or save.
Check risk notice honesty.
Risk text, status readback, button, and no reminder service.

risk text Copy review needs owner is exact pinned notice text.

status readback role status exposes the risk notice.

no reminder The lesson should not imply reminders, project APIs, routing, storage, timers, or analytics.