Effective May 2, 2026

Accessibility Statement

iPitch is built to be usable by as many singers as possible, including people who rely on assistive technologies. This page describes the standards we aim for, where we currently fall short, and how to tell us about a problem.

1. Our commitment

We target WCAG 2.1 Level AA conformance across the marketing site and the in-app experience. We use the system design tokens for color contrast, semantic HTML for structure, ARIA labels on icon-only controls, and focus-visible outlines on every interactive element. Components are built on the Radix UI primitive layer, which ships keyboard and screen-reader semantics by default.

2. What works well

  • Full keyboard navigation across the marketing site and dashboard.
  • Screen-reader labels on all icon-only buttons and form controls.
  • Color-contrast ratios meet AA against both surface and background tokens.
  • No motion-only feedback — every animation has a static fallback.
  • Tap targets on primary mobile actions are at least 44×44 CSS pixels.

3. Known limitations

  • The real-time pitch coach and Voice Lab require microphone access. Browser microphone permission prompts cannot be triggered by a keyboard shortcut alone — a pointer or touch activation is needed the first time per origin.
  • The Backing Track Studio's record button uses a visual ring + pulse to indicate recording. Screen-reader users receive an aria-live announcement, but the pulse itself is decorative.
  • Some chart and waveform visualisations are presented as canvas drawings. Numeric summaries are provided alongside them for assistive-tech users; the canvas itself is marked aria-hidden.
  • Auto-playing audio previews respect prefers-reduced-motion for ambient visuals, but the backing track itself still plays on user-initiated playback only.

4. Browsers and assistive technology

We test against current versions of Chrome, Safari, Firefox, and Edge on macOS, Windows, iOS, and Android. We test screen-reader flows with VoiceOver (macOS / iOS) and NVDA (Windows). If you use a different combination and something doesn't work, please let us know — we treat assistive-tech bugs as functional regressions.

5. How to report an issue

Email noetica@noeticaapps.com with subject line "Accessibility". Please include the page URL, the browser and assistive technology you were using, and a short description of what you expected versus what happened. We aim to respond within 5 business days and to fix critical issues (anything that blocks access to a feature) in the next release cycle.

6. Formal complaints

If we don't resolve an accessibility issue to your satisfaction, you can raise it with the relevant national authority in your country — for example, the U.S. Department of Justice (ADA), the UK's Equality Advisory Support Service, or your national equivalent body.

7. Review date

This statement was last reviewed on May 2, 2026 and applies to https://noeticaapps.com and the iPitch web application.

This document contains placeholders in [BRACKETS] that must be replaced with your real legal entity, address, and contact information before publishing. It is a starting point, not legal advice — have a lawyer review before launch, especially the subscription, audio recording, and data-handling sections.