Accessibility commitments

Accessibility Statement

Accessibility statement for auroracommand.ai, the public Trust Center, and the standard Aurora Command product experience.
Last updated
March 15, 2026
Accessibility contact
accessibility@auroracommand.ai
Plain-English summary

Aurora Command is designed so teams can navigate, understand, and act on the workflow without unnecessary barriers. Accessibility review is part of design, QA, and release review for core public and product workflows.

We aim for WCAG 2.1 Level AA as reasonably applicable to the core web and app experience, while recognizing that some third-party dependencies and complex workflows can still require additional remediation.

Publication details
Owner
Borealis Security, Inc. Product
Published version
Published Aurora legal release · 2026-03-15
Rendered document hash
cfa91da8079eeb95a7ff8d85a5bb7278e8d07dac08914e9a502c740bf296e8e6
Reference files
48_External_Aurora_Command_Accessibility_Statement.txt
This statement describes Borealis's current accessibility commitments and support path. It does not create a warranty that every page, export, or dependency will be accessible in every circumstance.

1. Scope

This statement applies to Aurora Command public marketing pages, trust and security pages, contact and walkthrough flows, and the standard Aurora Command product experience made generally available to customers. It does not create a guarantee that every page, export, reviewer artifact, integration surface, or third-party dependency will be error-free or accessible in every circumstance.

2. Target standard and review approach

  • Target benchmark: WCAG 2.1 Level AA for the core web and app experience, as reasonably applicable.
  • Accessibility considerations should be part of design, QA, and release review for core workflows.
  • Review methods may include automated scans, keyboard-only navigation tests, zoom and reflow checks, and manual spot checks of headings, forms, dialogs, tables, and review or share flows.

3. Product-specific accessibility commitments

  • Maintain clear structure, labels, and status messaging in key workflows.
  • Avoid unnecessary motion, low-contrast controls, and ambiguous actions where practical.
  • Keep important product actions understandable at standard zoom and responsive layouts.
  • Accept and triage reported barriers in the ordinary product-support process.

4. Known limitations and dependencies

Aurora Command may depend on browsers, identity providers, third-party integrations, exported files, embedded viewers, or external reviewer devices that Borealis does not fully control. Some workflows, attachments, or embedded content may require additional remediation over time. Borealis may prioritize remediation by severity, feasibility, user impact, and roadmap constraints.

5. How to get help

Users who encounter an accessibility barrier can contact accessibility@auroracommand.ai, support@auroracommand.ai, or privacy@auroracommand.ai. Reports should identify the page, workflow, or screen involved, what happened, and any device, browser, or assistive-technology details that can help reproduce the issue.

6. Alternative paths and support

Where practicable, Borealis may provide a reasonable alternative path for affected users, such as support assistance, alternate delivery of needed information, or a different workflow to accomplish the task.

7. Changes to this statement

Borealis may update this statement as Aurora Command evolves. The published version should display a current last-reviewed or last-updated date whenever revised.

8. Contact information

Borealis Security, Inc.

3300 Arctic Blvd

Suite 201 PMB 1085

Anchorage, AK 99503

United States

Accessibility: accessibility@auroracommand.ai

Support: support@auroracommand.ai

Security: security@auroracommand.ai

Privacy: privacy@auroracommand.ai

Need an Alternate Path?

If a barrier blocks procurement, review, or product use, contact the accessibility or support channels so Borealis can provide the fastest workable path.