```suggestion
The [wizard](https://clarity.design/documentation/wizard) component guides users through a series of predefined steps. Wizards help users concentrate on the necessary input for each ...
```suggestion
- Design teams **may** use the range input component when it's okay to have a less precise input and the exact value doesn’t matter, allowing users to quickly pick a value from a wid...
```suggestion
- Design teams **should** use appropriate [range input states](https://clarity.design/documentation/range#states) to provide visual feedback and enhance the user experience during in...
```suggestion
- Design teams **must** include clear labels indicating the purpose of the slider to ensure users understand what value they are selecting.
```
```suggestion
A [range input](https://clarity.design/documentation/range) features a slider that allows users to select a value within a defined minimum and maximum range. It’s ideal for scenarios...
```suggestion
- Design teams **must not** stack side panels, as this can make them difficult to dismiss and create confusion for users regarding their navigation.
```
```suggestion
- Design teams **must** ensure users can easily exit the side panel and maintain control over their navigation by providing options to dismiss it, such as buttons for canceling or pr...
```suggestion
- Design teams **must** keep side panels simple. They can include components like links, cards, images, or text, but avoid complex components such as tables or accordions to ensure c...
```suggestion
- Design teams **must** use a side panel when more content or complex interactions are required than a modal can accommodate. Side panels are recommended for tertiary actions or sub-...
```suggestion
- Design teams **must not** use color alone to convey information, as this can make content inaccessible to users with visual impairments or color vision deficiencies. Use additional...
```suggestion
- Design teams **should not** use excessive colors within the same context. As a rule of thumb, aim to limit colors to only those necessary for conveying meaning and maintaining visu...
```suggestion
- If a count or other number is related to the metadata displayed in the label, a badge **must** be used to clearly convey the information.
```
```suggestion
- Design teams **may** use a close icon at the right-most side of a label to dismiss it. Design teams **must not** assign a separate action for a dismissible label, as its primary a...
```suggestion
- Design teams **should** use [clickable labels](https://clarity.design/documentation/label#clicking-labels) to perform actions related to the label, providing a more intuitive user ...