Skip to main content

Accessibility and Support

Last updated: August 21, 2026

Games in this Universe are published across three verticals and a catalogue, which means a support question has to find the right owner before it can be answered. The rule is simple: a problem belongs to the surface where the thing runs. A browser title that will not start is an Arcade matter. A prototype that misbehaves belongs to Xdripia Games. Anything about colonies, fleets or your own world state is Terminus. A boxed game with a missing component is a commerce matter and belongs to the Emporium.

Before reporting

Work through the browser checks first — hardware acceleration, content blockers, a second browser, input focus, foreground tab. They resolve most reports, and they take a minute. If a clean browser profile works, the finding is about your configuration and is worth knowing regardless.

What to include if you do report

The exact title and route, what you did, what happened, what you expected, your browser and platform, and whether a clean profile reproduces it. A report with those six things can be acted on; one without them starts a conversation instead.

Accessibility, stated plainly

Canvas-rendered games are drawn rather than marked up, which limits what assistive technology can do. Where a title documents input alternatives on its own page, those are what exist. Physical games have their own accessibility characteristics — component size, colour dependence, reading load — described with the game.

Documentation cannot add accessibility options to a game or fix a defect in one. Its useful role is directing a report to the surface that can.

Official source

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

Previous
Game Manuals and Source Map
Next
Tales of Xdripia: Terminus Guide