Altinn / Altinn/app-frontend-react

Ability to (optionally) unselect selected radiobutton / likert answer (On-Hold)

Open
#1,141 2 comments 1 reaction 0 assignees View on GitHub
area/designsystem org/udir ux
Dominant language
TypeScript
Stars
21
Forks
33
Avg merge
6d 23h
Merged PRs (30d)
3

Description

Ability to optionally make radiobuttons unselectable.

**This issue is on hold, Udir has deceided to run 2023 survey without this feature**

After testing Altinn Studio as a survey engine with the UDIR PBU project against 7500 students (grade 5-vg3) in April and May 2023. It is quite clear that many users are answering the survey with IPad's or other touch screen devices. Since they are using fingers to answer and scroll, they sometimes select and answer that was not intended.

It is a political decision to change the format of the questions, this includes adding an option for "do not wish to answer". This enforces the UDIR PBU team to try to solve this the same way as the previous version of the survey was implemented. Making it possible to unselect radiobuttons in certain senarios. We see that some other survey engines support this as well.

Our suggestion is not to change the default behavior, but add a flag that can enable a radio button set og likert to support unselecting a selected radiobutton.

### Ability to unselect selected radiobutton / checbox answer
_Answer from 31 May 2022_

Angående radioknapper og avkrysningsbokser - det er viktig at disse brukes til korrekte formål, og at en ikke mikser med standard oppførsel her. 😊 
(Altså _ikke_ lurt å trikse til avkrysningsbokser der kun èn kan markeres, slik jeg tror det var snakk om i møtet i dag?)
- Radioknapper brukes når brukeren **_må velge ett alternativ_**. En bør vurdere å ha med et valg for "Jeg vet ikke", "Ingen av disse" eller "Ønsker ikke å besvare". Kanskje sistnevnte i deres tilfelle?
- Avkrysningsbokser brukes når brukere kan velge et hvilket som helst antall av valgene (null, ett eller mange.)

Radioknapper kan som standard oppførsel **_ikke avmarkeres_**, da hensikten med dem er at det **_skal_** være et markert valg. Når det gjelder om de bør ha et markert alternativ som utgangspunkt, ser jeg det er delte meninger om dette. En artikkel fra [Nielsen Norman Group](https://www.nngroup.com/articles/radio-buttons-default-selection/) mener at det i de fleste tilfeller bør være et default valgt alternativ, mens studier fra [Gov UK](https://design-system.service.gov.uk/components/radios/) tilsier at en ikke bør sette et default alternativ da dette gjør det mer sannsynlig at brukere overser et spørsmål og derav angir feil svar.

_Originally posted by @mrosvik in https://github.com/Altinn/app-frontend-react/issues/181#issuecomment-1141970162_

Contributor guide

Open the contributing guide

Research direction

The issue names no files, components, or tests; first confirm whether the on-hold request is active, then locate the radio-button and Likert implementations and their existing tests. Read how selection and validation are currently handled. Done means an agreed optional behavior for these controls while preserving standard default behavior when the option is not enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.