Contact Us

Tell us which page you used and which direction you were working in. Include a short example with the expected and actual output. For a Morse input issue, preserve the spaces, line breaks, and slashes in the sample. Even one missing space can turn two valid characters into an invalid group or a different character. If you found a mismatch in the chart, identify the exact letter, number, or punctuation mark and the pattern you believe it should use.

A short message such as HELLO WORLD can make it easier to check whether a problem occurs with a specific character, a word boundary, or the whole editor. If you were translating a private message, try replacing it with a small neutral example that reproduces the same issue. Leave any information you want to keep private out of the email and out of any screenshots or share links.

Describe whether the issue concerns the Play control, a downloaded recording, an uploaded file, or a live microphone. Include the browser and operating system, the format of any file, and the speed and tone settings you were using. Tell us if the signal plays through your device speakers or through a different output such as headphones. If the Play button changes state but you hear silence, the device output and volume settings are useful details.

For a decoder report, note whether the tool found a pitch, displayed an energy trace, and showed any uncertainty or clipping. A test file made with the generator gives a repeatable example with a known answer. You can report that example using its text, speed, tone, and file format without sending any recording from a microphone or radio receiver.

Include the page address and the label of the control involved. Describe what you were trying to do and what happened when you used the keyboard, touch, a mouse, or assistive technology. If the problem depends on zoom, viewport width, or orientation, approximate values are enough. A description such as “focus returned to the page after closing the menu, but I could not find the menu button again” identifies a specific interaction to reproduce.

You can also describe a reading issue, such as a status that is not announced, text that is hard to read, or a control that is difficult to reach. Include the browser and assistive technology versions when you know them. Screenshots can help with visible layout issues, and a short written description is useful for anything a screenshot cannot capture.

Read the Privacy Policy for how the site handles messages, recordings, lesson progress, and usage analytics. You can reset lesson progress from the learning page and clear practice history from the practice trainer. Your browser settings can also clear cookies and cached offline pages.

If your question concerns an email you already sent, share enough context to identify it, such as the date and general subject. Avoid including account passwords, device credentials, or third-party details. For a local storage issue, the browser and the feature you used are usually more useful than a full export of browser data.

Name the page or tool, then describe the change in terms of what you want to accomplish. For example, explain which group is hard to identify in an audio trace or which part of a practice session you would like to review. If you are proposing a correction to the written reference, include the current wording or example and a link to an authoritative source when you have one.

If an issue occurred after using the site offline, say whether it also happens after reconnecting and refreshing. Include any visible error or status message exactly if you can. A single repeatable sequence of steps can help distinguish an interrupted download, a browser permission decision, and a problem in the tool itself. Messages sent to a configured address are reviewed through email, where replies depend on availability.