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

Identify potential changes to conditional reveals for research #1992

Closed
2 tasks
36degrees opened this issue Oct 16, 2020 · 2 comments
Closed
2 tasks

Identify potential changes to conditional reveals for research #1992

36degrees opened this issue Oct 16, 2020 · 2 comments

Comments

@36degrees
Copy link
Contributor

36degrees commented Oct 16, 2020

What

Identify what potential changes to the conditional reveals on radios and checkboxes we might want to prototype and test in user research.

Why

There are a few known issues with conditional reveals, as described in the epic. There are no simple fixes, so we're likely to want to test and potential changes in user research.

Done when…

  • Desk research for which assistive tech does and does not support aria-expanded on conditional reveals
  • Chosen which use cases are the most appropriate to test in the research prototype. Ed's examples on slides 53 onwards should help.
@36degrees 36degrees added this to Upcoming sprints in Design System Sprint Board via automation Oct 16, 2020
@trang-erskine trang-erskine moved this from Upcoming sprints to Sprint Backlog in Design System Sprint Board Oct 21, 2020
@kellylee-gds kellylee-gds moved this from Sprint Backlog to In progress in Design System Sprint Board Oct 28, 2020
@CharlotteDowns
Copy link
Contributor

Upcoming user research

We are going to test the existing components that use conditional reveal, (checkboxes and radios), in order to establish what works well and what works less well.

Once we have that understanding, we will be in a better place to prioritise design and development changes to the components.

@kellylee-gds kellylee-gds moved this from In progress to Done in Design System Sprint Board Oct 30, 2020
@CharlotteDowns
Copy link
Contributor

CharlotteDowns commented Oct 30, 2020

We have decided to take the component 'as-is' to user research in November 2020. The two versions of the component we are going to test are:

  1. a contact details example (as seen in the Design System)
  2. a fieldset example where we will use either a date or address input.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants