Contact

Email is the only channel: hello@audiotesttool.com. Replies usually take a couple of working days.

Reporting a problem with a test

Audio behaviour varies more between browsers and devices than almost anything else on the web, so a bug report is only actionable with a few details. Please include:

The page you were on, and which step or control misbehaved.
Your browser and its version, and the operating system.
The output device: laptop speakers, wired headphones, a named Bluetooth set, a USB interface.
What you expected to happen and what happened instead.

One check first, because it resolves a good share of reports: if no sound plays at all, confirm the browser tab is not muted and that the system output is the device you think it is. The no-sound checklist runs through the rest in order.

Suggesting a tool

Suggestions are welcome, particularly for tests that exist as an app but not as a web page. Tell us what you were trying to find out rather than what feature you want — the underlying question is usually the more useful thing, and it often has a simpler answer than the feature would.

Embedding a tool

The tests can be embedded in your own page, free and without attribution requirements. The embed page has the snippet and the sizing. If you need a different default configuration for your audience, ask.

Corrections

If a guide states something inaccurate, please point at the specific sentence and, where you can, what it should say. Corrections are made quickly and the review date at the foot of the page is updated when they are.

What we cannot help with