Accessibility

Accessibility statement

Cyber Ambush is operated by Sterling Readiness Group, LLC. This page states the standard we design against, what has and has not been verified, the limitations we know about, and how to tell us when something blocks you.

Effective date: September 17, 2026

Our target

The standard we design and build against.

  • We target the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA.
  • That is the target we work toward. It is not a claim that the platform currently conforms to it.
  • In practice this means keyboard operability, visible focus, text alternatives for meaningful images, labeled form fields, sufficient color contrast, and status information conveyed by more than color alone.

Conformance status

What has been verified, and by whom.

  • Conformance has not been independently audited.
  • No Voluntary Product Accessibility Template (VPAT) or Accessibility Conformance Report has been produced yet.
  • Our current assessment is internal and ongoing, so parts of the platform may not meet every Level AA success criterion.
  • We will not describe the platform as WCAG 2.1 Level AA conformant until an independent audit supports that statement.

Known limitations

Where we know the experience may fall short today.

  • A tabletop exercise runs on a shared clock. A timed, continuously updating live interface can present real difficulties for people who need more time, who use a screen reader, or who are sensitive to frequent content changes.
  • The after-action report export is the accessible record of any exercise. It is a static document containing the objectives, the inject timeline, the decisions recorded, the timestamps and the findings, and it can be read at any pace with assistive technology.
  • An Operator can pace or hold injects, so a Participant who needs additional time can be accommodated within the exercise itself. Ask your Operator before the exercise begins.
  • Some dense tables and framework mapping views are easier to use on a wider screen than on a small one.

Reporting a barrier

How to tell us something is inaccessible.

  • Report an accessibility barrier through the contact page, choosing the "Report a product bug" topic.
  • Tell us the page or screen, what you were trying to do, the assistive technology and browser you were using, and what happened instead.
  • We will acknowledge your report, tell you what we find, and describe any workaround while a fix is in progress.
  • If you need an exercise record in a different format, ask and we will work with you to provide one.

Changes to this statement

How this page is kept current.

We revise this statement as the platform changes and as limitations are resolved or discovered. The effective date at the top of the page shows when it was last revised.