# Tabs 🗂 * [ ] Label Name of tab ⭐️ Label should be logical enough for the user to predict what's in the tab ⭐️ Keep it short and sweet, 1-3 words * [ ] Pane Where the content for the active tab is displayed * [ ] Usage Tabs should be used as a sibling view to filter parent information * [ ] Style How the active tab and inactive tabs differentiate visually * [ ] Structure Parallel with each other, and spaced closely enough to appear connected ⭐️ Consider arrangement of tabs to be ordered by popularity or familiarity ⭐️ Each tab should behave the same in interaction * [ ] States Tabs can be active and inactive --- # 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/tabs.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.