Skip to main content
Accessibility.com, LLC
Category: Assistive Technologies

Refreshable Braille Display

Also known as: RBD, Braille Display, Braille Terminal
Simply put

A refreshable Braille display is an electronic device that converts text shown on a computer or other device into readable Braille. It uses small pins that rise and fall to form Braille characters, and it updates continuously as the user moves through the text on screen. This allows people who are blind or have low vision to read digital content by touch.

Formal definition

A refreshable Braille display is an electro-mechanical assistive technology device that renders on-screen text as tactile Braille characters, typically using arrays of round-tipped pins that raise and lower to represent Braille cells. It connects to a host device such as a computer and refreshes dynamically, updating the displayed characters as the user navigates the cursor across the content. Displays commonly present a limited number of characters per line (for example, up to 80 characters), and stand-alone models are also available. Refreshable Braille displays generally operate in conjunction with a screen reader to interpret and route content to the device.

Why it matters

Refreshable Braille displays provide a direct, tactile means of accessing digital content for people who are blind or have low vision, particularly those who read Braille. Unlike audio output from a screen reader alone, a Braille display allows users to read text by touch, which supports precise reading of spelling, punctuation, formatting, code, and mathematical or technical notation that can be difficult to interpret through speech. For deafblind users in particular, a refreshable Braille display may be the primary or only practical way to access on-screen information.

Because these devices generally work in conjunction with a screen reader that interprets and routes content to the display, the accessibility of digital content depends heavily on how well that content is structured and coded. Poorly marked-up interfaces, images without text alternatives, or content that is not exposed to assistive technology can leave Braille display users unable to read information that is visually available to others. Supporting Braille output is therefore an important consideration when evaluating whether digital content is usable by the full range of assistive technology users, and testing with a screen reader and Braille display can surface issues that automated checks alone do not detect.

The presence of Braille display users among an audience reinforces why manual and assistive technology testing matters. Meeting technical guidelines or passing automated tests does not guarantee that content reads correctly in Braille, so organizations aiming for accessible experiences generally include Braille-based reading among the scenarios they consider.

Who it's relevant to

Blind and low-vision users
People who read Braille rely on refreshable Braille displays to access digital text by touch, allowing precise reading of spelling, punctuation, and formatting that may be harder to follow through speech alone. Deafblind users may depend on a Braille display as their primary means of accessing on-screen content.
Accessibility engineers and QA testers
Because Braille output depends on content being correctly exposed to a screen reader, testing with both a screen reader and a refreshable Braille display can reveal issues that automated tools do not catch. Including Braille-based reading in manual test plans helps confirm that content is usable by this group.
UX designers and content creators
Well-structured markup, meaningful text alternatives, and logical reading order directly affect how content reads on a Braille display. Designers and authors who account for tactile reading help ensure their content is legible to Braille users, not only to those using audio output.
Compliance officers and accessibility leaders
Supporting refreshable Braille displays is part of ensuring digital content works across the range of assistive technologies. This entry is general information and not legal advice; requirements depend on the applicable authority and evolve through regulation and case law, so consult qualified legal counsel for jurisdiction-specific obligations.

Inside RBD

Braille Cells
A row of cells, each typically containing six or eight pins that raise and lower to form braille characters. The pins are electromechanically actuated so the display can refresh dynamically as content changes.
Refreshable Pins
The movable dots within each cell that rise and fall to represent characters, distinguishing this device from static, embossed braille on paper.
Screen Reader Integration
The display works in tandem with screen reader software, which translates on-screen digital text into braille output and sends it to the device.
Cursor Routing and Navigation Controls
Buttons or keys that let the user move through text, position the cursor, and navigate content, often supplemented by scrolling controls to advance through lines.
Connectivity Interface
A wired (USB) or wireless (Bluetooth) connection linking the display to a computer, tablet, or smartphone running compatible assistive software.

Common questions

Answers to the questions practitioners most commonly ask about RBD.

Does a refreshable braille display read a screen on its own, like a screen reader does?
No. A refreshable braille display is an output device that renders text in braille cells but does not, by itself, interpret or navigate on-screen content. It generally works in tandem with a screen reader, which determines what content is exposed and passes that text to the braille display. The display presents the information; the screen reader does the interpretation and navigation.
Is a braille display only useful for people who are completely blind?
Not necessarily. While refreshable braille displays are commonly associated with blind users, they can also serve people who are deafblind, for whom braille may be a primary means of accessing digital content when audio output is not usable. Usage depends on the individual's needs and braille literacy rather than on a single category of disability, so it is best not to assume a fixed user profile.
How does a refreshable braille display connect to a computer or mobile device?
Refreshable braille displays commonly connect through USB or Bluetooth, and some models support both. The specific connection options and setup steps vary by device and by the operating system and screen reader in use, so the manufacturer's documentation and the screen reader's supported-device list are the appropriate references for a given configuration.
What should developers keep in mind so content works well with braille displays?
Because a braille display renders whatever the screen reader exposes, the same practices that support screen reader access generally benefit braille users: providing meaningful text alternatives, using semantic structure and correct programmatic roles, labeling controls and form fields, and ensuring content is presented in a logical reading order. Since braille conveys information linearly and without audio cues, clear text and accurate structure are especially important.
Can meeting WCAG success criteria guarantee a good experience on a braille display?
Meeting applicable WCAG success criteria supports accessibility but does not by itself guarantee a usable experience on a refreshable braille display. Conformance is not the same as usability, and automated testing detects only a portion of potential issues. Testing with a screen reader in combination with a braille display, ideally involving braille-reading users, is generally recommended to confirm the content is understandable in that context.
How should braille displays be included in accessibility testing?
Testing with a braille display is typically done alongside screen reader testing, since the two work together. Because behavior can vary across screen readers, operating systems, and braille display models, testing across representative combinations helps surface issues. Manual and assistive-technology testing are needed to complement automated checks, and involving people who use braille regularly can reveal problems that automated tools and non-braille testers may miss.

Common misconceptions

A refreshable braille display shows an entire screen or page of content at once.
Most displays present a single line at a time, and the user scrolls through the content. The number of cells varies by device, which limits how much text is visible at any moment.
Providing screen reader and braille compatibility guarantees WCAG conformance or legal compliance.
Supporting assistive technology such as braille displays is important, but conformance depends on how content is structured and coded. Automated checks detect only a portion of issues, and manual testing with assistive technology is generally needed. Compatibility alone does not ensure conformance or immunity from legal claims.
Braille displays are outdated because text-to-speech exists.
Braille displays serve users who read braille, including people who are deafblind for whom audio output is not usable, and they support tasks like precise reading, spelling, and code review where tactile access is valuable. They complement rather than replace speech output.

Best practices

Ensure digital content is coded with correct semantic structure (headings, lists, tables, and labels) so screen readers can convey accurate information to the braille display.
Provide meaningful text alternatives for non-text content, since a braille display can only render information that is available as text.
Test with an actual screen reader and, where feasible, a refreshable braille display rather than relying solely on automated tools, which capture only part of the potential issues.
Maintain a logical reading and focus order so that content presented line-by-line on the display flows in a sensible sequence.
Verify that interactive controls expose their name, role, and state so braille users can understand and operate them.
Consult qualified accessibility and legal professionals for guidance specific to your obligations, recognizing that requirements evolve through regulation and case law and that this guidance is not legal advice.