Accessibility Statement

Altaius is actively developed to meet and maintain Web Content Accessibility Guidelines (WCAG) 2.2 Level AA standards. We believe that leadership capability should be accessible to everyone, and we integrate inclusive design principles from the first wireframe to the final deployment.

Our platform architecture is built to support a wide range of accessibility needs. Key features include:

Keyboard Navigation: The entire platform, including complex simulations, is operable without a mouse. We implement focus traps, visible focus states, and logical tab sequences.

Screen-Reader Support: We use semantic HTML landmarks and ARIA attributes (including polite live regions) to ensure compatibility with modern screen readers.

Arabic RTL: Full, native right-to-left support for Arabic, ensuring visual flow and cognitive ease match the cultural context.

Color Contrast: All text and critical UI elements adhere strictly to WCAG 2.2 AA contrast ratios.

Captions & Transcripts: Any multimedia or audio-driven scenario content includes accurate text alternatives.

Reduced Motion: We respect operating system `prefers-reduced-motion` settings, disabling unnecessary animations and transitions for users prone to motion sickness.

Form Error Clarity: Forms provide immediate, clear, text-based error messages that do not rely solely on color to convey failure states.

While we strive for complete accessibility, some complex interactive visual charts in the Executive Dashboard may currently pose challenges for screen-reader-only users. We are actively working on providing accessible tabular data alternatives for these visualizations in our next release cycle.

We continuously audit our platform using both automated tools and manual testing, including dedicated screen-reader testing in Arabic and English environments. Our development pipeline prevents regressions by enforcing accessibility checks on every code commit.

Accessibility is an ongoing journey. If you experience any barriers while using Altaius or wish to report an accessibility issue, please contact our accessibility team directly by Contacting the Privacy Team or through our dedicated incident reporting form. We prioritize accessibility-related bug reports in our development cycles.