A static manual fallback shows Wi-Fi login purpose, 482-19 manual code, Type code entry method, and Fallback available status.

Program

Manual fallbacks help people use the same handoff when scanning is unavailable.

manual_code_fallback.html
Visuals: captured from real browser rendering
<section class="manual-fallback" aria-labelledby="manual-fallback-title"><h2 id="manual-fallback-title">Manual code fallback</h2><div class="code-chip" aria-label="Manual fallback code">482-19</div><dl>
  <div><dt>Purpose</dt><dd>Wi-Fi login</dd></div>
  <div><dt>Manual code</dt><dd>482-19</dd></div><div><dt>Entry method</dt><dd>Type code</dd></div>
  <div><dt>Status</dt><dd><span class="badge">Fallback available</span></dd></div></dl>
  <p class="check">Learner check: the manual code is visible when scanning is unavailable.</p>
  <p class="note">Static manual fallback only; no camera, scanner, scan event, QR generation library, QR decoder, device API, Wi-Fi connection, storage, cookie, route, API, network, script, event listener, form submit, input, textarea, contenteditable, analytics, timer, object URL, download, service worker, account/session behavior, or live submission runs.</p></section>
<style>
  .manual-fallback { display: grid; gap: 10px; max-width: 38rem; border: 1px solid #1d4ed8; padding: 12px; background: #eff6ff; }
  .code-chip { justify-self: start; border: 1px solid #1d4ed8; background: #ffffff; padding: 8px 12px; font-weight: 700; letter-spacing: 0.08em; }
  .manual-fallback dl { display: grid; gap: 8px; margin: 0; }
  .manual-fallback dl div { display: grid; grid-template-columns: 8rem 1fr; gap: 8px; }
  .manual-fallback dt { color: #475569; }
  .manual-fallback dd, .check, .note { margin: 0; }
  .badge { border-radius: 999px; background: #dbeafe; padding: 2px 8px; }
  .note { color: #475569; }
</style>
  1. Label the manual fallback.

    The section is labelled by its visible heading.
    The section is labelled by its visible heading.
  2. Show purpose row.

    The purpose is exact pinned data.
    The purpose is exact pinned data.
  3. Show manual code and entry method rows.

    The manual code and entry method are exact pinned data.
    The manual code and entry method are exact pinned data.
  4. Render fallback-available status.

    The status badge says the fallback is available.
    The status badge says the fallback is available.
  5. Check fallback readback.

    The check says the manual code is visible when scanning is unavailable.
    The check says the manual code is visible when scanning is unavailable.
  6. Check fallback honesty.

    Purpose, code, method, status, and no live submission.
    Purpose, code, method, status, and no live submission.
step flow step(1) labels the source, step(2) shows the purpose, step(3) shows manual code and entry method rows, step(4) shows fallback-available status, step(5) checks the manual fallback readback, and step(6) checks the honesty note.
manual fallback readback The section heading names the manual code fallback surface.
fallback rows Purpose, Manual code, Entry method, and Status values are exact pinned data.
no live entry The lesson should not imply cameras, scanners, scan events, QR generation libraries, QR decoders, device APIs, Wi-Fi connections, storage, cookies, routes, APIs, networks, scripts, event listeners, form submits, inputs, textareas, contenteditable surfaces, analytics, timers, object URLs, downloads, service workers, account/session behavior, or live submissions.