Keep the booking action visible at high zoom
At 400% zoom the fixed step header and cookie banner cover the selected time and Continue button. Repair reflow across booking steps.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- CSS layout · Reflow · Visual verification
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.
Acceptance criteria
- At the documented desktop viewport and 400% zoom, essential content reflows without horizontal page scrolling.
- Fixed UI never covers focused fields, error links, or booking actions.
- Long service names and expanded text spacing do not clip labels or values.
Implementation constraints
- Use normal flow where fixed positioning provides no user benefit.
Verification to include
- Complete service and slot selection at 400% zoom by keyboard.
- Apply expanded text spacing and a long service name with an error summary; check clipping and focus obstruction.
Deliverables
- Reflow corrections and viewport/zoom evidence notes
Rollout and recovery
Check every step before shared layout release; revert sticky behavior first if actions become obscured.
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.