legal · accessibility

Usable for everyone.

We target WCAG 2.2 AA on every customer-facing page. This page lists what works today, what doesn't yet, and how to reach us when something blocks you.

effective · April 1, 2026last updated · April 12, 2026

1. Our commitment

ZingRoam targets WCAG 2.2 Level AA across the customer-facing surfaces — marketing site, catalog, plan detail, checkout, account, and help. We audit each release against this bar and publish known gaps instead of waving them away.

2. What works today

  • Full keyboard navigation: every action reachable without a mouse, visible focus ring.
  • Screen-reader markup: semantic HTML, ARIA only where semantics fall short, labels on every form field.
  • Color contrast: 4.5:1 for body text, 3:1 for large text and non-text indicators — tested with automated and manual checks.
  • Reduced motion: prefers-reduced-motion disables non-essential animations.
  • Resizable text: pages stay usable at 200% zoom and with user-overridden font sizes.
  • Language direction: full RTL support for Arabic, with locale-appropriate number and date formatting.

3. Known gaps

We keep a public list of areas we've flagged but haven't fixed yet. When you reach us about one, we share the target fix date.

  • Admin console — WCAG AA-ish but not yet audited to the same bar as customer-facing surfaces. Fix in flight.
  • PDF invoices — generated in a template that doesn't yet expose full semantic tagging. Accessible HTML receipts always available as an alternative.

4. How we test

  • Automated: axe-core in CI on every PR; Lighthouse accessibility score above 95 for each public page.
  • Manual: keyboard-only runs of the critical flows (browse → plan detail → checkout → account) each release.
  • Assistive tech: VoiceOver on macOS/iOS and NVDA on Windows are our primary AT test targets; TalkBack spot-checks on Android.
  • External audit: full third-party WCAG 2.2 AA audit at least once per year.

5. Feedback

Accessibility is a moving target — devices change, specs get tighter, we ship new features. If you hit something that didn't work the way you expected, please tell us. The fix is almost always smaller than the bug.