> For the complete documentation index, see [llms.txt](https://docs.klai.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/topics/colors.md). # Colors 🎨 Colors represent your story in a product's interface. They inform the mind emotionally and intellectually on what's happening, and what decision to make next. In short, color is all about influence. The color of a button influences how a user reacts to its intent. The color of a brand influences a user's choice to commit. The contrast, depth and saturation of color all influence how an element is communicated. A good experience lets color effectively influence. * [ ] Color psychology How color can impact how people think, feel, and act ⭐️ Utilise the psychology e.g. destructive button is red, approved message is green ⭐️ Research the cultural differences in color, dependent on who your audience is ⭐️ Don't add colors just for appearance, they will always communicate something to the user * [ ] Branding values How your brand colors incorporate into the experience ⭐️ Primary, secondary and tertiary brand colors can translate the hierarchy of actions ⭐️ Color can represent your brand's style: traditional or modern, fancy or grungy * [ ] UI states Showing success, error and warning elements through color ⭐️ Don't rely on color only to convey state, combine it with information e.g. explain there is an error when an element's color changes to red * [ ] Contrast How colors combine in a purposefully different way ⭐️ Change your design to grayscale to test contrast from hue and value intensity * [ ] Combinations How colors work together as a palette --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/topics/colors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.