Make confirmation usable on screen and in print
The screenshot-style confirmation cannot be selected, print cuts off the address, and appointment time omits the time zone.
- Focused work estimate
- 1h 45m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Semantic content · Print CSS · Transaction UX
Estimated field mix
- Accessibility60%
- Frontend40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
The fictional Riverside desk books appointments for permit paperwork and library assistance. Its browser flow was assembled from separate forms and dialogs. Work uses synthetic availability and booking adapters; actual appointments and personal records are excluded.
Setup prerequisites
- Synthetic services, slots, and booking API contract
- Keyboard and screen-reader access for a documented manual check
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- A11Y-101 · Replace clickable service tiles with a named selection group
- A11Y-103 · Make month navigation work without a pointer
- A11Y-105 · Recover when another visitor takes the chosen slot
- A11Y-102 · Keep contact-field help and errors understandable together
- A11Y-104 · Keep the booking action visible at high zoom
- A11Y-106 · Announce availability changes without reading the whole page again
- A11Y-107 · Handle expiry without an inaccessible countdown trap
- A11Y-108 · Return focus correctly after reviewing contact details
Acceptance criteria
- Service, date, time zone, location, and reference are selectable semantic text.
- Print includes all appointment details without navigation chrome or clipping.
- Only confirmed bookings show confirmation, with an accessible copy-reference action.
Implementation constraints
- An HTML print view is sufficient; PDF generation is excluded.
Verification to include
- Confirm a synthetic appointment, copy its reference, and inspect print preview.
- Return an uncertain result and use a long location; no false confirmation appears and reconciled print details remain complete.
Deliverables
- Semantic confirmation and print stylesheet
Rollout and recovery
Release styling after booking-identity checks; retain plain-text details if print styling fails.
Value of the work
For the engineer: Practice accessibility as complete interaction behavior, including recovery and asynchronous updates.
For the team: Inspect whether an engineer removes concrete barriers while preserving appointment integrity and supportability.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.