Start Free Trial

Legal

Accessibility Statement

Last updated August 30, 2026

WellAudio LLC (“WellAudio,” “we,” “our,” or “us”) wants everyone to be able to use our website and app, regardless of ability or the technology they use to browse. This statement describes where we stand today, what we know is not yet working, and how to reach a person if something blocks you.

1. Our Commitment

WellAudio LLC is committed to making our website and mobile application usable by as many people as possible, including people with disabilities. Accessibility is not a feature we finished. It is something we work on continuously, and this page reflects our current honest position rather than an aspiration.

2. Conformance Status

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. WellAudio aims to conform to WCAG 2.1 Level AA.

Current status: partially conformant

Partially conformant means some parts of the content do not yet fully conform to WCAG 2.1 Level AA. We have not commissioned a formal third-party audit or published a VPAT. Our status is based on internal self-evaluation, and we describe the specific gaps we know about in section 4 rather than leaving them unstated.

3. Measures We Take

Semantic, keyboard-navigable markup

Our pages are built with semantic HTML and standard interactive elements, so they can be navigated with a keyboard and interpreted by screen readers. The page language is declared so assistive technology announces content with the correct pronunciation.

Reduced motion

Our site uses animation for emphasis. Where animation could cause discomfort, we honor the prefers-reduced-motion setting in your operating system and suppress the effect. This includes celebratory animations, which are disabled entirely rather than merely shortened.

Text alternatives

Meaningful images carry descriptive alternative text, and images that are purely decorative are marked so screen readers skip them instead of announcing noise. Icon-only controls carry accessible names.

Responsive and zoom tolerant

Layouts use relative units and adapt to different viewport sizes and text scaling, so content remains readable when zoomed or viewed at larger text sizes.

Consent without dark patterns

Our cookie consent controls present accept and decline options with equal prominence, and analytics tracking runs only after explicit consent.

4. Known Limitations

We would rather tell you what is not working than let you discover it. The following are known gaps we are actively working to resolve:

No skip navigation link

Our pages do not yet provide a skip to main content link, so keyboard and screen reader users must move through the navigation on every page load. This is a WCAG 2.4.1 issue and is on our roadmap.

Low contrast secondary text

Some secondary and supporting text, such as timestamps and helper copy, is rendered at a low opacity against our dark background and falls below the WCAG 4.5:1 contrast requirement for body text. Primary content meets the threshold, but we are revising the muted text values.

Motion on the home page

Our home page uses entrance animation and a parallax effect. We honor reduced motion preferences in most components, but coverage is not yet complete across every animated element.

Third-party interfaces

Some flows hand off to services we do not control, including Stripe for payment and billing management, and the Apple App Store and Google Play for mobile subscriptions. The accessibility of those interfaces is governed by those providers. If you encounter a barrier there, contact us and we will help you complete the task another way.

Audio content

Our core product is instrumental audio engineered around specific frequencies, and it contains no speech or dialogue, so captions and transcripts are generally not applicable. Where we publish spoken or narrated material, we work to provide text alternatives.

5. Compatibility

Our website is designed to be compatible with current versions of major browsers, including Chrome, Safari, Firefox, and Edge, used together with the assistive technologies built into your operating system, such as VoiceOver on macOS and iOS, TalkBack on Android, and NVDA or Narrator on Windows. Our site may not work reliably with browsers older than three major versions.

6. Technical Specifications

Accessibility of our website relies on HTML, CSS, JavaScript, WAI-ARIA, and SVG. These technologies are relied upon for conformance with the accessibility standards described above. JavaScript is required for some interactive features, including account management and checkout.

7. Feedback and Reporting a Barrier

If you encounter an accessibility barrier on our website or in our app, please tell us. Your reports help us find problems our own testing missed, and we treat them as bugs rather than suggestions.

How to reach us

Email hello@wellaudio.com with the subject line Accessibility. Please describe the page or screen, what you were trying to do, and the browser, device, and assistive technology you were using if you know them. We aim to acknowledge accessibility reports within 5 business days and will tell you our plan and timeline for a fix.

If you need help completing something

If an accessibility barrier is preventing you from signing up, managing your subscription, or cancelling, contact us at the address above and we will complete the request on your behalf. You should never have to keep paying for a service because a barrier prevented you from cancelling it.

8. Assessment Approach

WellAudio assessed the accessibility of this website by internal self-evaluation, including manual keyboard navigation review, code review of markup and contrast values, and review against the WCAG 2.1 Level AA success criteria. We have not engaged an external accessibility auditor. If that changes, we will update this page and state who performed the evaluation and when.

9. Changes to This Statement

We review this statement when we make significant changes to our website or app, and at minimum annually. When we resolve a limitation listed in section 4, we remove it here rather than leaving the disclosure in place.