Braille is one of the great encodings: a full writing system built from a six-dot grid, designed two centuries ago around the resolution of a human fingertip, and now carried inside Unicode like any other script. Translating English text into Braille characters is something a web page can do instantly, and understanding what the translation does, and where it honestly stops, makes the output far more useful. This guide covers the cell, the alphabet, the grade system, and how our free English to Braille translator handles it all in your browser.
In this guide
The cell: six dots, sixty-four patterns
A Braille cell is a grid of six dot positions, two columns of three, numbered 1-2-3 down the left and 4-5-6 down the right. Each position is raised or flat, which yields 64 possible patterns including the empty cell that serves as the space. Sixty-four is not many for a writing system that needs letters, digits, punctuation and formatting, and that scarcity explains most of Braille’s design: symbols get reused, and special prefix cells switch the meaning of whatever follows. The dimensions of the cell itself are remarkably standardized worldwide, because they encode a biological constant, the area a fingertip can read in one touch.
The alphabet, and the trick for numbers
The letters a through j use only the top four dot positions: a is dot 1 (⠁), b is dots 1-2 (⠃), c is dots 1-4 (⠉). The next ten letters, k through t, are the same ten shapes with dot 3 added; u through z (except w) add dots 3 and 6. The system is a spiral, ten shapes recycled three times, which is why Braille is learnable in weeks. Numbers showcase the prefix trick: there are no separate digit symbols; instead the number sign (dots 3-4-5-6, ⠼) declares that the following a-j letters mean 1 through 0, so ⠼⠁⠃ reads as 12. One historical footnote hides in the alphabet: w sits outside the pattern because the system was designed for French, which barely used the letter when Louis Braille built the code.
Grade 1 and Grade 2: spelling vs shorthand
Grade 1 Braille is letter-for-letter transcription: every character of print becomes one cell, unambiguous and bulky. Grade 2 is the contracted form that fluent readers actually use: common words get single cells (the, and, for), frequent letter groups get dedicated signs (sh, ing, tion), and the same 64 patterns take on context-dependent meanings. The compression is substantial, shrinking documents by roughly a quarter, which matters enormously when embossed pages are thick and slow to produce. The cost is complexity: Grade 2 contraction rules fill books, interact with word boundaries, and differ between English dialect standards. Browser translators, including ours, work in Grade 1, which is the honest scope for instant translation: exact, reversible, and correct for learning, labeling and display purposes.
Braille in Unicode: the U+2800 block
Unicode reserves a 256-character block starting at U+2800 for Braille patterns: 256 rather than 64 because the block covers the eight-dot variant used in some technical and computer Braille, with the classic six-dot patterns as the subset leaving the bottom pair flat. The block’s layout is elegant: each dot maps to one bit of the character’s number, so the pattern is computable from the code point and back, an encoding inside the encoding. This is what makes web Braille work: translated output is ordinary Unicode text, copyable, searchable and stylable like any string, following the same byte rules as every other script in the text encoding guide. A screen’s flat glyphs are a visual representation, of course; the dots become Braille proper on an embosser or a refreshable display.
What a translator can and cannot promise
Letter-level translation is mechanical and safe, the same kind of pure character mapping as Morse code conversion, whose dots-and-dashes system is unpacked in the Morse guide. What no instant tool should promise is production-ready Grade 2 transcription of long documents: contraction rules, formatting conventions for page layout, and the requirements of official accessible-document standards are a professional transcriber’s territory. The practical division of labor: use the translator for learning the system, checking a label or sign, generating display text and exploring how the encoding works; use certified transcription for published material that blind readers will rely on. Knowing where the line sits is part of taking the script seriously.
Frequently asked questions
Is Braille the same in every language?
The cell and the core letter assignments travel widely, but each language standardizes its own accents, punctuation and contractions, and some scripts diverge substantially. English Braille itself has a unified standard (UEB) adopted across English-speaking countries precisely because earlier national variants drifted apart.
Can Braille represent capital letters and punctuation?
Yes, with the prefix strategy again: a capital sign (dot 6) before a letter capitalizes it, doubled for whole words, and punctuation uses the lower-cell patterns. The number sign from the alphabet section is the same idea; Braille spends cells on mode switches instead of new symbols.
Why does pasted Braille show as empty boxes on some devices?
Missing font coverage: the device has no glyphs for the U+2800 block, so it draws fallback boxes. The characters are intact, and copying the same text to a system with fuller fonts shows the dots; it is the same missing-glyph behavior any less-common script meets.
Does anyone still use Braille now that screen readers exist?
Emphatically: audio and Braille serve different needs, and literacy, spelling, math, music and code reading lean on Braille in ways speech cannot replace. Refreshable Braille displays, which raise pins under software control, are an active hardware category, and Unicode’s block is part of what keeps the script first-class in the digital world.