Legal

Accessibility Statement

Effective: May 22, 2026. TinyGuard LLC, 7428 SW Ashford St, Tigard, OR 97224. Accessibility contact: accessibility@tinyguard.co.

1. Our commitment

TinyGuard's marketing site, dashboard application, and family portal target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. We treat accessibility as part of how we build the product, not as an after-the-fact checklist.

This statement is an honest snapshot of where we are. We're a small team in pilot phase, and full WCAG 2.1 AA conformance across every screen of a 200+ route application is an ongoing effort, not a binary state we already achieved. Where we have known gaps, this statement says so.

2. Current posture

Surface	Status	Notes
tinyguard.co (marketing)	Largely conformant	Keyboard navigable, sufficient color contrast, semantic landmarks. Known issue: video demo embeds do not all yet have captions. Mitigation: every video demo also has an equivalent screenshot tour available on the same page.
app.tinyguard.co (dashboard)	Substantially conformant	Keyboard accessible across primary flows (login, daily reports, billing, care log, parent portal). Screen-reader support tested in NVDA + VoiceOver for primary flows. Known gaps: some camera-grid surfaces use drag-handle interactions that are not fully keyboard-equivalent today; complex tables in EVV reports may not announce row headers correctly on some screen readers.
Kiosk check-in (camera-attached devices)	Limited	Kiosks are designed for tap-based facility check-in and do not have alternative input modes. Facilities are responsible for providing a non-kiosk alternative check-in path for any individual unable to use the kiosk (manual sign-in by staff, PIN entry, QR badge). This is documented in our setup guidance for facility operators.
Mobile app (Capacitor)	Early	The Capacitor-based mobile app is in early build. Accessibility audits are queued before the App Store / Play Store launch. iOS VoiceOver and Android TalkBack support is partial today.
PDF exports (care reports, invoices, compliance docs)	Partial	Generated PDFs include semantic structure (headings, lists, tables with row headers) but are not yet tagged-PDF/UA conformant. If you need a tagged PDF or a different format (CSV, JSON), email accessibility@tinyguard.co.
Live video stream (HLS + WebRTC)	Functional	Live camera streams are by their nature visual; no transcript or audio description is generated. Audio capture is OFF by default on cameras; when enabled by a facility, audio is part of the recording stream but no real-time transcript is provided. This is a known limitation of video-monitoring products generally; we are evaluating whether real-time captioning belongs on the product roadmap.

3. How we test

Automated tooling — axe-core runs in our CI for every page in tinyguard-web via a Playwright integration. Violations at error severity block merge.
Manual keyboard-only testing — primary flows (login, dashboard navigation, daily report drafting, billing, parent portal) are exercised with keyboard only at every release.
Screen reader spot-checks — NVDA on Windows and VoiceOver on macOS, on primary flows, before any minor release.
Color contrast — all foreground/background pairs targeted at 4.5:1 for body text, 3:1 for large text; verified at design time and re-verified by axe-core.
What we don't yet do — full external WCAG 2.1 AA audit by a third party. That is planned once we cross our first 25 paying facilities. If you require a documented third-party audit as a procurement condition, tell us — we can prioritize.

4. Standards and laws we account for

Americans with Disabilities Act (ADA) Title III — the de facto US standard requires WCAG 2.1 AA as a benchmark for public-accommodation websites.
Section 508 of the Rehabilitation Act — federal contractor benchmark, also references WCAG 2.0 AA / 2.1 AA.
State laws — California's Unruh Civil Rights Act, New York Executive Law §296, and similar statutes have been read by courts to extend ADA-style requirements to commercial websites.
EN 301 549 — European public-procurement accessibility standard; relevant if a customer requires it under a procurement.

5. Requesting an accommodation or reporting a barrier

📬 Contact accessibility@tinyguard.co

If you encounter an accessibility barrier on any TinyGuard surface, please tell us. We respond within five (5) business days and aim to resolve verified barriers within thirty (30) days, depending on complexity. If a resolution will take longer, we provide an interim accommodation (alternative format, manual support).

When reporting a barrier, please include: the URL or screen where you encountered it, the assistive technology you were using, and what you were trying to accomplish. This lets us reproduce the issue quickly.

For accommodations during the sales process (audio of demo recordings, alternative formats for the BAA template, large-print versions of pricing documents), email accessibility@tinyguard.co at any point.

6. Feedback

Accessibility is an ongoing commitment. We learn from real users with disabilities and from accessibility-expert input. If you'd like to participate in a usability session or have suggestions, contact accessibility@tinyguard.co.