Skip to main content

WebGL, Accessibility and Troubleshooting

Last updated: August 21, 2026

The Atlas is a WebGL experience, and WebGL fails silently more often than it fails loudly. The usual symptom is a blank or black canvas with no message at all, which tells you nothing about the cause. Working through the possibilities in order identifies it quickly, and three of the four are on your side of the connection.

The checks

  1. Hardware acceleration. If it is disabled, the browser may fall back to software rendering — the scene will load and move badly — or refuse entirely.
  2. WebGL availability. Some managed devices and hardened browser profiles disable it outright.
  3. Extensions. Content blockers and privacy extensions can prevent a canvas from initialising. Try a clean profile.
  4. Memory and viewport. A 3D scene on a very constrained device may load partially or stall. Closing other tabs genuinely helps.

Accessibility, stated honestly

A 3D scene is drawn, not marked up. There is no reliable way for assistive technology to convey a canvas, and no amount of documentation can add one. What exists instead is a full textual equivalent for content: the Codex publishes the same spheres, sectors, systems and planets as readable, linked, navigable pages. That is not a lesser way to use the Universe — for many purposes it is the better one, since it carries relationships the Atlas cannot show.

If nothing works

Use the Codex geography categories. You will lose the sense of arrangement and gain everything else.

Motion and camera movement are inherent to the experience. Readers sensitive to it are better served by the Codex records than by attempting the canvas.

Official source

Canonical source for this subject: the Celestial Atlas. Checked 21 August 2026 — where this guide and the live service disagree, the service is right.

Previous
Locations and Their Canonical Sources
Next
Xdripian Sanctum Guide