Legal

Accessibility Statement

Last updated: September 27, 2026

Our Commitment

Boba Globe wants its iOS and Android apps, public website, account flows, billing and subscription flows, legal pages, and creation controls to be usable by people with disabilities. We use the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as our target for new and updated web content, and apply the same success criteria as far as they fit to the app interface, which runs in the platform web view alongside native purchase, sharing, and file screens.

Current Accessibility Work

  • Public legal pages use semantic headings, links, lists, and page titles.
  • Sign-in, upgrade, export, route-provider, dashboard, and editor dialogs use labels, accessible names, and ARIA attributes where needed.
  • Core actions are designed to work with keyboard navigation where the underlying browser and component support it.
  • Form errors and loading states are presented with text and status messaging where practical.
  • We review color contrast, focus visibility, text alternatives, keyboard access, and status messages as part of launch readiness.
  • In the iOS and Android apps, controls use accessible names, roles, and live status messages for screen readers such as VoiceOver and TalkBack; key confirmation sheets move focus to their heading when opened; and interface animations respect the system reduce-motion setting where supported.
  • Subscription purchase, restore, and cancellation use Apple’s and Google’s own store screens, which follow each platform’s accessibility features.

Known Limitations

Boba Globe includes a visual 3D globe, WebGL rendering, map animations, video export workflows, route previews, and third-party payment or route-provider surfaces. Some highly visual editor features, including the animated globe preview and exported videos, may not have a full non-visual equivalent yet; exported videos are silent visual animations without audio description. Stripe-hosted checkout and billing pages, Geoapify, BusMaps, Google Maps Platform, Flightradar24, browser APIs, operating systems, and assistive technologies may also affect the experience outside Boba Globe's direct control.

We do not treat an automated accessibility scan as proof that the service is accessible. Manual keyboard, screen reader, zoom, contrast, motion, and form-flow checks are still required before final accessibility signoff.

Market And Legal Review

Accessibility laws and service obligations vary by market. The European Accessibility Act has applied to many consumer e-commerce services in the EU since June 28, 2025, and harmonised standard EN 301 549 references WCAG for web and mobile app content. Because Boba Globe is available through app stores in many countries, we review whether this statement, the support channel, the conformance target, and manual test evidence need to be updated for those markets, including EU e-commerce accessibility rules, public-sector procurement rules, or contract accessibility commitments.

Feedback And Support

If you have trouble using Boba Globe because of an accessibility issue, send feedback from Account in the app or email [email protected]. Please include the page or feature, the assistive technology or browser you use if relevant, what you were trying to do, and what happened. We will review accessibility reports and work on reasonable fixes or alternatives.

Review Process

We review this statement when Boba Globe adds major public pages, account flows, checkout flows, editor controls, video export features, third-party embeds, or material visual interaction changes. We also review it when accessibility laws, standards, or legal guidance change.