Keep contact-field help and errors understandable together
A phone-field error replaces the format hint, then disappears on the first keystroke while the value remains invalid. Give help and validation a coherent lifecycle.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Accessible validation · Forms · Focus management
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Persistent help and current errors are associated with their field.
- Submitted errors remain until correction or the next documented validation point.
- Invalid submission provides a focusable summary linked to every invalid field.
Implementation constraints
- Do not announce errors on every keystroke; document validation timing.
Verification to include
- Submit an invalid phone and navigate from summary to field; hear both hint and error.
- Correct one of two invalid fields and resubmit; only the remaining error appears and values persist.
Deliverables
- Contact validation semantics and assistive-technology notes
Rollout and recovery
Apply to contact fields first; retain plain inline errors if enhanced summary behavior loses focus.
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.