# Better radio buttons and checkboxes

**URL:** <https://forum.getodk.org/t/better-radio-buttons-and-checkboxes/27775>\
**Category:** Ideas\
**Created:** [June 27, 2020, 3:24pm UTC](https://forum.getodk.org/t/better-radio-buttons-and-checkboxes/27775 "2020-06-27T15:24:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dmenne](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/dmenne/32/11796_2.png) [@dmenne](https://forum.getodk.org/u/dmenne)\
**Post date:** [June 27, 2020, 3:24pm UTC](https://forum.getodk.org/t/better-radio-buttons-and-checkboxes/27775/1 "2020-06-27T15:24:17Z")

</div>

Radio and checkboxes in Browsers are a strange relict of the last millenium. In case you have tried to change their look on normal web pages, you know the dirty tricks required to get this to work - shifting the boxes off-screen is the funniest part. I have tried this for formio, an Angular based framework [here](https://github.com/dmenne/custom-radio).  
 ![68747470733a2f2f692e6962622e636f2f7634316872624e2f637573742e706e67](https://getodk.b-cdn.net/uploads/default/original/2X/e/eb7a2fc277123ebe5871b4ac38a130976cd88099.png)

On mobile devices, checkboxes are much too small and when selected. RedCap - data entry for medical studies - has a solution that works nicely

 ![Create Mobile-Friendly Survey Buttons with this New REDCap Feature - ITHS-000040](https://getodk.b-cdn.net/uploads/default/original/2X/5/59bfc4a559e61aa35d6c3f20433655d8c6224f74.jpeg).  
I know from personal experience that nobody who ever used these switches back to standard buttons.

---

<div class="post-metadata">

**Author:** ![dmenne](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/dmenne/32/11796_2.png) [@dmenne](https://forum.getodk.org/u/dmenne)\
**Post date:** [September 24, 2020, 4:39pm UTC](https://forum.getodk.org/t/better-radio-buttons-and-checkboxes/27775/2 "2020-09-24T16:39:15Z")

</div>

I know that ODK follows Material design rules, but:

- The example shown as used by RedCap also follows material design
- See [Fits's Law:](https://lawsofux.com/fittss-law.html)The time to acquire a target is a function of the distance to and size of the target ([Wikipedia](https://en.wikipedia.org/wiki/Fitts%27s_law))

---

<div class="post-metadata">

**Author:** ![LN](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/ln/32/1605_2.png) [@LN](https://forum.getodk.org/u/LN)\
**Post date:** [September 27, 2020, 9:38pm UTC](https://forum.getodk.org/t/better-radio-buttons-and-checkboxes/27775/3 "2020-09-27T21:38:23Z")

</div>

> [@dmenne](#):
>
> See [Fits's Law](https://lawsofux.com/fittss-law.html)

List items in Android are selectable by tapping anywhere on the element. That is, you can tap on the radio button/check box but also on the text or in the margin above or next to the element. We've also extended that tap area all the way to the horizontal edges of the screen instead of leaving the usual margin because users often answer questions while holding their device in one hand. We've also recently tuned the vertical spacing between select elements based on user observation and feedback. Is your concern that the larger tap area is not discoverable so users may try to keep aiming for the radio button or check box?

---

<div class="post-metadata">

**Author:** ![dmenne](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/dmenne/32/11796_2.png) [@dmenne](https://forum.getodk.org/u/dmenne)\
**Post date:** [September 28, 2020, 6:25am UTC](https://forum.getodk.org/t/better-radio-buttons-and-checkboxes/27775/4 "2020-09-28T06:25:15Z")

</div>

> [@LN](#):
>
> That is, you can tap on the radio button/check box but also on the text or in the margin above or next to the element.

It does not help to know it theoretically, user want intuitive behaviour. And it is intuitive to try to hit the square. I know that everything can be touched, and nevertheless try to hit the square, because there I get the immediate feedback.

I have asked users about your orange-border solution, but they were not happy with it. I do not know exactly why, but to me the border it looks like the active (not the selected) button in Windows.

> [@LN](#):
>
> Is your concern that the larger tap area is not discoverable so users may try to keep aiming for the radio button or check box?

Partly. We have made some studies when using RedCap as an eCRF (electronic case report form), where you can select between the two. The colored buttons were strongly preferred, even by young trained users, but the more when patients filled the form. Being able to hit correctly was not the primary argument (even if Fit's Law would suggest it), the main advantage is that even out-of-focus it is easy to see that an item has been checked.
