Accessibility

Critical communications tools cannot be inaccessible. If someone cannot operate the console, they cannot warn anybody.

Our commitment

We build toward WCAG 2.1 Level AA across the public site, the setup flow and the customer command center.

What is implemented

• Full keyboard navigation with a visible focus state on every interactive element.
• Semantic structure and labelled controls for screen readers.
• Contrast ratios checked against AA for body and interface text.
• prefers-reduced-motion respected — all animation, including the broadcast demonstration, the scanline and the ticker, resolves to a static state.
• A skip link to main content on every page.
• Responsive layout down to small mobile widths; no horizontal page scroll.
• Tables and wide content scroll within their own container rather than the page.

Recipients

Messages arrive as ordinary SMS/MMS, so they inherit the accessibility features the recipient already uses on their own device — text size, screen reader, voice control. That is a deliberate advantage of not requiring an app.

Known gaps

We keep this section honest rather than empty. Data-dense operational views are the hardest to make fully screen-reader friendly and remain an active area of work.

Feedback

If any part of this product is difficult to use, tell us at support@armit.co and describe what happened. Accessibility reports are treated as defects, not suggestions.