We want everyone to be able to detect pitch, convert notes, and practice confidently. This statement explains our standards, what we support today, known limitations, and how to get help. Most audio processing on PitchDetector.com happens locally in your browser; no audio is uploaded or stored. See our Privacy Policy: https://pitchdetector.com/privacy-policy/

Our commitment & what this covers

PitchDetector.com aims to meet WCAG 2.2 Level AA accessibility guidelines across our core experiences:

This statement applies to pages hosted on pitchdetector.com. Any third-party services we link to maintain their own accessibility policies and practices.

Standards & design principles we follow

  • Conformance target: WCAG 2.2 Level AA; we adopt AAA techniques where practical (plain language, predictable navigation, generous touch targets).
  • Semantics & announcements: Clear labels, roles, and ARIA only where needed. Live readouts for Note, Frequency (Hz), and ±cents are announced politely to assistive technology.
  • Keyboard first: All controls (Start/Stop, A4 440/442, presets, inputs) are reachable and operable with keyboard alone; focus order is logical and a visible focus indicator is maintained.
  • Contrast & color use: Text contrast is ≥ 4.5:1. Status is never conveyed by color alone—numeric ±cents and Hz are always visible.
  • Responsive & zoom: Content remains usable at 200–400% zoom and with system font scaling without loss of functionality.
  • Privacy & latency: Processing is local/on-device to protect privacy and reduce latency (no audio uploads).
  • Consistency: Headings, buttons, and controls use consistent wording and placement across the site.

Using our tools with assistive technology

Screen readers

  • Live status for Note, Frequency (Hz), and ±cents updates without reloading and is announced politely (so screen readers aren’t overwhelmed).
  • Readouts are labeled to communicate context (e.g., “Cents offset” rather than a generic number).

Keyboard navigation

  • Primary actions (Start/Stop), calibration (A4 = 440/442), presets (Voice, instrument), and inputs are reachable in a logical order.
  • Press Enter or Space to activate controls. Escape routes are provided to leave or stop interactive components.

Reduced motion and visual alternatives

  • The animated meter is subtle and designed below known seizure thresholds.
  • Users can rely entirely on numeric ±cents and Hz readouts if motion is distracting.

Browsers, devices, and assistive tech we test

We aim for robust, cross-platform support and routinely check:

  • Desktop: Chrome, Edge, Safari, and Firefox (current versions) on macOS and Windows.
  • Mobile: Safari on iOS and Chrome on Android. (Some mobile browsers require a user gesture—press Start—before microphone access is permitted.)
  • Screen readers: VoiceOver (macOS/iOS), NVDA and JAWS (Windows), TalkBack (Android).
  • Input devices: Keyboard-only navigation and external microphones/headsets.

Known limitations & practical workarounds

We’re actively improving; your feedback helps us prioritize.

  1. Mobile mic permission prompts (especially iOS/Safari): Some sessions require granting permission each time by design. After allowing, press Start again.
  2. Polyphonic input (chords/ensembles): The detector is monophonic; test one voice or instrument at a time.
  3. Noisy or reverberant rooms: Background noise and strong reflections can destabilize readings. Use a quieter room, move closer (20–30 cm), and angle the mic 15–30° off-axis.
  4. High zoom (≥400%) on small screens: Content remains functional but may require some horizontal scrolling.
  5. Reduced-motion preferences: If visual motion is uncomfortable, focus on the numeric ±cents and Hz values.
  6. Browser/device variability: Sample-rate handling and input gain differ across devices; if results seem inconsistent, try a second browser or an external mic.

For quick fixes and setup tips, see FAQ: https://pitchdetector.com/faq/

Practical guidance for better results (accessibility & accuracy)

  • Choose a quiet room; close doors/windows and reduce fans/AC.
  • Keep the mic 20–30 cm away and 15–30° off-axis to reduce plosives.
  • Use a single steady vowel (“ah/ee/oo”) at a comfortable volume for 3–5 seconds.
  • If the meter “flickers,” hold your note steady and check mic distance/angle; consider an external mic or headset.
  • Keyboard users: Tab/Shift+Tab moves focus; Enter/Space activates controls.

How we test & improve

We combine automated and manual testing on real devices:

  • Automated audits: heading/landmark structure, label associations, and contrast checks.
  • Keyboard reviews: reachability, focus order and visibility, no traps, clear escape routes.
  • Screen-reader spot checks: confirm live announcements are meaningful and not noisy; ensure all form fields and buttons are labeled.
  • Real-world trials: iOS/Android permission flows, offline/slow network states, and high-zoom scenarios.

We track issues and prioritize fixes that block access. Significant updates are reflected on this page.

Request assistance or alternative formats

If you experience an accessibility barrier, need content in a different format, or want to report an issue:

Response time: We aim to reply within 3 business days and propose a resolution or interim workaround within 10 business days.

Legal & compliance note

We strive for WCAG 2.2 Level AA alignment and continuous improvement as standards and browsers evolve. If you believe we are not meeting requirements, please contact us: https://pitchdetector.com/contact-us/ — we will investigate promptly and work toward resolution.

Scroll to Top