Accessibility

    This statement covers both the Atlarix website and the Atlarix desktop app for macOS, Windows, and Linux.

    We have not completed a formal WCAG conformance audit, so we do not claim a conformance level. Below is an honest account of what works today and what does not — we would rather tell you the real state than publish a badge we have not earned.

    Keyboard and pointer

    • Both the site and the app are built on accessible component primitives (Radix UI), which provide focus management, focus trapping in dialogs, and arrow-key navigation in menus and lists.
    • In the app, chat, approvals, and mode switching are reachable without a mouse. Approve and reject actions on a file change are keyboard-operable inline in the conversation.
    • The built-in terminal is a real interactive shell, so it takes keyboard input directly, including tab completion and arrow keys.

    Vision and display

    • Interface zoom — the app scales to 90%, 100%, 110%, 125%, or 150% from Settings, independently of your OS display scaling.
    • Light, dark, and system themes — the app follows your operating system's appearance setting by default and updates live when you change it.
    • Reduced motion — the website honours theprefers-reduced-motionsetting and suppresses decorative animation when you have asked your system for less of it.
    • Decorative icons are hidden from assistive technology rather than announced as meaningless labels, and images carry text alternatives.

    Alternatives to typing

    The app includes voice-to-text for composing messages. It runs on-device by default using a local Whisper model — no account, no API key, and nothing leaves your machine — so it is available to everyone rather than only to users with a cloud speech subscription.

    Because Atlarix works alongside your editor rather than replacing it, you can also keep using the editor and assistive setup you already have configured, and use Atlarix for the agent work.

    Known gaps

    • No formal audit. We have not had the site or the app assessed against WCAG 2.2 by an auditor, and we have not run systematic screen-reader testing across NVDA, JAWS, and VoiceOver.
    • Screen-reader announcements are incomplete. Streaming assistant output and live status updates are not yet consistently announced, so a screen-reader user may not be told when a response finishes or when an approval is waiting.
    • The terminal and code diffs are difficult non-visually. A terminal emulator and a side-by-side diff are hard to convey through a screen reader, and we have not solved this. It is the area we would most like to hear from you about.
    • No skip-to-content link on the website yet.

    Found a barrier? Please tell us. Email support@atlarix.dev with what you were trying to do, the assistive technology you use, and where it broke down. Accessibility reports are treated as bugs, not feature requests.

    This statement describes the product as it currently ships and is updated as things change.