> For the complete documentation index, see [llms.txt](https://themedocs.zenit.design/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://themedocs.zenit.design/en/faq/accessibility/colors.md).

# Colors

## Color Contrast and Accessibility

Sufficient color contrast is essential for the readability and accessibility of your store. Text, controls, and input fields, in particular, must stand out clearly from the background so that people with visual impairments can easily recognize and use them.

### Here's what you should pay attention to:

* **Text and background:** The contrast should be at least **4.5:1** (for body text) or **3:1** (for larger fonts and UI elements).
* Input fields and buttons: They should stand out clearly from the background and be easily recognizable – ideally with a visible border or a distinct fill color.
* Focus and hover effects: Ensure that interactive elements such as buttons or form entries are clearly highlighted when focused or hovered.

\
**Tip:** You can test the color contrast with online tools such as the [WebAIM Contrast Checker](https://webaim.org/resources/contrastchecker/) or browser plugins for accessibility testing and adjust it if necessary. This ensures that your store is easily accessible for all users.


---

# 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://themedocs.zenit.design/en/faq/accessibility/colors.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.