Accessibility, Privacy, and Security#
These pages make explicit what Cellucid does and does not do in two areas that often get skipped in visualization tooling:
Accessibility: how to produce figures and workflows that work for diverse readers (color vision deficiency, low vision, keyboard-only use), plus current limitations of a WebGL canvas-based UI.
Privacy model: what stays local, what can touch the network depending on your loading workflow, what is stored in the browser, and what exported artifacts can contain.
If you are in a regulated environment (clinical, IRB-controlled, corporate IP), the key idea is:
Cellucid is “just a web app”, but your workflow choices determine what leaves your machine and what gets saved into shareable artifacts.
Fast path (pick your situation)#
You need to… |
Do this first (safe default) |
Then read |
|---|---|---|
Use sensitive/clinical data without uploading it |
Use local prepared exports + avoid Community Annotation + review figure metadata before sharing |
|
Share sessions safely with a team |
Treat |
|
Make figures readable for colorblind audiences |
Use perceptually-uniform colormaps; check the export preview’s colorblind simulation |
Recommended reading order#
Privacy model (know what leaves your machine and what gets saved)
Accessibility (make what you publish readable to more people)
Related (often relevant):
Metadata and provenance (export metadata can include dataset paths/URLs)
Security, privacy, and trust (session bundle privacy/trust)
System requirements (managed environments, blocked storage, iframe restrictions)
Pages in this section#
Color/contrast guidance, keyboard shortcuts, motion sensitivity tips, and practical limits of a WebGL viewer.
What stays local vs hits the network, what is stored in the browser, and what exported artifacts can contain.