Accessibility

Built to work with the settings you already use.

Last updated 2026-04-24

Sutrace targets conformance with WCAG 2.1 Level AA. Our dashboard, marketing site, and docs surface are developed against the same accessibility rules: keyboard-first navigation, semantic landmarks, system-level theme and motion preferences. This statement covers the obligations under the EU Accessibility Act (EAA, June 2025) and the US ADA.

What works today

  • Full keyboard operability across marketing, dashboard, and admin. Tab / Shift+Tab respects visual order; focus rings are visible at 2–4px.
  • System theme is respected out of the box (prefers-color-scheme: light / dark). Toggle cycles Light → Dark → System.
  • Reduced-motion is global: prefers-reduced-motion disables all Framer animations, CSS keyframes, and the hero WebGL shader (renders a single static frame).
  • Text contrast — normal text hits WCAG AA (≥4.5:1). Large text and UI controls hit AA too (≥3:1). Light-mode signal accent is a darker cyan (#0891B2) specifically for this reason.
  • Semantic structure: one <h1> per page, sequential <h2>/<h3>, real <nav>, <main>, <aside>, and labelled <button> / <a>.
  • Icon-only buttons carry aria-label; decorative SVGs carry aria-hidden="true".
  • Forms: every input has an associated label or aria-label and a visible focus state.
  • Scrollable regions are pan-friendly; no horizontal scroll is introduced on mobile.

Known gaps we are working on

  • Some inline data visualisations (sparklines, matrix glyphs) convey meaning via color plus position; a textual summary table sits alongside each one, but we plan to add pattern channels as a second belt.
  • Marketing hero uses a WebGL shader for ambience. It is purely decorative, honours prefers-reduced-motion, and is aria-hidden — but we know some assistive tech handles WebGL inconsistently.
  • Dashboard keyboard shortcuts (Cmd-K command palette) are currently documented in product but not yet exposed in a menu with screen-reader-readable summaries.

How we test

  • Automated: ESLint-a11y in CI, Lighthouse and axe-core on each build.
  • Manual: keyboard-only walkthrough of the golden paths (sign-in, create workspace, connect a source, open an alert) on every release.
  • Assistive tech: periodic spot-checks with VoiceOver (macOS), NVDA (Windows), and TalkBack (Android) — documented in our internal QA log.

Conformance basis

We measure against the W3C WCAG 2.1 recommendation at Level AA. The EU Accessibility Act applies to us as a business-to-consumer / business-to-business digital service offered in the EU; we publish this statement and keep a log of improvements per the Act’s requirements.

Feedback + how to report a barrier

Email accessibility@sutrace.io with the page, the browser / assistive tech you’re using, and what happened. We acknowledge within two business days and aim to resolve blockers within 30 days. If you think we haven’t responded adequately, your local supervisory body (for the EU, the member-state enforcement body under the EAA) can investigate.