> For the complete documentation index, see [llms.txt](https://wiki.simpler.grants.gov/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.simpler.grants.gov/design-and-research/brand-guidelines/colors.md).

# Colors

Color plays a significant role in our brand. The following values represent our core palette. These are used most often in the system and should be relied on when the color palette must be limited. Each of our colors is named for ideas that represent trust and accessibility.

Patina Green, Forest Green, and Sky Blue should be used most frequently as the primary brand colors, with the remaining values being used as support.

<figure><img src="/files/VLcd5vp6c4XmNoFlKpoq" alt=""><figcaption></figcaption></figure>

## Color Families

The Grants color system is based on the design token system in USWDS. Each color family has 7-8 grades.

<figure><img src="/files/ATpIunn8kwHUT8EbBGjs" alt=""><figcaption></figcaption></figure>

## Color & Accessibility

Pairing colors together can be complex. Always consider the application, information, and audience when selecting values. Higher contrast combinations make information clearer, while lower contrast combinations can be helpful for graphic elements.

Color contrast is crucial to legibility and accessibility in type. Always be sure there is enough contrast between the type and background. In most situations, type should be used in Gray or White, with color being used to create emphasis.

<figure><img src="/files/HkfqulwKkuGF6VXCIesN" alt=""><figcaption></figcaption></figure>

## Additional don’ts

Do not diminish the value of color in the brand. Avoid the following uses.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Do not use unapproved colors.</td><td><a href="/files/WB2Md3HEGi94jNxTHy1Q">/files/WB2Md3HEGi94jNxTHy1Q</a></td></tr><tr><td>Do not use gradients.</td><td><a href="/files/EcfAb35VBvrSZ704UBRG">/files/EcfAb35VBvrSZ704UBRG</a></td></tr><tr><td>Do not use low-contrast combinations.</td><td><a href="/files/vDe2zshNPNAIXQ9OXLTD">/files/vDe2zshNPNAIXQ9OXLTD</a></td></tr><tr><td>Do not use only accent color combinations.</td><td><a href="/files/Uhv9VerR3u9a54yzHdO2">/files/Uhv9VerR3u9a54yzHdO2</a></td></tr></tbody></table>


---

# 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://wiki.simpler.grants.gov/design-and-research/brand-guidelines/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.
