> 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/elements/checkbox.md).

# Checkbox ☑️

* [ ] Label

  Text associated with the checkbox

  ⭐️ Label should indicate that if checkbox is clicked, the label
* [ ] Default selection

  Whether the checkbox is selected or not

  ⭐️ An active checkbox by default depends on the purpose of the checkbox - it should come down to how much this conveniences the user
* [ ] Style

  Make sure checkbox is unique and stands out from other input options
* [ ] Clickability

  Consider what is clickable to make the checkbox active (text label, container)

  ⭐️ Clicking a checkbox shouldn't activate another element to appear, change or react - it confirms a change, it doesn't trigger it
* [ ] States

  Radio can be default, active and disabled (see examples below)


---

# 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/elements/checkbox.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.