How accessible is your website?Start free check

POUR Principles: The Four Pillars of WCAG

Also called: Four principles of accessibility, Perceivable Operable Understandable Robust, WCAG principles

Definition

The POUR principles are the four principles at the top of WCAG: content must be perceivable, operable, understandable and robust. Every WCAG guideline and success criterion sits under one of them.

The POUR principles are the four ideas behind every rule in WCAG: content must be Perceivable, Operable, Understandable and Robust. The acronym is not in the standard itself, but it is the common way to remember the structure. If a site fails any one of the four, some people cannot use it at all.

What it means

The W3C Introduction to Understanding WCAG 2.2 describes the four principles as the foundation of web accessibility and states: "If any of these are not true, users with disabilities will not be able to use the web." Below the principles sit 13 guidelines, and below those the testable success criteria with their conformance levels.

Principle W3C definition Guidelines in WCAG 2.2
Perceivable Information and user interface components must be presentable to users in ways they can perceive. 1.1 Text Alternatives, 1.2 Time-based Media, 1.3 Adaptable, 1.4 Distinguishable
Operable User interface components and navigation must be operable. 2.1 Keyboard Accessible, 2.2 Enough Time, 2.3 Seizures and Physical Reactions, 2.4 Navigable, 2.5 Input Modalities
Understandable Information and the operation of user interface must be understandable. 3.1 Readable, 3.2 Predictable, 3.3 Input Assistance
Robust Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. 4.1 Compatible

The first digit of every success criterion tells you its principle: 1.4.3 Contrast (Minimum) is a perceivable rule, 2.1.1 Keyboard an operable one.

Examples

Each principle shows up in everyday markup. A single "add to cart" button can fail all four:

Example
<!-- P: icon only, no text alternative
     O: div is not reachable by keyboard
     U: no hint what happens
     R: no role, so assistive technology does not know it is a button -->
<div class="cart-btn" onclick="addToCart(42)">
  <img src="cart.svg">
</div>

<!-- Meets all four -->
<button type="button" onclick="addToCart(42)">
  <img src="cart.svg" alt="">
  Add to cart
</button>

The native button gives perceivable text, keyboard navigation, a clear label and the right role for the accessible name computation.

Do

Use native HTML elements, give every image and control a text alternative or name, and write labels and error messages in plain language.

Don't

Treat POUR as four separate projects, or fix only what is visible – robustness and understandable text matter as much as contrast.

How to test the POUR principles on a page

  1. Perceivable – check alt text, captions and text contrast; zoom to 200 % and 400 %.
  2. Operable – put the mouse away and use Tab, Shift+Tab, Enter and Space; look for a visible focus and no traps.
  3. Understandable – read labels, instructions and error messages; is the page language set and the navigation consistent?
  4. Robust – inspect the Accessibility panel in DevTools and listen with VoiceOver or NVDA: does every control have a name, role and state?

Questions

What does POUR stand for in accessibility?

Perceivable, Operable, Understandable and Robust – the four principles of WCAG. Every guideline and success criterion belongs to one of them.

Are the POUR principles a legal requirement?

Not on their own. Laws reference WCAG success criteria at a level such as AA; the principles organize those criteria but are not tested directly.

What is the difference between principles, guidelines and success criteria?

Principles are the four top-level goals, guidelines (13 in WCAG 2.2) describe what to work toward under each, and success criteria are the testable statements with a level of A, AA or AAA. Only success criteria are used to decide conformance.

How many guidelines belong to each POUR principle?

In WCAG 2.2: four under perceivable, five under operable, three under understandable and one under robust – 13 guidelines in total.

How can I check my site against all four principles?

Combine an automated check with a short manual keyboard and screen reader test. The free WCAG scanner covers the automatically testable criteria of all four principles.

  • WCAG: The Web Content Accessibility Guidelines

    WCAG (Web Content Accessibility Guidelines) is the technical standard of the W3C that describes how to make websites and other web content accessible to people with disabilities. It is organized into four principles, 13 guidelines and testable success criteria at levels A, AA and AAA.

    Read definition: WCAG: The Web Content Accessibility Guidelines
  • WCAG Conformance Levels: A, AA and AAA Explained

    WCAG conformance levels are the three tiers – A, AA and AAA – at which a web page can meet WCAG. Each level includes every success criterion of the levels below it, and conformance always applies to full pages and complete processes.

    Read definition: WCAG Conformance Levels: A, AA and AAA Explained
  • Screen Reader: How It Reads Websites and What It Needs

    A screen reader is assistive software that reads the content and controls of a screen aloud or outputs them on a braille display. It relies on the names, roles and states that a website exposes through the browser's accessibility tree.

    Read definition: Screen Reader: How It Reads Websites and What It Needs
  • Keyboard Navigation: WCAG 2.1.1 Explained

    Keyboard navigation means that every function of a website can be reached and operated with a keyboard alone – usually with Tab, Shift+Tab, Enter, Space and the arrow keys. WCAG 2.1.1 requires it at Level A.

    Read definition: Keyboard Navigation: WCAG 2.1.1 Explained

Let AI Handle Website Accessibility

Built in Europe. Set up in 2 minutes, no developer needed. Put website accessibility on autopilot with AI-powered fixes and automated monitoring.

  1. 1Choose your plan
  2. 2Install in 2 min
  3. 3AI fixes your website
  4. Done