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

Survey Task - design improvement for deselecting species choices #6076

Open
lcjohnso opened this issue May 3, 2024 · 3 comments
Open

Survey Task - design improvement for deselecting species choices #6076

lcjohnso opened this issue May 3, 2024 · 3 comments
Labels
design Design and/or UX question Further information is requested

Comments

@lcjohnso
Copy link
Member

lcjohnso commented May 3, 2024

Package

lib-classifier

Problem / Current Behavior

When a volunteer has selected a species via the FEM survey task and wants to deselect the species, currently the user has to click on the species and select the "not this" option from the modal interface.

Example: Left = Species selection has been made; Right = clicking re-opens the same modal and user has to click "not this" -- same as if when the clicked into the species detail originally and reconsidered.
Screenshot 2024-05-03 at 5 14 08 PM Screenshot 2024-05-03 at 5 14 17 PM

Volunteers have highlighted that the PFE UX, where species identifications generate an icon / label that appears at the bottom of the image viewer (see screenshot below), allows the user to deselect a choice without re-entering the species dialog. However, there's pretty strong consensus that this PFE UX is a little wonky and not desirable to replicate.

Example: PFE subject image viewer with species identification tag for single selected species in lower left corner.
Screenshot 2024-05-03 at 5 48 13 PM

Potential Solutions

Initial conversations (Cliff, Delilah, Sam, and Laura) generated a few ideas, but open to others (this list is not comprehensive!).

  1. Simple Click (less good option): clicking on a selected species will deselect the choice.
    • Pro: simple is good?
    • Con: volunteer may want to edit rather than delete their selection (i.e., edit answer to follow-on subquestions), but this solution only allows for all-in removal of annotation.
  2. Add "X" Tooltip: on hover (or similar?), reveal an "X" icon connected to the choice button that would allow for deselection of species. Alternately, clicking on the species reopens the dialog (as is currently done).
    • Pro: keeps users from having to click into dialog
    • Con: "X" button would require hover to reveal (?), might be difficult to use (tooltip would be small when many choices)
  3. Change Button Text in Dialog When Already Selected: keep same behavior, but in the case that the dialog is opened for an already-selected species, replace the "not this" / "identify" button text to a more useful alternative (e.g., "Deselect" / "Keep Selected", but better :-) )
    • Pro: minimal change
    • Con: still requires opening dialog
@lcjohnso lcjohnso added question Further information is requested design Design and/or UX labels May 3, 2024
@eatyourgreens
Copy link
Contributor

eatyourgreens commented May 4, 2024

PFE supports backspace to deselect a selection. I think that shortcut was ported across. Use the arrow keys to navigate the choices menu, then backspace to deselect.

https://github.com/zooniverse/Panoptes-Front-End/blob/0f3b2dbf088b5d7afbd078b2156618d4aa96ba81/app/classifier/tasks/survey/chooser/Choices.jsx#L77-L80

EDIT: FEM supports backspace and delete to remove a selected menu item:

case 'Backspace':
case 'Delete': {
event.preventDefault()
event.stopPropagation()
handleDelete(choiceId)
return false
}

@eatyourgreens
Copy link
Contributor

eatyourgreens commented May 4, 2024

Hover interactions aren’t available on touch devices, and fail WCAG success criterion 2.1.1, which is a level A requirement, so you’d still need a solution for touch and keyboard in that case.

@eatyourgreens
Copy link
Contributor

eatyourgreens commented May 4, 2024

Zooniverse has at least one blind volunteer, who uses NVDA to participate in audio survey projects, so any design solution should include screen readers, as well as keyboard interaction. Screen readers, of course, don't have hover interactions.

The new survey task uses a checkbox menu. Here, 'Bat' is selected and its checkbox is checked. In that case, as a blind user I would expect Enter or Space to toggle the checkbox off, but it actually opens the Choice popup (and unexpectedly changes the reading focus?) Adding a haspopup relationship, to indicate that the menu item is linked to a Choice popup, might help fix that. At the moment, Backspace or Delete will uncheck the checkbox, but that's not the usual shortcut for a checkbox.

MDN lists the keyboard interactions for a checkbox menu item.

A survey task menu in Firefox, with the accessibility inspector open to show that the menu is a list of checkbox menu items. The 'Bat' checkbox is selected, and its state is 'checked'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design Design and/or UX question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants