# Blindness: How Blind People Use the Web

Source: https://allyway.ai/glossary/blindness

Blindness is a substantial, uncorrectable loss of vision in both eyes. Blind people use websites without seeing them, through a screen reader that reads content aloud or shows it on a refreshable braille display, and they navigate with the keyboard or touch gestures.

Blindness changes how a person uses the web completely: instead of looking at a page, a blind person listens to it or reads it with their fingers on a [braille display](https://allyway.ai/glossary/braille-display). Everything that only exists visually – an unlabeled icon, a photo without a description, a chart, a button that works only with the mouse – is simply not there for them.

## What it means

W3C's page on [visual disabilities](https://www.w3.org/WAI/people-use-web/abilities-barriers/visual/) describes blindness as a "substantial, uncorrectable loss of vision in both eyes". The W3C Low Vision Task Force quotes WHO estimates of 39 million blind people worldwide. Far more people have [low vision](https://allyway.ai/glossary/low-vision) and still read with their eyes; blind users rely on assistive technology instead.

The central tool is the [screen reader](https://allyway.ai/glossary/screen-reader). In W3C's words, these tools "can read the information on the screen out loud, or they can present it in Braille." Blind users move through a page by headings, links, form fields and landmarks, usually with the keyboard on a computer and with swipe gestures on a phone. That only works when the page exposes its structure in the code.

W3C lists the barriers people with visual disabilities face. These hit blind users hardest:

| Barrier | WCAG criterion | Level |
|---|---|---|
| Images and controls without a text alternative | 1.1.1 Non-text Content, see [alt text](https://allyway.ai/glossary/alt-text) | A |
| Videos without an audio alternative or [audio description](https://allyway.ai/glossary/audio-description) | 1.2.3 / 1.2.5 | A / AA |
| Missing page structure, headings and navigational aids | 1.3.1 Info and Relationships | A |
| Functions that don't work without a mouse | 2.1.1 Keyboard, see [keyboard navigation](https://allyway.ai/glossary/keyboard-navigation) | A |
| Buttons and links without a clear name | 4.1.2 Name, Role, Value | A |
| Inconsistent, unpredictable navigation | 3.2.3 Consistent Navigation | AA |

> **Note:** > **Deafblind people use braille**
> People who are both deaf and blind can't rely on speech output. They read the screen reader's output on a refreshable braille display – one more reason why every piece of information must exist as real text, including captions and transcripts for audio.

## Examples

```html title="Example"
<!-- Inaccessible: an icon without a name, a clickable div, a heading that is only big text -->
<div class="big-text">Our services</div>
<div onclick="openCart()"><svg>…</svg></div>
<img src="team.jpg">

<!-- Accessible: real heading, real button with a name, image with alt text -->
<h2>Our services</h2>
<button type="button" aria-label="Open cart">
  <svg aria-hidden="true" focusable="false">…</svg>
</button>
<img src="team.jpg" alt="Our five team members in front of the office">
```

A screen reader announces the second version as "Our services, heading level 2", "Open cart, button" and "Our five team members in front of the office, image". The first version gives a blind user plain text, nothing at all and a file name.

**Do:** Do

Use real headings and [ARIA landmarks](https://allyway.ai/glossary/aria-landmarks), give every image, icon and form field an [accessible name](https://allyway.ai/glossary/accessible-name), make everything work with the keyboard, describe charts and videos in text and keep a logical reading order.

**Don't:** Don't

Build buttons from plain `div` elements, use images of text, write instructions like "click the red button on the right", hide content in canvas graphics or put important information only in pictures or color.

## How to check your site for blind users



## Questions

Q: How do blind people use websites?
A: With a screen reader that reads the page aloud or sends it to a braille display. They navigate by headings, links, landmarks and form fields, using the keyboard on a computer or swipe gestures on a phone.

Q: What is the difference between blindness and low vision?
A: People who are blind use the web mainly through speech or braille. People with low vision still have usable sight and read with their eyes, often with zoom, a magnifier or high contrast.

Q: What do blind users need most on a website?
A: Text alternatives for images, a clear heading structure, full keyboard access, clear names for links and buttons, and form fields with labels.

Q: Which WCAG level matters most for blind users?
A: Most of the criteria that matter for blind users are Level A, the minimum: text alternatives, keyboard access, structure and names. Level AA adds, among other things, audio description for video and consistent navigation.

Q: How can I quickly find barriers for blind users on my site?
A: Start with an automated check: the free [WCAG scanner](https://allyway.ai/free-wcag-accessibility-scanner-for-websites) lists missing alt text, unnamed buttons and missing labels on your homepage. Then test the key tasks yourself with a screen reader.
