Skip to main content
Back to home

Accessibility statement

Statement last reviewed by hand: August 7, 2026. The automated checks described below run on every change.

In short: Snaga is built to WCAG 2.2 level AA. Some of that is enforced by tests that run on every change and can fail a release; the rest is reviewed by people, less often. Below says which is which — and we want to hear from you if anything gets in your way.

Conformance

Squad AI Inc is committed to making the Snaga platform accessible in accordance with the European Accessibility Act (Directive (EU) 2019/882) and the harmonised standard EN 301 549. The platform is designed and tested against WCAG 2.2 level AA, including the criteria new in 2.2: minimum target sizes, alternatives to dragging, focus that is never obscured, accessible authentication, and no redundant data entry.

What we do

  • Colour contrast is enforced by automated tests for every theme the platform ships — text meets 4.5:1, interface components meet 3:1.
  • Every surface is keyboard-operable: panels resize with arrow keys, canvases expose focusable nodes, dialogs trap and restore focus, and a skip link leads to the main content.
  • Live agent activity is announced through polite screen-reader regions without flooding assistive technology during streaming.
  • We honour your system preferences: reduced motion, increased contrast, forced colours (Windows High Contrast), and light or dark colour schemes.
  • Sign-in uses a one-time code that can be pasted and autofilled — no puzzles or cognitive tests.
  • Four checks fail a build rather than file a ticket: contrast ratios for every semantic pair in all four palettes; an axe scan of the public pages in the browser, which catches the mixing a token-level check cannot see; tap targets measured as boxes at 320px wide, because a class named for 24 is not evidence of 24; and a tab through each public page asking whether the centre of the focused control still resolves to it. The fourth runs on the pages anyone can open. The same walk over the signed-in screens needs a credential the build does not hold, so there it is run by hand and carries the date below.
  • Manual keyboard and screen-reader passes happen periodically rather than on every release, and this statement carries the date of the last one. Where a criterion is met by design rather than by a test — sign-in has no cognitive test to fail — that is what the entries above describe.

What we know is not right yet

  • The visual node canvas (Mission Control) offers keyboard access to nodes and connections, but complex re-wiring is easier with a pointer; every action it performs is also available through standard forms and chat.
  • Content produced by AI agents (generated documents, third-party images) may not always include full alternative text. You can ask the agent to describe any output it produced.

Telling us, and getting in touch

If you encounter an accessibility barrier, we want to fix it. Write to support@snaga.aiwith "Accessibility" in the subject, or use the contact form. We aim to respond within 5 business days. Support conversations themselves are available in accessible, text-based form.

Enforcement

If you are in the European Union and are not satisfied with our response, you may contact the market surveillance authority responsible for the European Accessibility Act in your member state.