SpringSaLaD viewer: default site colors are confusable under color blindness (#1605 audit X1)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 64/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- java
- Domain
- accessibility
Research direction
Start from org.vcell.util.springsalad.Colors.COLORARRAY and the two default-assignment sites in SpeciesContextSpec (around lines 855 and 874), keeping existing saved model colors untouched. The palette check to satisfy is ColorAccessibilityTest (used by the #1605 remediation); extend or run it to confirm the new default sequence measures ΔE′ ≥ 10 under protan, deutan and tritan simulation. Done means new sites get the revised sequence, the test passes, and a deuteranopia-simulated screenshot of SpringSaladViewerCanvas shows each site type distinguishably; note the issue leaves options 1-3 undecided, so confirm the chosen option with maintainers first.
Written by the indexing model from the issue text.
Description
Follow-up from the #1605 color audit, row X1 (docs/accessibility/color-audit.md).
Finding. In the SpringSaLaD particle viewer, site type is shown only by sphere color. The default colors are assigned in org.vcell.util.springsalad.Colors.COLORARRAY order (RED, BLUE, LIME, ORANGE, …; see SpeciesContextSpec around lines 855 and 874). Simulated for deuteranopia, the first 8 defaults have a worst-pair color difference of ΔE′ 2.2 (CAM02-UCS), so two of them look the same. Red/lime is the red/green pairing UConn's color guidance says to avoid.
Constraint. Site colors are model data. They are saved with the model and written by name into SpringSaLaD input files, so this is not a free palette swap. The viewer's species legend with show/hide toggles (SpringSaladSpeciesLegend) is an existing non-color way to find a site type.
Options, to decide.
- Change the default order for new sites only, to a sequence that measures ΔE′ ≥ 10 under protan, deutan and tritan simulation. Existing models keep their colors.
- Label spheres on hover or selection in
SpringSaladViewerCanvas. - Vary sprite size or outline per site type.
Acceptance.
- The default sequence for new sites passes the palette check used by the #1605 remediation (
ColorAccessibilityTest). - A reviewer can identify each site type in a deuteranopia-simulated screenshot without toggling the legend.
Related: #2072 (anchor site defaults to near-invisible DARK_GRAY). Part of #1603.
- Dominant language
- Java
- Stars
- 140
- Forks
- 35
- Avg merge
- 17h 39m
- Merged PRs (30d)
- 19
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from virtualcell/vcell
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
virtualcell/vcell#2193 · 1 comment ·
Maintainers usually reply within 1 day
-
Accessibility Requirement Java-based User Interface
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
virtualcell/vcell#2138 ·
Maintainers usually reply within 1 day
-
Accessibility Requirement Java-based
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
virtualcell/vcell#2137 ·
Maintainers usually reply within 1 day
-
Accessibility Requirement User Interface
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
virtualcell/vcell#2135 ·
Maintainers usually reply within 1 day
-
Accessibility Requirement Java-based User Interface
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
virtualcell/vcell#2134 ·
Maintainers usually reply within 1 day
All issues in virtualcell/vcell
Similar issues
-
Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
MCP add-on: JSON responses with non-ASCII characters are truncated (wrong Content-Length)Possibly taken @dhanushbs10 claimed this today. Openadd-on bug in:mcp
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Map.Coordinate does not implement proper equalsPossibly taken A pull request linked to this issue is open or already merged. Openvaadin-map
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
vaadin/flow-components#10586 ·
Maintainers usually reply within 1 day
-
WeReadInstaller writes the launcher database on the main thread at handover (Activity pause timeout)Openbug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
wpilibsuite/SystemcoreTesting#446 ·
Maintainers usually reply within 1 day