Ecosyste.ms: Timeline
Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** use checkboxes to allow users to select one or more options from a list of choices. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion The [checkbox](https://clarity.design/documentation/checkbox) control enables users to select one or more options from a list of multiple choices, providing a straightforward way to ...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must not** use unrecognizable system error messages, such as "code 500 error," as error messages. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - For password fields that display visible password strength criteria. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - When users return to an error field and successfully correct the input. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Inputs that require validation for sensitive field value lengths, such as tweets. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams must not validate the form while the user is typing, as this can lead to frustration. Exceptions to this rule are noted below. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** ensure that error messages are clear and straightforward. The content should provide specific guidance on how to fix the error, helping users understand the n...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** follow the [error message styling](https://clarity.design/documentation/forms#error-message-styling) guidelines to ensure that error messages are clearly comm...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **should** choose a vertical layout for narrow or mobile screens. This format ensures better readability and accessibility, allowing users to navigate through the cont...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams should use a horizontal layout for longer forms. This approach allows for better organization of information, making it easier for users to navigate and complete the f...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **should** choose this layout when highlighting labels for users. A single-column format ensures that all labels are prominently displayed and easily readable. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **should** choose a horizontal layout when vertical space is limited, as this approach allows users to view all options at once, reducing scrolling and improving acces...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **should** use [radio buttons](https://clarity.design/documentation/radio), [checkboxes](https://clarity.design/documentation/checkbox), or [select boxes](https://clar...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **should** logically group controls in forms, especially when there are more than six inputs. For example, street, city, zip, county, and country can be grouped as an ...