Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spike: Grouped Radio buttons #663

Open
3 tasks
htmlandbacon opened this issue Dec 10, 2024 · 0 comments
Open
3 tasks

Spike: Grouped Radio buttons #663

htmlandbacon opened this issue Dec 10, 2024 · 0 comments
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.

Comments

@htmlandbacon
Copy link
Member

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

  • Example html
  • Example component
  • Reviewed and decided next steps

Outcomes

We should have a clear idea of what to do with this suggestion.

Anything else

@htmlandbacon htmlandbacon added 🔗 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. accessibility labels Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Projects
None yet
Development

No branches or pull requests

1 participant