Accessibility · WCAG 2.2 AA Targeted

Accessibility
Statement.

WCAG 2.2 AA targeted. Section 508 / VPAT in preparation for 2026.

STRATUS AccessGov is built and maintained with accessibility in mind from the design phase forward, not retrofitted afterward. This page describes what we currently meet, what we're working toward, and how to report an accessibility issue.

Current Posture

Where we are.
Honestly.

Targeted · WCAG 2.2 AA

Color, contrast, keyboard, focus.

Our website and product UI are designed against WCAG 2.2 AA criteria. We test with axe-core in CI, manual keyboard navigation, and screen-reader review (NVDA, VoiceOver, JAWS) on critical flows.

  • 4.5:1 contrast ratio for body text · 3:1 for large text and UI elements
  • Core SaaS workflows are designed to be keyboard-navigable, with full coverage targeted as part of the VPAT process
  • Visible focus indicators on every interactive element
  • Semantic HTML, ARIA where required, never as a substitute
  • Form labels and error messages associated programmatically
In Preparation · 2026

Section 508 / VPAT 2.5

We are preparing a complete VPAT 2.5 (Voluntary Product Accessibility Template) covering Section 508 Refresh, EN 301 549, and WCAG 2.2 AA. Target: full document published Q4 2026.

Founding Partners receive interim VPATs scoped to their deployment surface during POC.

Built In

Tech that helps, not hurts.

  • System fonts available — no required font downloads for screen reader users
  • Reduced-motion preferences respected (prefers-reduced-motion)
  • No flashing content above 3 Hz
  • Skip-to-content links on every page
  • Time-out warnings before session expiry
Known Limitations

What we're still working on.

Some complex data visualizations (the Identity Graph, the Architecture diagram) currently rely on image and SVG content. Text alternatives are provided, but we are working on fully accessible interactive equivalents. Target: Q2–Q3 2026.

The legacy administrative console (deprecated) does not meet our current WCAG targets and is being phased out.

Reporting an Issue

Found something?
Please tell us.

We respond to accessibility reports within 5 business days with a triage decision and a target resolution timeline. Critical accessibility blockers (anything preventing core functionality) are treated as P1 production issues.

Email: [email protected]