Tarosyn Legal

Accessibility Statement

Last updated May 31, 2026

Work in progress. We are actively improving accessibility across Tarosyn. This statement reflects our current status honestly — not where we aspire to be, but where we are today.

Tarosyn is committed to making our app and website accessible to as many people as possible, including those who rely on assistive technologies. Spiritual exploration should not require perfect vision, hearing, or motor control. We recognise there is meaningful work ahead of us and are taking steps to improve.

1. target standard

We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. We do not currently claim full conformance — this statement is an honest commitment to progress rather than a declaration of complete compliance.

Target: WCAG 2.1 Level AA (working toward) Platforms in scope: web app (tarosyn.app, tarosyn.com), iOS app, Android app Evaluation approach: ongoing internal review; formal third-party audit planned

2. features supported

The following accessibility features are currently in place or actively maintained:

Semantic HTML5 elements used throughout the web app (landmarks, headings, lists) Interactive controls include descriptive ARIA labels and roles where native semantics are insufficient Focus-visible styles are preserved — we do not suppress the browser's default focus ring globally Colour contrast ratios for primary text content meet or approach the WCAG AA 4.5:1 threshold on our dark background Text content can be resized up to 200% without loss of information or functionality in modern browsers Tap/click targets are sized to at least 44 × 44 CSS pixels on mobile surfaces Decorative images include empty alt attributes; meaningful images include descriptive alt text The app does not auto-play audio or video with sound without user interaction Animated elements respect the prefers-reduced-motion media query where implemented

3. known limitations

We are aware of the following areas where accessibility is incomplete. We are working to address these over time:

Some custom interactive components (card swipe gestures, drag-and-drop) do not yet have full keyboard-navigable equivalents Animated tarot card transitions and parallax effects may not fully respect prefers-reduced-motion in all surfaces Certain complex SVG illustrations (birth charts, constellation views) lack comprehensive text alternatives Screen-reader announcements for real-time content updates (live session feeds, circle messages) are inconsistent Third-party embedded content (social sharing previews, Stripe checkout) is outside our direct control and may have its own accessibility gaps Some modal dialogs may not correctly trap focus on all screen-reader / browser combinations

We prioritise addressing limitations that affect core functionality first — reading results, navigation, account management, and payments.

4. assistive technology compatibility

Tarosyn is designed to work with common assistive technologies. We test primarily with:

VoiceOver on iOS and macOS (Safari) TalkBack on Android (Chrome) NVDA and JAWS on Windows (Chrome, Firefox) — coverage is more limited here Keyboard-only navigation on desktop browsers

If you encounter issues with a specific assistive technology not listed above, please let us know — your report helps us prioritise testing.

5. our ongoing commitment

Accessibility is included in our design and engineering review process for new features We aim to add keyboard navigation equivalents for gesture-based interactions as features mature We plan to commission a formal WCAG 2.1 AA audit and publish results We review and update this statement whenever material improvements or known regressions are identified report an accessibility barrier

If something prevents you from using Tarosyn, tell us here. Your device and browser details are attached automatically so you don't have to look them up. We aim to respond within 5 business days.

Your email Assistive technology you use None / not sure VoiceOver (iOS / macOS) TalkBack (Android) NVDA (Windows) JAWS (Windows) Narrator (Windows) Voice Control / voice dictation Switch control Screen magnifier / zoom Keyboard-only navigation None / not sure Other (described below) Page or screen where it happened (optional) Describe the barrier Send report prefer to email?

The form above is the quickest way to reach us, but if you'd rather email — or need content in an alternative format — write to [email protected]. Either way, we will do our best to respond within 5 business days. It helps if you include:

A description of the barrier or difficulty you encountered The URL or feature name where the issue occurred The assistive technology and browser or app version you were using Any workaround you needed to take (if any)

We welcome feedback from users with disabilities — it is one of the most effective ways for us to identify and fix gaps.

changes to this statement

We will update this statement as our accessibility programme progresses. Material changes — including newly discovered limitations or completed improvements — will be reflected in the "Last Updated" date above. For questions, contact [email protected].

Questions? [email protected]