> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/identity-verification/ux-and-design.md).

# UX & Design

Great experiences are built on three pillars: a product that looks like yours, works for everyone, and speaks your customers' language. This section explains how {{Product}} supports each of these.

***

### What's in this section

* Brand Customization - Make 1Kosmos match your brand, from logo and colors to text and content.
* Accessibility -  How 1Kosmos is built to conform to WCAG 2.2 Level AA so your experience is usable by everyone.
* Localization -  Deliver 1Kosmos in your customers' preferred language, region, and formats.

### Our design principles

* **Consistency by default, flexibility where it matters.** Sensible defaults out of the box, with the controls to tailor what your brand needs.
* **Accessible from the ground up.** Accessibility is a baseline, not an add-on.
* **Inclusive at global scale.** Built for multiple languages, locales, and writing directions.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.1kosmos.com/identity-verification/ux-and-design.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
