Skip to content
Tutorials Center
My learning

Topics

Lesson 5 of 38 ยท Principles and WCAG

The POUR Principles

Learn the four WCAG principles, Perceivable, Operable, Understandable and Robust, with practical examples of what each one means for the pages you build.

The Web Content Accessibility Guidelines (WCAG) rest on four principles, remembered by the acronym POUR: content must be Perceivable, Operable, Understandable and Robust. Every WCAG rule, and there are dozens, belongs under one of these four ideas. If you understand POUR, you can reason about a situation the checklist never mentioned.

Think of a coffee machine in a public place. People must be able to see the buttons or hear the beeps (perceive), reach and press them (operate), understand what each does and what went wrong (understand), and the machine must keep working with different cups and users (robust). Web pages are no different.

Perceivable

Users must be able to perceive the information through at least one of their senses. Nothing can be invisible to every sense a person has.

Typical techniques:

  • Text alternatives for images, charts and icons.
  • Captions, transcripts and audio descriptions for media.
  • Content that adapts: a structure that can be presented in different ways, such as a screen reader order or a zoomed single column.
  • Enough contrast, resizable text, and no colour-only meaning.

Operable

Users must be able to operate the interface. Controls and navigation cannot require an interaction a person cannot perform.

  • Everything works with a keyboard.
  • Enough time to read and act, with ways to pause or extend limits.
  • No content that flashes dangerously.
  • Ways to find content: page titles, skip links, focus order, descriptive links.
  • Alternatives to complex gestures such as dragging or multi-finger swipes, and big enough targets.

Understandable

Users must be able to understand both the content and how the interface works.

  • Readable text, with the page language identified.
  • Predictable behavior: navigation stays in the same place, and a change of setting does not suddenly change context.
  • Help with input: clear labels, instructions, error messages that say what is wrong and how to fix it.

Robust

Content must be robust enough to work with current and future user agents, including assistive technology.

  • Valid, well-formed markup with unique IDs.
  • Correct names, roles and values for custom controls.
  • Status messages that AT can announce without moving focus.

POUR at a glance

Perceivable Can users sense it?
Operable Can users use it?
Understandable Does it make sense?
Robust Does it work with AT?
1 / 2

Sorting problems into principles

A useful habit is to classify every barrier you find. This helps you describe it in an audit and decide how to fix it. Try it with this interactive sorter.

Which principle does this break?

Some barriers can be argued either way, such as vague errors, which may also hurt operability. That is fine: WCAG success criteria sit under one principle, but real problems often touch several.

POUR beyond the checklist

POUR also helps when you design. Before shipping a feature, ask four questions: Can everyone perceive the output? Can everyone operate the input? Will they understand what happened? Will it keep working with their tools?

A feature through the POUR lens

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does POUR stand for?

    These are the four WCAG principles that every success criterion falls under.
  2. 2. A dropdown menu that opens only on mouse hover most directly violates which principle?

    Keyboard and touch users cannot trigger hover, so they cannot operate the control.
  3. 3. Which is an Understandable technique?

    Identifying the language, giving clear labels and helpful errors make content and behavior easier to understand.
  4. 4. Why does the Robust principle matter?

    Correct roles, names and values let assistive technology interpret the page reliably.

Summary

  • POUR stands for Perceivable, Operable, Understandable and Robust.
  • Each WCAG success criterion belongs to one of these four principles.
  • Use POUR to classify problems and to review new features before release.
  • Real barriers often touch more than one principle.

Next: WCAG Versions and Conformance Levels