Enforce sufficient touch targets and keyboard nav

Start with a systematic audit: list every widget with an InkWell, GestureDetector, IconButton, or TextButton, then measure its render size with Flutter DevTools Widget Inspector. Prioritize the clear button and microphone button in the search field — these are the most likely offenders. The accessible-touch-target-wrapper should use a transparent overlay with the same onTap callback, keeping the visual size unchanged (use Stack + Positioned or ConstrainedBox). For FocusTraversalGroup, wrap the entire SearchScreen body and use ReadingOrderTraversalPolicy as the default — only override with OrdinalSortKey if reading order diverges from visual order in a specific sub-section.

Document every element that was below 44×44 dp before the fix in a comment next to the wrapper so future developers understand why the wrapper is there.

Widget test using SemanticsController: iterate all nodes with hasTapAction, assert each has size >= Size(44, 44). Widget test: verify FocusTraversalGroup wraps SearchScreen and that FocusTraversalOrder matches expected reading order. Manual test checklist: (1) physical iOS device with VoiceOver swipe navigation — confirm order, (2) physical Android device with Switch Access — confirm scanning order, (3) external Bluetooth keyboard Tab navigation on both platforms. All manual test results must be documented in the PR description.