Draft — pending legal review. This describes the state of the product today rather than a conformance claim. Where something has not been tested, it says so.

Accessibility

We aim for SignalOS to meet WCAG 2.1 Level AA. We have not been audited against it, so this page separates what is checked automatically from what is not yet checked at all.

What is checked, on every build

Colour contrast. Every text colour is computed against every surface it can appear on and must clear the WCAG 2.1 AA ratio of 4.5:1 for normal text. This runs in continuous integration and fails the build, in both light and dark themes.
It checks both places the palette is defined — the design tokens used by components and the CSS variables that paint the page — because checking only one of them can pass while the other ships.

Built, but not independently verified

Reduced motion: animation is suppressed for anyone whose system asks for it.
Visible keyboard focus on interactive elements.
Semantic headings and landmarks, and text alternatives on meaningful images.

What we have not tested

Screen-reader output, on any screen reader.
Full keyboard operation of every flow, including dialogs and data tables.
Focus order and focus return after a dialog closes.
How form errors are announced.
Any third-party or embedded content we render.

Until those are tested we cannot honestly claim conformance, only intent — so that is all this page claims.

Telling us about a barrier

If something here stops you working, please tell us through the contact form, with the page and what happened. We treat an accessibility barrier as a defect, not a feature request, and we will tell you what we find. Contact us.

What still needs real work

A real audit against WCAG 2.1 AA, and whatever statutory accessibility obligations apply in the jurisdictions we sell into. Both are outstanding; neither is described here.