Make inspection inputs usable with large text
A technician increases system text size. Pass/Fail controls overlap equipment names, and the last input disappears beneath the keyboard.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Mobile accessibility · Responsive layout · Forms
Estimated field mix
- Accessibility60%
- Mobile40%
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 Vale facilities team services equipment in basements with poor reception. Technicians receive assigned work orders, record checks, and attach synthetic equipment photos. The practice app uses an on-device database and a stub sync service; background location tracking is excluded.
Setup prerequisites
- Synthetic work orders and a revisioned sync contract
- An emulator with controllable connectivity and app lifecycle
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- The agreed largest supported text setting keeps labels and choices readable.
- Focused fields can scroll above the keyboard without hiding their error messages.
- Each checklist choice has an accessible name that includes its inspection item.
Implementation constraints
- Do not disable system text scaling to make the layout fit.
Verification to include
- Complete a six-item inspection at large text size with the on-screen keyboard.
- Use a long equipment name and an invalid reading; controls and errors remain reachable through assistive navigation.
Deliverables
- Adaptive inspection layout and emulator accessibility walkthrough
Rollout and recovery
Review on the smallest supported test device; revert affected layout components if input becomes unreachable.
Value of the work
For the engineer: Practice durable local state, mobile lifecycle recovery, and conflict resolution in realistic offline workflows.
For the team: Review whether an engineer can protect field work through crashes, interrupted uploads, and reassignment.
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.