Skip to main content
Corvus Connection

Accessibility

Corvus Connection should be usable by everyone, however you stream. We target WCAG 2.2 Level AA across this documentation site and the desktop app, and we adopt Level AAA provisions wherever they are practical. This page describes what is in place today and what we are improving next.

Conformance status

  • Target: WCAG 2.2 Level AA (Web Content Accessibility Guidelines).
  • Docs site: conforms to AA in light, dark, and high-contrast themes. Every build is scanned automatically before it ships (see How we test, below).
  • Desktop app: AA is substantially in place (theming, high contrast, keyboard and target-size support), with an ongoing hardening pass on the remaining screens.

Perceivable

  • Themes: System, Light, Dark, and High Contrast, chosen from the toolbar and remembered across visits. Your OS color-scheme preference is honored on first load. (WCAG 1.4.3 AA)
  • Contrast: text and meaningful UI (borders, focus rings, node port bands) meet the AA contrast ratios in every theme. Node headings flip their ink to keep labels legible on any category color. (WCAG 1.4.3 / 1.4.11 AA)
  • Windows High Contrast and forced colors: the site respects the OS palette. Shadows are replaced with real borders, so structure never depends on color alone. (WCAG 1.4.1 A)
  • Reduced motion: if you ask your system to reduce motion, scroll and reveal animations are turned off and content renders immediately. (WCAG 2.3.3 AAA)
  • Text alternatives and reflow: images carry alt text (decorative art is hidden from screen readers), and layouts reflow down to narrow and zoomed viewports without loss of content. (WCAG 1.1.1 A / 1.4.10 AA)

Operable

  • Full keyboard support: every link, menu, and control is reachable and operable with the keyboard alone. No mouse is required, and there are no keyboard traps. (WCAG 2.1.1 / 2.1.2 A)
  • Skip to main content: the first Tab stop jumps past the header straight into the page content. (WCAG 2.4.1 A)
  • Visible focus: a clear focus ring follows keyboard focus on every interactive element, focused content is never hidden behind the sticky header, and menus return focus to their trigger on Escape. (WCAG 2.4.7 / 2.4.11 AA)
  • Generous targets: standalone controls are at least 44 by 44 px and inline links at least 24 px. That meets the AA minimum and, for most controls, the stricter AAA size. (WCAG 2.5.8 AA / 2.5.5 AAA)

Understandable

  • Consistent navigation: the header, footer, and search sit in the same place on every page, with the current section clearly marked. (WCAG 3.2.3 AA)
  • Meaningful structure: one h1 per page and an ordered heading outline let assistive tech build an accurate page map. On navigation, focus moves to the new page's heading. (WCAG 1.3.1 / 2.4.3 A)
  • Plain language: the docs favor direct, low-jargon copy, with terms explained where they first appear. The page language is declared for screen readers. (WCAG 3.1.1 A)

Robust

  • Semantic markup: real nav, main, section, and ul elements, and genuine navigable links, so pages are crawlable and work with screen readers and with opening links in a new tab. (WCAG 1.3.1 A / 4.1.2 A)
  • Built on Fluent UI: interactive components come from Microsoft's Fluent UI React library, which ships accessible roles, states, and focus management out of the box.

In the desktop app

The Windows desktop companion carries the same commitments into WinUI 3:
  • Standard Dark, Accessible Light, and High Contrast themes, with brand controls that adopt the system colors under High Contrast.
  • Keyboard navigation, visible focus, and touch-friendly target sizes across the app's pages.
  • Closed captioning of your own audio for streams, with a mute hotkey, as a built-in feature.

How we test

  • Automated audits on every build: we run axe-core against representative pages with the WCAG 2.0, 2.1, and 2.2 A and AA rule sets, in light, dark, high-contrast, and forced-colors modes. A single violation fails the build.
  • Keyboard and focus checks: an automated pass verifies the skip link, focus rings, menu keyboard operation, Escape handling, and the absence of keyboard traps.
  • Manual review: real screen-reader and High Contrast Mode passes cover the behaviors automation cannot fully judge.

What we're improving next

  • Complete the desktop AA hardening pass so every screen matches the docs site's conformance.
  • Reach Level AAA where feasible: enhanced contrast (1.4.6) and enhanced target size (2.5.5) beyond the controls that already meet them.
  • Broaden automated coverage from representative pages toward the full catalog, and add reduced-transparency handling.
  • Accessible-authoring guidance for the visual node editor and overlays, so what you build for your viewers is accessible too.

Tell us

Found a barrier, or need content in another format? Email support@theomenden.com and we will work with you. We aim to acknowledge accessibility reports quickly and fix confirmed issues in a following release. You can also browse the acknowledgements for the tools we build on.