Decision:
We should remove the visible Search button and rely on autocomplete + Enter to trigger the search, aligning this flow with FFTS.
Rationale:
Consistency Across Products – Families are already exposed to the FFTS pattern where autocomplete and Enter confirm the search. Maintaining the same behavior here reduces cognitive load and builds familiarity.
Streamlined UI – The button introduces redundancy. When autocomplete handles results dynamically and Enter triggers submission, the button doesn’t add functional value. Removing it simplifies the interface and keeps the focus on the input field.
Modern Search Standards – Most search-driven products (Google, Amazon, etc.) don’t require an explicit search button anymore. Parents who use digital platforms regularly are accustomed to this interaction pattern.
Accessibility Still Covered – Screen readers and keyboard users can still submit the search by pressing Enter, which is a standard input behavior. We’ll confirm with QA that the input field is properly labeled and accessible.