Methodology & Sources

How the Code Tables Are Verified

The Morse code table on this site follows the International Morse Code standard maintained by the International Telecommunication Union (ITU-R M.1677), the same standard used by amateur radio operators, maritime services and aviation worldwide. It is not an Americanized or simplified variant. The reference charts and the live translator do read from two separate tables in the site's code, so rather than ask you to take their agreement on trust, a dedicated check compares them character by character on every single build and fails the build outright the moment they disagree. A per-character page and the translator therefore cannot drift apart unnoticed — the agreement is verified every time the site is rebuilt, not assumed. The NATO phonetic alphabet follows the ICAO spelling alphabet as standardized in ICAO Annex 10, cross-checked against the official ICAO documentation rather than reconstructed from memory or from other secondary sites. Braille pages use Grade 1 (uncontracted) English braille and the Unicode Braille Patterns block (U+2800–U+28FF), so the dot pattern shown on the page is a real, standard Unicode character rather than a custom image.

How the History Pages Are Researched

The History section draws on primary and well-documented secondary sources: ITU and ICAO official records and standards documents, published histories of telegraphy (including Samuel Morse and Alfred Vail's own correspondence and patent records where available), and well-attested accounts of specific events like the 1906 Berlin International Radiotelegraph Convention that adopted SOS, and the documented final commercial Morse transmissions of the late 1990s. Where a detail is genuinely disputed or under-documented — and in a field this old, some details are — the page says so rather than presenting a tidied-up version as settled fact.

What We Don't Do

• We don't invent a code or spelling to fill a gap. If a punctuation mark or symbol has no widely-agreed Morse representation, it isn't listed as though it does.
• We don't present the braille reference pages as a substitute for real tactile braille instruction — they're a sighted-learning aid showing the standard dot patterns, explicitly framed that way.
• We don't backfill a tidy origin story where the real history is genuinely uncertain or disputed among historians.

How Word Counts and Depth Are Decided

Not every page on this site is held to the same depth, and that's deliberate rather than inconsistent. A handful of characters and letters — E, T, O and Q in Morse, and words like Charlie and Alfa in the NATO alphabet — have real, well-documented, individually interesting histories, and those pages get full treatment. The remaining letters, digits and punctuation marks don't each carry a unique origin story; forcing one onto every single character would mean inventing padding rather than reporting fact, which is exactly the kind of thin, templated content this site is trying not to be. Those pages are intentionally shorter and data-focused: the accurate code, a genuine memory aid, and clear cross-links to related characters, rather than a manufactured paragraph of filler history.

Independent Verification, Not a Single Source Chain

Where possible, a claim is checked against more than one independent source rather than trusted from a single reference — official ITU or ICAO documentation cross-checked against published, peer-reviewed or well-cited historical accounts, rather than one Wikipedia-style summary copied and lightly rephrased. This matters most for the historical narrative pages, where a single popular but inaccurate retelling (like the SOS-as-acronym myth) can spread across dozens of sites that all cited each other rather than a primary source.

Corrections

These are old, well-documented standards, but transcription errors happen. If you find a code, spelling or historical detail that looks wrong, the Contact page explains how to flag it, and corrections are treated as a priority rather than filed away, since a wrong code on a reference chart is a genuinely worse failure than a wrong code nowhere at all.