On this page

Web Accessibility

What is web accessibility?#

Web accessibility is the practice of building websites and applications that people with different abilities and ways of interacting can use.

It is not a theme, a compliance slogan, or a screen-reader-only concern. It is an engineering requirement on meaning, structure, and interaction.

Fundamentals

Receive the information.

  • Text can be read
  • Images can have alternatives
  • Video can have captions

Who experiences barriers?#

Barriers show up when an interface requires abilities or input methods someone does not have—or cannot use in the moment.

Access needs

  • Screen reader
  • Magnification
  • Contrast

Duration

Lifelong blindness, deafness, or limited mobility

Accessibility barriers can affect people permanently, temporarily, or situationally.

Continue in Accessibility in Practice.

How does the web reach different users?#

Appearance is not enough. Assistive technologies and alternative input methods consume the semantics browsers expose from your markup and behavior.

Select each layer.

Accessibility stack

Authors define structure, meaning, and behavior in markup and script.

Native elements already carry roles and interaction contracts.

<button type="button">Save</button>

A conceptual model—not a claim that every browser implements an identical pipeline.

Why implementation choices matter#

The same visual control can expose very different semantics.

BadLooks like a control

<div onclick="save()">Save</div>

GoodIs a control

<button type="button" onclick="save()">Save</button>
The button provides role, focusability, and Enter/Space activation. The div does not—unless you rebuild that contract yourself.