Accessibility
WCAG 2.2 AA is the target.
For this site and for the console itself. This page says what is checked, what is known to fall short, and where to send what you find.
What is checked
Two passes, one automated and one by hand.
An accessibility pass runs statically in CI on the console's markup. Contrast and keyboard traps are checked in the desktop window after each merge.
- Contrast. Every text color against its ground, in both themes, at AA.
- Keyboard. Every control reachable and operable by keyboard; no traps. The map's boxes, the lens keys and the Desk verbs included.
- Reduced motion. Honored on this site: it stops animating when the device asks, and the mark's animation stands still.
- Structure. One h1 per page, landmarks, a skip link, visible focus, text that reflows to 320 pixels without a horizontal scroll.
- Theme. Dark by default, light on request, following the device until the toggle is pressed.
Known gaps
Two things fall short today.
Listed so that nobody discovers them the hard way. Both are being worked on and will be removed from this page when they are closed.
- The map's diagrams. The map and the pipelines are SVG with titles, but not every box carries a full text alternative. A screen reader hears the pipeline's name and the stage names; it does not yet hear every item's state in every box.
- Screen-reader labels on the map. Labels for the map's boxes, particles and lens states are being completed. The same information is available in the panels each box opens, which are labeled.
How to report
Tell us what you hit.
Email support@soloinc.ai with "accessibility" in the subject. Say which page or screen, which assistive technology and browser, and what you expected. A confirmed barrier is treated as a defect, not a request, and goes into the next release.
The version shown under Settings › Licence, if it is the console. The URL, if it is this site. Whether the theme was light or dark, and whether reduced motion was on.