Accessibility

Last updated 24 October 2026

Cellucid should work for everyone who looks at single-cell data. This page says what works, what does not yet, and how to tell us when something is in your way. Cellucid aims to meet WCAG 2.2 at level AA.

What works

  • Keyboard. Panels, fields, buttons and analysis windows are reached with Tab and used with Enter, Space and the arrow keys, with a visible focus ring. The plot is the first Tab stop, and its camera moves with keys. Press ? for every shortcut.
  • Screen readers. Controls are named and announce their state. The plot has a name and a description of its keys, and opening progress and notifications are announced.
  • Contrast and colour. Text meets AA contrast in the light and the dark theme. The first 24 category colours stay distinct for red–green colour blindness, and figure export previews three kinds of colour blindness.
  • Motion. With your system's reduce-motion setting on, transitions stop and camera paths jump to their end.
  • Phones and touch. The interface fits a phone screen, and every control is large enough to tap.

Known limits

  • The plot is a picture. Cells are drawn with WebGL on a canvas, so a screen reader cannot read out single cells. Legends, values and analysis results are text.
  • Selecting cells needs a pointer. Lasso and click selection have no keyboard equivalent yet; no key needs to be held while you point. Without a pointer, select cells with the Python or R package.
  • Many categories. Beyond 24 categories, colours are not chosen for colour blindness, and blue–yellow colour blindness is not covered.
  • WebGL 2 is required. Cellucid runs in current Chrome, Edge, Firefox and Safari; without WebGL 2 it cannot draw.
  • Not audited. Cellucid has not had a formal accessibility audit, so it does not claim conformance.

Tell us

If something stops you from using Cellucid, open an issue on GitHub or write to Kemal Inecik, k.inecik@gmail.com. Say what you were trying to do, and which browser and assistive technology you use. The documentation's accessibility guide has the details, including every keyboard shortcut.