Accessibility Statement

Effective: April 29, 2026

We aim to make the Axolotl Army Portal usable by everyone and target conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA across the application. This statement applies to portal.axolotlarmy.net and the marketing site at www.axolotlarmy.net.

What we do today

• Keyboard-navigable flows for sign-in, dashboard, video generation, calendar, and editor surfaces.
• Visible focus indicators on every interactive element.
• Form fields associated with persistent labels (not placeholder text); error messages exposed to assistive technology.
• Color contrast ratio of at least 4.5:1 for body text and 3:1 for large text and UI controls.
• Honoring prefers-reduced-motion for animations and transitions.
• ARIA landmarks on layout regions (main, nav, complementary) and live regions (role="status") for async toasts, errors, and progress.
• Modals built on a shared <Modal> primitive that handles focus trap, Escape-to-close, and click-outside dismiss.
• Destructive actions go through a Promise-based confirm dialog rather than the native window.confirm() for full keyboard + screen-reader support.
• Maximum-scale viewport headers omitted so users can pinch-zoom (a WCAG 2.2 requirement).
• Full keyboard support in the global Command Palette (⌘K, arrow keys, Enter, Escape).

Known limitations

• The video editor timeline currently relies on pointer interactions for fine-grained trim/split. Keyboard equivalents are on the roadmap; in the meantime an admin can perform these actions on request.
• Some long-form analytics charts use canvas rendering and do not yet expose data tables for screen readers; we will ship a "view as table" toggle.
• Voice features (AXY voice synthesis, slideshow narration) are optional; the same content is always available as readable text.
• Embedded social platform previews (TikTok, Instagram) inherit those platforms' accessibility behaviour, which we do not control.

Standards referenced

• WCAG 2.2 Level AA (W3C, October 2023)
• Section 508 of the US Rehabilitation Act
• European Accessibility Act 2025 (EN 301 549)
• Americans with Disabilities Act (ADA) Title III as applied to private sector websites

Assistive technology compatibility

We test with VoiceOver (macOS, iOS), TalkBack (Android), NVDA (Windows), and JAWS (Windows) on Safari, Chrome, Firefox, and Edge current versions. If your assistive technology stack runs into a barrier we missed, please let us know.

How to report an accessibility barrier

If you encounter an accessibility barrier, email support@axolotlarmy.net with a description of the issue, the page or feature affected, the device + assistive technology you were using, and (where helpful) a screen recording. We aim to respond within 5 business days.

Alternative format requests

If a portal feature is currently inaccessible to you, contact us at support@axolotlarmy.net and we'll work with you to provide an alternative way to complete the task — including, where reasonable, manual assistance from our support team.

Continuous improvement

Continuous improvement. Accessibility is part of our PR review checklist. New features ship with keyboard support, focus management, and screen-reader-friendly copy. We test critical flows manually with assistive technologies before each release. We have not yet integrated automated accessibility scanning (e.g. axe-core) into CI; that is on our roadmap.