Accessibility Statement

VocalRangeCalculator.com is committed to making its tools and educational content as usable as reasonably possible for people with different abilities, devices, and ways of interacting with the web.

Because the site includes microphone-based and real-time audio tools, some accessibility challenges are specific to voice input, dynamic pitch detection, charts, and other interactive features. We aim to improve those experiences over time and to provide practical alternatives where possible.

Our Accessibility Commitment

We aim to improve VocalRangeCalculator.com toward WCAG 2.2 Level AA.

This is an ongoing goal rather than a claim that every page, tool, or interaction currently meets every WCAG 2.2 success criterion.

Some parts of the site, particularly custom voice tools and rapidly updating visual results, may still have accessibility limitations.

Measures We Aim to Use

Across the site, we aim to support accessibility through measures such as:

  • clear page titles and headings
  • readable text and spacing
  • sufficient contrast
  • meaningful link text
  • descriptive text alternatives for important images
  • keyboard-accessible navigation and controls where practical
  • visible focus states
  • labelled form fields and buttons
  • responsive layouts that work at different screen sizes and zoom levels
  • text-based results where possible
  • avoiding reliance on color alone to communicate important information
  • avoiding unnecessary autoplaying audio

We continue to review these areas as pages and tools are updated.

Accessibility of Voice and Microphone Tools

Several tools on VocalRangeCalculator.com rely on microphone input or audible voice production.

This can create barriers for users who:

  • cannot vocalize
  • cannot sustain a note
  • have a speech or voice disability
  • cannot or prefer not to grant microphone permission
  • use a device without a suitable microphone
  • experience difficulty controlling pitch or volume

Some limitations are inherent to tools whose purpose is to analyze a live vocal signal. Where practical, we aim to reduce those barriers through alternatives such as manual input, numeric input, text results, or supporting educational content.

Microphone-based results should not be considered a requirement for accessing the site’s general educational information.

Manual and Text-Based Alternatives

Some site features can be used without live microphone input.

For example, certain tools accept manual notes or numeric values, and the main vocal range experience may offer manual entry where available.

The Frequency to Note tool converts a frequency value entered by the user rather than requiring live voice detection.

You can browse the current set of options on our Tools page.

Where a microphone-based tool does not provide an equivalent non-audio interaction, related educational pages may still provide useful information in standard text format.

Known Limitations

We want to be transparent about areas that may not yet provide an equivalent experience for every user.

Real-Time Pitch Updates

Pitch detectors and similar tools can update values rapidly while a person is singing.

These changes may be difficult for some screen readers or other assistive technologies to announce meaningfully in real time.

Where possible, stable results and summaries should be presented as text after or during the interaction, but real-time dynamic information may still be less accessible than ordinary page content.

Charts and Visual Results

Some tools use keyboards, range diagrams, charts, or visual indicators to show detected notes or classifications.

We aim to provide text information alongside important visual results and avoid using color as the only way to communicate meaning.

However, some complex visual relationships may not yet have a fully equivalent non-visual presentation.

Voice-Dependent Interactions

A tool designed to analyze a voice cannot always provide an identical experience to someone who cannot produce or capture the required sound.

Where a suitable manual or text-based alternative is available, we aim to make it discoverable.

Custom Tool Controls

Interactive tools may contain custom controls and dynamic elements that behave differently from standard article content.

We aim to use semantic controls, labels, logical focus order, and keyboard interaction where practical, but some tool interfaces may still require further accessibility improvements.

If you encounter a control that cannot be reached or operated with your keyboard or assistive technology, please report it to us.

Screen Readers and Keyboard Navigation

We aim for core navigation, links, forms, and tool controls to work with keyboard-only interaction and common assistive technologies.

However, compatibility can vary by:

  • browser
  • operating system
  • screen reader
  • input method
  • individual tool implementation

For the best chance of compatibility, use a current version of a major browser together with an up-to-date operating system and assistive technology.

If a particular tool does not work as expected, our Troubleshooting guide may help identify browser, microphone, or permission issues.

Hearing Accessibility

Where possible, information produced by a voice or pitch tool should be presented visually or as text rather than requiring users to hear an audio cue.

The site does not intentionally require users to listen to autoplaying media in order to access ordinary educational content.

If an audio-dependent feature does not provide a useful non-audio alternative, we consider that an area for further improvement.

Zoom, Reflow, and Responsive Use

We aim to make site content readable across desktop, tablet, and mobile devices and usable with browser zoom.

Custom tool layouts can be more challenging than ordinary text pages, so users who encounter clipping, overlapping controls, or unreadable results at higher zoom levels are encouraged to report the affected page.

Accessibility and Voice Safety

Accessibility also includes avoiding interactions that pressure users to perform beyond what is comfortable.

You should not need to force an extreme high or low note simply to make a tool produce a result.

If singing causes pain, sharp discomfort, strong pressure, or unusual voice changes, stop the test.

For additional information about tool behavior and limitations, see How It Works.

Accessibility Feedback

We welcome feedback about accessibility problems.

If you have difficulty using a page, tool, form, control, or piece of content, please contact us through the Contact Us page.

When possible, include:

  • the page or tool URL
  • a short description of the problem
  • your device and browser
  • the assistive technology you were using, if relevant
  • what you expected to happen
  • what happened instead

You do not need to provide medical or disability details in order to report an accessibility issue.

We review accessibility feedback and aim to respond within a reasonable period.

Ongoing Improvements

Accessibility is not a one-time project.

We may review and update this statement when:

  • new tools are introduced
  • existing tools are redesigned
  • accessibility issues are reported
  • browser or assistive-technology behavior changes
  • our design system changes
  • relevant accessibility guidance evolves

We aim to prioritize improvements that affect core navigation, access to information, form controls, and the ability to understand tool results.

For the accessibility standard we are working toward, you can review the W3C’s WCAG 2.2 guidance.

Related Help and Information

You may also find these pages useful:

If you identify an accessibility problem that is not covered here, please contact us so it can be reviewed.

Scroll to Top