Accessibility Statement

We design and build RAgencyOS to be usable by everyone, including people with visual, auditory, motor, or cognitive disabilities. Our target conformance level is the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, published by the World Wide Web Consortium.

Accessibility is an ongoing effort. Some parts of the Service meet this target today; others do not. We treat accessibility gaps as bugs and fix them on the same priority as functional bugs.

• The application is built with semantic HTML elements so screen readers can navigate naturally.
• Interactive controls (buttons, links, form fields) are reachable by keyboard. We test the major flows (sign-in, dashboard, statement upload, agent management) with keyboard only.
• Color is not the only signal we use to convey meaning. Categorical states (paid / unpaid, success / error, draft / published) also use text and shape cues.
• Text contrast on primary surfaces meets or exceeds the WCAG 2.1 AA threshold of 4.5:1 for body text.
• Form fields have programmatic labels. Error messages are associated with the fields they refer to.
• Modal dialogs trap focus and restore it on close.
• We do not auto-play audio or video.

• We have not commissioned a third-party accessibility audit. We will publish the results when we do.
• Some legacy components (older charts and tables) may not have complete screen-reader labels.
• We do not currently provide a Voluntary Product Accessibility Template (VPAT). One is on our roadmap; if your procurement team requires it before then, email us and we’ll work through their requirements directly.
• Right-to-left language layouts are not supported (we serve a U.S. English-only customer base today).

If something in the Service is hard or impossible to use because of an accessibility issue, whether keyboard, screen-reader, contrast, motor, or cognitive, please email support@ragencyos.com with:

• What you were trying to do.
• What blocked you (and which assistive technology, if applicable).
• Which URL or part of the Service it happened on.

We aim to acknowledge within one business day and fix high-impact issues in the next release. For lower-priority issues, we’ll explain our timeline and check in with you when it ships.

Accessibility questions or reports: