Six dots, 64 patterns and a Unicode block
Braille is a touch-based writing system where each cell of up to six raised dots stands for a letter, number or symbol. Louis Braille developed it in the 1820s, and the Unicode Braille Patterns block now lets you show those dot patterns as text on a screen.
Braille represents writing through tactile dot patterns. A six-dot cell has two columns of three positions: 1, 2, 3 down the left and 4, 5, 6 down the right when viewed from the reading side. These six positions allow 64 patterns, including a blank cell.
Unicode’s Braille Patterns block, U+2800 to U+28FF, encodes 256 eight-dot patterns. It contains the six-dot subset too. Unicode encodes the shape; the selected Braille code determines meaning. A pattern on a screen is not itself a tactile rendering.
The TextToolbox mapper is an isolated lowercase alphabet reference, not a complete uncontracted or contracted Braille transcriber. It accepts a to z, ordinary spaces and line breaks. Its dot explorer connects each letter cell to numbered positions.
Why a letter map is not Braille transcription
The lowercase alphabet cell for a uses dot 1; b uses dots 1 and 2; c uses dots 1 and 4. Capital and numeric indicators change how following cells are interpreted. A letter-only map cannot substitute for those rules.
For example, UEB uses ⠠⠁ for capital A and ⠼⠁ for the digit 1. The mapper does not emit or interpret these indicators; it rejects both sequences. Lowercase a maps to ⠁, which the mapper always decodes as a in its explicitly limited alphabet mode.
Uncontracted Braille still needs numeric, punctuation, capitalization and other context rules. Contracted Braille also represents words or groups of letters with contractions. A decoder cannot assume that every letter-shaped cell in an arbitrary document is a literal letter.
Braille can be read on raised-dot media or suitable refreshable tactile displays. Displayed Unicode glyphs are useful for inspecting patterns, but tactile dimensions, language-code correctness and assistive-technology behavior require a suitable reviewed workflow.
In the linked mapper, numbers and indicators are rejected. Uppercase letters are rejected by default; an explicit option maps them to lowercase while discarding the capitalization.
Letter cells, and two cases the mapper rejects
- Lowercase a: ⠁, dot 1; supported by the mapper
- Lowercase b: ⠃, dots 1 and 2; supported by the mapper
- Lowercase c: ⠉, dots 1 and 4; supported by the mapper
- Lowercase h: ⠓, dots 1, 2 and 5
- Lowercase n: ⠝, dots 1, 3, 4 and 5
- Lowercase q: ⠟, dots 1, 2, 3, 4 and 5
- Capital A: ⠠⠁; UEB illustration, unsupported by the mapper
- Digit 1: ⠼⠁; UEB illustration, unsupported by the mapper
Learning patterns, and when to use real transcription
- Compare isolated alphabet patterns with numbered dot positions.
- Inspect Unicode code points while keeping ordinary text alongside examples.
- Learn why a pattern’s meaning depends on its Braille context rather than assuming every cell is a letter.
- Use a reviewed language-specific transcription process for tactile labels and accessible documents.