Spike: Grouped Radio buttons #663
Labels
accessibility
🔗 component
Reusable parts of the user interface that have been made to support a variety of applications.
⏱ hours
A well understood issue which we expect to take less than a day to resolve.
What
We've seen a couple of examples of large lists of radios being split up by headers (within the radio) we should extract this as a component to test.
Most recently 'Determine a customer's habitual residence' sent an example.
Why
In agent interfaces with longer lists it is better to have clear sections to help people navigate to what they need to select.
The example given had content issues, but the example represented to the accessibility team seemed to resolve this issue.
The other assumption is this might be better as guided questions.
Done when
Outcomes
We should have a clear idea of what to do with this suggestion.
Anything else
The text was updated successfully, but these errors were encountered: