Legal

Accessibility Statement

Effective January 1, 2024 · Last reviewed May 18, 2024

Our Commitment

Uniguard Pro is committed to providing a security monitoring platform that everyone can use, including people with disabilities. Security alerts and emergency communications must reach every user reliably and effectively regardless of how they perceive or interact with the web.

We design and build the platform to conform with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. This statement summarizes our current conformance, documents known gaps, and explains how to reach us if you encounter an accessibility barrier.

Conformance Status

The Uniguard Pro web application substantially conforms with WCAG 2.1 Level AA. “Substantially conforms” means most parts of the application meet the standard, with documented exceptions listed in the next section.

We are working toward full conformance and toward Level AAA where feasible. WCAG 2.2 conformance is on our roadmap as authoring tools and component libraries update to support the newer success criteria.

Accessibility Features

The following accessibility features are implemented across the Uniguard Pro web application:

  • Keyboard navigation — all interactive elements (links, buttons, form fields, dropdowns) are reachable and operable with keyboard only. Visible focus indicators throughout.
  • Screen reader support — semantic HTML, ARIA roles where native semantics fall short, descriptive labels on every form input, live-region announcements for dynamic alarm updates.
  • High contrast — the operator console uses a dark theme tuned for contrast ratios above 4.5:1 on body text and 3:1 on large text. Status badges (severity, alarm state) pair colour with text labels so they remain meaningful in monochrome or with colour-blindness simulation.
  • Text scaling — the application reflows cleanly at up to 200% browser zoom without horizontal scrolling.
  • Reduced-motion support — animations (live-alarm pulse, transition effects) respect the prefers-reduced-motion media query.
  • Form validation — errors are announced inline next to the offending field, identified by colour AND text, and associated with the field via aria-describedby.
  • Multi-channel notifications — security alerts are delivered via SMS, voice, AND email so users who depend on assistive technology can choose the channel that works best.
  • Modal dialogs — confirmation dialogs trap focus, restore focus on dismissal, and can be cancelled with the Escape key.

Known Accessibility Gaps

We’re honest about where we’re still working to improve. The following gaps are tracked and prioritized:

SurfaceGapMitigation
Camera snapshot imagesSnapshots in the alarm timeline don't have detailed alt text — they show as 'Snapshot from {device-name} at {time}'.Device name and timestamp are read aloud by screen readers. Full visual description requires human review on a per-image basis.
Infrastructure dashboard (superadmin)The fleet bar uses dense numeric tables that benefit from a screen-reader summary mode we haven't built.Surface is superadmin-only; numeric data is also accessible via the read API.
UniFi Protect camera live viewThe 'Open in UniFi Protect' link launches a third-party tool whose accessibility we don't control.Use the snapshot timeline (which IS accessible) for review-after-the-fact. Live-view is informational.
Stripe Checkout (billing flow)The payment page is rendered by Stripe and follows Stripe's accessibility — not directly under our control.Stripe Checkout has its own WCAG 2.1 AA conformance. We pass through their accessible-by-default flow.

If you encounter an accessibility issue not listed here, please report it (see “Feedback & Assistance” below) — we’ll add it to this list and prioritize a fix.

Testing & Assistive Technology

We test the platform during development with the following combinations. Where possible we use the latest stable releases:

  • Screen readers: VoiceOver (macOS / iOS), NVDA + Firefox (Windows), TalkBack (Android)
  • Keyboard-only navigation in Chrome, Firefox, Safari, Edge
  • Browser zoom up to 200% in the same browsers
  • Spot-checks with browser-extension accessibility auditing tools (axe DevTools, Lighthouse) on new and recently-changed UI surfaces
  • Manual review of new UI surfaces against the WCAG 2.1 AA checklist before release

We don’t yet have automated accessibility scans gating our continuous-integration pipeline — adding that (running axe-core against staging on every pull request) is on our roadmap. Until then, we rely on the manual review + spot-check workflow above.

Feedback & Assistance

If you have trouble using any part of Uniguard Pro, or you’d like to report a barrier we should know about, please contact us:

We aim to acknowledge accessibility reports within two business days and to provide a fix or written remediation plan within 15 business days. Critical barriers that block emergency-alert delivery are triaged as security incidents and addressed within 24 hours.

If you need help completing a task in the meantime, our support team can walk you through it by phone or take the action on your behalf upon your request.

Standards & References

Formal Complaints

If you believe Uniguard Pro has not met its accessibility obligations and our team has been unable to resolve the issue, you may file a complaint with the relevant regulator in your jurisdiction:

  • Ontario, Canada: Accessibility for Ontarians with Disabilities Act compliance — Ministry for Seniors and Accessibility
  • United States: U.S. Department of Justice Civil Rights Division (ADA-related); U.S. Access Board (Section 508-related)
  • European Union: your national data protection / accessibility authority under the Web Accessibility Directive
Accessibility Statement — Uniguard Pro — Uniguard Pro