Autonomi logo
Trust · AUTONOMi

Accessibility Statement

Conformance Target
WCAG 2.1 AA
Current Status
Partially conformant
Last Reviewed
May 3, 2026
Accessibility Contact
accessibility@autonomitech.com
ComplianceWe're being explicit about gaps. Section 4 lists every known limitation we're tracking — if you hit one we haven't documented, please report it.

1. Our Commitment

AUTONOMi is committed to making our platform accessible to as many people as possible — including people with visual, auditory, motor, or cognitive disabilities. We believe autonomous-advertising infrastructure should be usable by every dealer team that depends on it, regardless of how individual team members interact with software.

This statement describes our current accessibility posture, the standards we target, the known gaps we're working on, and how to reach us if you encounter an access barrier.

2. Conformance Target

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. The marketing surfaces (landing site, FAQ, status, legal pages) are partially conformant today; the dealer application and Campaign Studio surfaces are under active accessibility remediation toward AA conformance.

"Partially conformant" means that some content does not yet fully conform to the standard. Section 4 describes the specific gaps we are aware of.

3. Compatible Technology

AUTONOMi is designed to be compatible with the following assistive technologies and browsers:

  • Screen readers — VoiceOver (macOS, iOS), NVDA (Windows), JAWS (Windows), TalkBack (Android).
  • Browsers — latest two stable releases of Chrome, Firefox, Safari, and Edge.
  • Operating systems — macOS 12+, Windows 10+, iOS 15+, Android 10+.
  • Keyboard — full keyboard navigation across all interactive surfaces.

Older browsers and OS versions may experience degraded accessibility; we recommend keeping your software up to date.

4. Known Limitations

We're being explicit about gaps so you know what to expect. These are tracked and prioritized for remediation:

  • Custom dropdowns and date pickers in Campaign Studio (mode=Build, mode=Budget) — keyboard navigation works but screen-reader announcements are not yet fully descriptive. Targeted for AA conformance Q2 2026.
  • Animated visualizations on the marketing site (decision cascade, hash-chain ribbon, channel matrix) — decorative motion respects prefers-reduced-motion and animations stop or simplify when set, but some text content embedded in SVG visualizations is not yet exposed to screen readers as structured headings. Tracked.
  • Color contrast on the canonical glassmorphic surfaces meets WCAG AA in standard text contexts; some uppercase-tracking eyebrow labels at small sizes (10–11px) on accent-colored backgrounds are below the 4.5:1 ratio. Targeted fix Q1 2026.
  • Compliance Guardian terminal output in the AEGIS dashboard streams as a typewriter effect; the live region announcement is currently coarse. Refining granularity is on the roadmap.
  • Charts & data visualizations in Analytics provide tabular fallbacks for screen readers but the navigation between visual and tabular forms is not yet fully discoverable by keyboard alone.

5. Accessibility Features

What we have shipped:

  • Full keyboard navigation across all primary surfaces (landing, app, FAQ).
  • Visible focus indicators on all interactive elements (buttons, links, form fields).
  • Semantic HTML structure with proper landmarks (main, nav, article, section) and heading hierarchy.
  • Alternative text on all informative images; decorative images marked with aria-hidden="true".
  • ARIA attributes on custom controls (accordion items, modal dialogs, tab panels) to communicate state and role.
  • Respect for the prefers-reduced-motion media query — animations simplify or pause when the operating system setting is on.
  • Form fields associated with labels; validation errors announced inline.
  • Color is never used as the sole means of conveying information (status indicators always pair color with text or icon).

6. Reporting Access Barriers

If you encounter an accessibility barrier on AUTONOMi, please email accessibility@autonomitech.com with:

  • The page or feature where the barrier occurred.
  • Your assistive technology setup (screen reader version, browser, operating system).
  • What you expected to happen vs what actually happened.
  • Any workarounds you've identified (helps us prioritize).

We aim to acknowledge accessibility reports within 2 business days and provide an initial remediation timeline within 5 business days. For barriers that block your ability to use a critical feature, we'll work with you on a manual workaround in parallel with the engineering fix.

7. Accommodations Beyond the Software

If you need our assistance with any aspect of AUTONOMi — onboarding, billing, support, contract review — and the standard self-service flow is not accessible to you, contact accessibility@autonomitech.com and we will arrange an alternative channel (phone walkthrough, screen-share with audio narration, written transcript, etc.) at no additional cost.

8. Last Reviewed

This statement was last reviewed on the date in the page metadata above. We re-audit our accessibility posture quarterly and update this statement to reflect current conformance and known gaps.