Refreshable braille display
Also: braille terminal, braille display
A hardware device that converts on-screen text into refreshable braille on a row of pins, paired with a screen reader. The braille-first interface to digital content for braille-fluent blind users.
A refreshable braille display is a hardware device that renders text as tactile braille characters on a row of mechanically-actuated pins. Paired with a screen reader, it provides a braille-first interface to digital content — letting braille-fluent blind users read web pages, emails, documents, and code without relying on speech output.
How it works
The braille display sits in front of the user, typically a low, rectangular box with a row of 14, 20, 32, 40, or 80 braille cells (each cell is 8 pins arranged in two columns of 4). Each cell can raise its pins into any of 256 braille-character combinations.
The screen reader sends the currently-focused line of text to the display. The user reads with their fingers; when they reach the end of the line, they press a “next line” key on the display itself, and the next line of text rises into the pins.
Braille displays also include navigation keys — usually a chord of buttons resembling a braille keyboard — that let the user move through the document without taking hands off the display. Pairing this with a screen reader produces a tactile-only interface to most desktop and mobile operating systems.
The user population
Braille displays are used primarily by:
- Deafblind users — for whom speech output isn’t an option; braille is their primary interface to digital content.
- Braille-fluent blind users in noisy environments — open-plan offices, classrooms, public transport — where speech output is socially or practically untenable.
- Code-reading users — programmers and technical users who need to read code character-by-character (where speech output makes syntax characters difficult to parse).
- Multilingual or technical-content users — braille’s character-level output is more accurate than speech for code, mathematical notation, and non-Latin scripts.
Total braille-display users globally are estimated in the hundreds of thousands — a small population in absolute terms, but a population that depends on the technology for their entire digital life.
Software support
Major screen readers support braille displays out of the box:
- JAWS (Windows) has the most extensive braille-display support, recognising 100+ device models from multiple manufacturers.
- NVDA (Windows) supports a wide range of devices via plugins and built-in drivers.
- VoiceOver (macOS / iOS) has native support for common braille displays via Bluetooth.
- TalkBack (Android) supports Bluetooth-paired braille displays.
What this means for web developers
Almost nothing changes from screen-reader testing. A web page that works well in a screen reader works well on a braille display, because the screen reader is the intermediary — it sends text to the display in the same form it would speak it. The exceptions:
- Long unfractured strings of text can scroll across multiple braille-line refreshes. Keep paragraphs structured; don’t ship monolithic single-line text blocks.
- Heavy visual punctuation (emojis, decorative characters, ASCII art) reads literally on a braille display, character by character. Audit decorative content for braille-readability.
- Live regions and notifications flash across the braille display too, with timing. The same “polite vs assertive” tradeoffs apply.
If your site passes a screen-reader audit, it almost always passes braille-display testing as well. The discipline is the same; the output device is different.