> For the complete documentation index, see [llms.txt](https://able.bucca.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://able.bucca.com/core/components/form/checkbox.md).

# Checkbox

Component: A locked height form component for the collection of one or more on/off or yes/no input values from a set of options. Inner element spacing is used for dynamic resizing along with a background surface.

[Styleguide Link](https://zpl.io/aNYpq7n)

* Parent: Form (Container)
* Child: [Checkbox - Ctrl](/core/overview/checkbox.md), [Label](/core/overview/label.md)

## Properties

### Label

The component can be presented with a label to give context to the checkbox control. This label can be positioned either left align or right.

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

### Style

The styling of the checkbox can be altered to present a different appearance to the checkbox. For example, a To-Do list being presented with a fancier check than the typical checkbox, but having the same underlying functionality.

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

**Note:** Each of the nested elements and primitives of this form component have properties that can be adjusted to customize the component.


---

# 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://able.bucca.com/core/components/form/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.