Legal

Accessibility Statement

Effective 2026-06-12

Trackora LLC (Michigan) — operator of the app branded "Aspra"

Contact: accessibility@aspra.app

1. Our Commitment

Aspra is committed to providing a service that is accessible to the widest possible audience, including people with disabilities. We design and develop with accessibility as a first-order concern, not an afterthought. We acknowledge that we are not perfect, and we welcome feedback that helps us close gaps.

2. Compliance Standard

We aim to meet or exceed the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA for both our iOS app and our websites at aspra.app and aspra.app. Where iOS-specific accessibility patterns differ from WCAG's web framing, we follow Apple's Human Interface Guidelines for accessibility as the operational reference.

We also aim to comply with:

  • Americans with Disabilities Act (ADA) Title III as applied to commercial mobile applications.
  • California Unruh Civil Rights Act.
  • Section 508 of the Rehabilitation Act (US federal accessibility standard) where applicable.
  • EU Accessibility Act 2025 / European Accessibility Directive (2019/882) for users in the European Union.
  • UK Equality Act 2010 for users in the United Kingdom.

3. iOS App Accessibility Features

The Aspra iOS app supports the following accessibility features:

VoiceOver. All interactive elements have accessible labels. Action rows, goal cards, milestone entries, journal entries, and paywall content are reachable and operable via VoiceOver. Chart elements (the home constellation and goal-detail progress chart) include accessible summaries that convey the underlying data without requiring visual interpretation.

Dynamic Type. Text scales with the user's iOS Display & Text Size preference up to and including the largest accessibility size (AX5). The app's typography ladder is built on iOS's scalable text APIs.

Reduce Motion. When enabled, the app suppresses non-essential motion: chart point appearances are static, the constellation background stars do not breathe, the rotating quote on the Home screen shows only the first quote without rotation, the splash sequence skips its glow pulse. Functional motion necessary to communicate state is preserved.

Contrast. Primary text (parchment #EAE2D0 on canvas #04070F) meets WCAG AAA contrast at approximately 14.6:1. Secondary text meets AAA at approximately 10.8:1. Tertiary text meets AAA at approximately 7.6:1. The brand never relies on color alone to convey meaning — every state (active, complete, error, disabled) is also signaled by shape, position, or typography weight.

No color-only signaling. Completed actions are not communicated by color change alone — the action title gains a strikethrough and the leading dot fills with the signal accent. Errors are not communicated by red — they appear as inline Color.parchment Presence.secondary text. There is no red anywhere in the app.

Haptic feedback. Action completion, milestone acknowledgment, pair connection, and major navigation events emit calibrated haptic feedback. Haptics are layered on top of visual confirmation, never as a replacement.

Captions and audio. The app does not contain audio or video media at this time. If we add audio in the future, captions and transcripts will be provided.

Keyboard navigation (iPad). The app inherits standard iOS keyboard navigation. iPad-optimized layouts are deferred to a future release; in the current release, iPad runs the iPhone layout stretched, which preserves accessibility but does not optimize for it.

4. Known Limitations

We are transparent about gaps we are aware of:

  • iPad-optimized layout. The current release uses the iPhone layout stretched on iPad. Some elements are larger than necessary and the layout does not take full advantage of iPad screen real estate. A native iPad layout is planned for a future release.
  • Processing-screen announcement. The onboarding "Generating your plan" screen does not yet announce its processing state to VoiceOver, so a VoiceOver user may not hear that the screen is working. A live-region announcement on entry and completion is planned.
  • VoiceOver chart navigation. The constellation charts on Home and Goal Detail present an aggregated summary to VoiceOver, but the most-recent data point (shown visually as a glow) does not yet expose its date and value as a text label, and the charts do not yet support point-by-point navigation. Both are on the roadmap.
  • Custom toggle values. Some custom toggles (day-of-week selection in setup, shared-goal toggles) may not yet announce their on/off state to VoiceOver. Verification and remediation are pending.
  • Time-commitment dial. The custom dial/slider in onboarding has not been fully VoiceOver-tested and may not yet support swipe-to-adjust without a touch drag.
  • Onboarding screens. Several onboarding screens still require a live VoiceOver and Dynamic Type (largest accessibility size) verification pass. The underlying typography uses scalable system fonts and does not hard-cap font sizes, but correct rendering at every size is not yet confirmed on-device.
  • Reduce Transparency. The app respects Reduce Motion but does not yet check the Reduce Transparency setting. The interface uses minimal transparency overall, so the impact is small, but a full audit is planned.

This list will be updated as we audit and remediate. If you encounter an issue not listed here, please contact us.

5. Feedback and Remediation

If you encounter an accessibility barrier, we want to know. Email accessibility@aspra.app with:

  • A description of the barrier.
  • The device and iOS version you are using.
  • The accessibility feature you are using (VoiceOver, Dynamic Type, Reduce Motion, etc.).
  • The screen or feature where the barrier occurs.

We aim to respond to accessibility reports within 5 business days. We communicate a remediation timeline case by case, prioritizing barriers that prevent core use of the Service. Workarounds, where available, will be communicated in our initial response.

6. Third-Party Content

The Service uses content from third parties including Google Gemini (for AI plan generation), Supabase (for data sync), and Apple (App Store In-App Purchase) and Stripe (for payment). These third parties have their own accessibility policies and may have features we do not directly control. We work to ensure third-party integrations do not break our accessibility commitments and we report issues we find to those providers.

7. Date of Last Review

This statement was last reviewed on 2026-06-10. We review and update at least annually, or sooner when material accessibility-relevant changes ship.

8. Contact

Accessibility: accessibility@aspra.app General legal inquiries: legal@aspra.app Postal address: available on request via accessibility@aspra.app