> For the complete documentation index, see [llms.txt](https://docs.qatts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qatts.com/studio/ui-elements/radio_button.md).

# radio\_button

A radio button is a graphical control element that is used to select one option from a set of choices.

Radio buttons are usually used in conjunction with textboxes, dropdowns, and other input controls

These can be selected or deselected by clicking it. The user typically selects one option from among two or more options.

Radio buttons are often used in forms to provide the user with mutually exclusive choices.

## Automation

When automating the radio buttons, Sometimes clicking on the selected radio button become de-selected. To handle this kind of scenarios QATTS handles the logical behavior from the user inputs.

QATTS simply checks the radio button status, If it is not in selected state. Performs click operation on web element. Refer to library for different ways of clicking. [Properties Library](/studio/ui-elements/properties-library.md)

My web application was maintaining the state of the radio button in different attribute. Yes, we got it handled as well.

| Property Name          | Property Value  |
| ---------------------- | --------------- |
| attName.selected       | YOUR\_ATTRIBUTE |
| attName.selected.value | DEFINED\_VALUE  |

When configured the above and at the time of execution

Step1 : QATTS extracts your attribute value (YOUR\_ATTRIBUTE ) and compares with the  DEFINED\_VALUE.

Step2 : If both doesn't match. it will click on the web element. Refer to library for different ways of clicking. [Properties Library](/studio/ui-elements/properties-library.md)


---

# 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.qatts.com/studio/ui-elements/radio_button.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.