Access Revoked - Everyday Interface Patterns

A static access notice shows Access revoked, fixed date 2026-07-02, a Request access button, and no account check, permission service, or request submission.

Program

Access notices should show the visible state and next possible action without checking an account or sending a request.

access_revoked_notice.html

Visuals: captured from real browser rendering

<section class="access-revoked" aria-labelledby="revoked-title">
  <h2 id="revoked-title">Access revoked</h2>
  <p><strong>Status</strong> <span class="badge">Access revoked</span></p>
  <p><strong>Date</strong> 2026-07-02</p>
  <button type="button">Request access</button>
  <p class="note">Static access notice only; no account check, permission service, or request submission runs.</p>
</section>
<style>
  .access-revoked { display: grid; gap: 10px; max-width: 38rem; border: 1px solid #b91c1c; padding: 12px; background: #fef2f2; }
  .access-revoked p, .note { margin: 0; }
  .access-revoked button { justify-self: start; padding: 8px 12px; }
  .badge { border-radius: 999px; background: #fee2e2; padding: 2px 8px; }
  .note { color: #475569; }
</style>

Label the access notice.
The section is labelled by its visible heading.
Show the revoked heading.
The heading makes the access state visible.
Show the revoked status badge.
The badge repeats the pinned state for quick scanning.
Show the fixed access date.
The date is fixed display text.
Show the request affordance.
The button names a possible next action without submitting a request.
Check access honesty.
Revoked status, fixed date, button, and no permission service.

revoked status The access state is pinned display text.

fixed date The date is deterministic lesson data.

no request service The lesson should not imply account checks, permission services, or request submission.