> 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/dark-mode.md).

# Dark mode 🌑

For a designer, dark mode is larger than just flicking a switch and inverting some colors. The accessibility options completely change and your shades for structure and layout need to be re-evaluated - just for starters.

* [ ] Adaptable color palette

  What your product looks like visually with a dark setting

  ⭐️ A grey for your darkest color is more flexible in shadows and contrast than black

  ⭐️ The lower the saturation, the more accessible a color will be

  ⭐️ Ensure dark palette for backgrounds must allow white to be accessible
* [ ] Brand integrity

  Maintain your visual tone and style

  ⭐️ Invert monotone visuals

  ⭐️ Incorporate colours from your brand that are also present in light mode
* [ ] Elevation

  A way to structure elements to establish heirarchy

  ⭐️ Use lightness over shadows to give focus to certain containers or elements
* [ ] Switch to light mode

  Some products may be just one or the other, but if you offer both then allow the user to make a seamless switch between the two.


---

# 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/dark-mode.md?ask=<question>&goal=<endgoal>
```

`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.
