Announce availability changes without reading the whole page again
Each refresh rewrites a large live region. A screen reader repeats all slots and interrupts contact entry even when nothing changed.
- Focused work estimate
- 2h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Live regions · Async interaction · Assistive technology
Estimated field mix
- Accessibility70%
- Frontend30%
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
- Unchanged slot lists generate no routine announcements.
- Meaningful changes produce a short status without moving focus.
- Loss of a selected slot takes priority over routine counts; stale request messages are ignored.
Implementation constraints
- Use a small status region and coalesce bursts; never mark the entire form live.
Verification to include
- Refresh identical data three times while typing; no repeated list announcement occurs.
- Remove the selected slot while delayed old data arrives; announce loss once and retain current focus.
Deliverables
- Announcement coordinator and manual speech-output log
Rollout and recovery
Pilot with routine announcements disabled; retain only actionable notices if speech becomes noisy.
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.