# Search 🕵️‍♀️ * [ ] Input field A clear container for a user to start typing in * [ ] Label or placeholder text Identify the purpose of the field is for them to search ⭐️ Use your placeholder text to suggest examples of what to search for * [ ] Quick links, autocomplete and suggestions As the user is typing, offer available links and phrases based on what they have entered so far * [ ] Submit search button A visible link to submit search and view results * [ ] Previous searches Showing what a user has searched before can speed up their experience if they frequently search the same queries * [ ] Appropriate visibility Search should be directly linked to what you are looking for, whether it's searching across the entire platform or in a specific area --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/elements/search.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.