A braille display is a hardware device with cells whose pins rise and fall to form braille characters, refreshing as the reader moves through a page. Nearly all of them are a single row. It is an input device as well as an output one. Most carry a braille keyboard, and each cell has a key above it that moves the cursor to that character, which is the braille equivalent of clicking. It takes its text from a screen reader, so anything that breaks the screen reader breaks braille in the same moment. On a single-line display, text is all that reaches the reader. No color, no layout, no image, and nothing that lives only in your CSS. Multi-line devices that raise tactile graphics as well now exist, and they are the exception rather than what your reader is likely to own.
In practice
Single-line displays run from 14 cells on a pocket unit to 80 on a desk, and 40 is the working default. That is one line at a time, with no color, no layout and no image, which is why structure carries so much weight here. Headings, lists and landmarks are how somebody moves around a page rather than reading every word of it in order. Programmers and people working long database records are the ones who need 70 or 80 cells, because a line of code does not fit in 40.
Reading braille makes spelling, spacing and formatting immediate in a way speech does not. A screen reader can spell a word out on request, so somebody listening can find out whether a field said receive or recieve, and they have to stop and ask. On a display it is simply there, which on a form that rejects an entry without saying why is the difference between noticing and hunting. It is also quiet, which matters in an office and matters more in a meeting.
It is not free and it does not come with the phone. Single-line displays were running about $3,500 to $15,000 in 2026 depending on how many cells they carry, and a multi-line tactile-graphics device sits above that range, which is the part of the assistive technology story that gets left out when people say most of it is free now. What is free is the software driving it, and the chain your markup has to survive is exactly the one a screen reader uses.
Why it matters
Braille is the reason a transcript and captions are not interchangeable. Captions are synchronized with the video and arrive at the video's pace, and one line of 40 cells is a narrow window to keep up through, so a person who is deafblind is far better served reaching your video as a document read at their own speed. W3C says the same thing in its own words, naming a descriptive transcript as what that reader needs. The uncomfortable part is what the standard makes you do about it. A descriptive transcript is one of two ways to meet the Level A description rule, and nothing at A or AA requires you to pick that one. So a site can conform at AA, the level nearly every law names, and still have chosen the route that leaves a deafblind reader with nothing.
Who reads this way
In WebAIM's screen reader survey, 38% of respondents with disabilities said they use braille output, up from 33.3% in 2017 and 27.7% in 2012. Among the ones using VoiceOver it runs at 54.2%. Those are self-selected respondents rather than a census, and the direction is the part worth holding on to. This is not a small group at the edge of your audience, and every one of them meets your page as text or not at all.
Where this shows up on the site
Related terms
- Screen readerA screen reader is software that reads the screen out loud, or sends it to a braille display, for people who cannot see it.
- Assistive technologyAssistive technology is hardware or software that gives a person with a disability more than a mainstream browser offers on its own.
- TranscriptA transcript is the text version of audio or video, and two different things go by that one word.
- Heading structureHeading structure is the h1 to h6 outline of a page, and for screen reader users it is the map.
Knowing the word is the easy part.
Find out where your own site stands. The free scan checks 10 pages in a real browser against all 90 supported automated rules, separates 27 best-practice checks from its WCAG findings, and names the rule behind every result.