Check assistive-technology behavior for delivery errors
Eligibility failures appear visually below the form but keyboard users receive no useful indication.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Accessibility · Exploratory testing
Estimated field mix
- Accessibility50%
- Quality engineering50%
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
A fictional retailer is changing delivery options. Its regression suite is large, but no one can explain whether inventory, totals, or recovery behavior is covered.
Setup prerequisites
- Build a minimal local checkout fixture with synthetic prices, inventory, and a mock delivery provider.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Associate errors with the relevant inputs.
- Move or announce focus consistently after failed submission.
- Preserve entered values for correction.
Implementation constraints
- Use semantic HTML and owned accessible components.
Verification to include
- Complete the flow using a keyboard.
- Trigger multiple errors and verify readable order and no focus trap.
Deliverables
- Accessibility acceptance notes.
Rollout and recovery
Include these checks in the release smoke path; revert inaccessible validation changes.
Value of the work
For the engineer: Practice risk analysis, exploratory testing, and evidence-based release decisions.
For the team: Provide a reviewable release assessment tied to customer-impacting invariants.
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.