# Navigation 🧭 * [ ] Logo Reinforce your brand at the top level on every page * [ ] Structure Ensure your most important links are available at the high level, and links that are a level deeper are relevant and impactful to more niche users ⭐️ Consider only two levels of hierarchy to reduce complexity ⭐️ Ensure that each level of navigation has a different visual design to differentiate the levels clearer * [ ] Consistent location Usually located at the top of the page as it is the most accessible, but it should always appear at the same location on every page * [ ] Visual contrast to rest of page Make it clear for a user to easily see where they can visit other pages ⭐️ This can be made more noticeable with a visual change after scrolling on a page, such as a different background colour or shadow * [ ] Call to action/s The primary action/s you want users to perform * [ ] Mobile responsiveness Consider a design for the mobile version of the menu as the screen size difference is enormous and will definitely affect your layout * [ ] Icons next to link A visual cue can help break up lines of text * [ ] Breadcrumbs Showing the current level and hierarchy of sections above the current page --- # 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/navigation.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.