> For the complete documentation index, see [llms.txt](https://qatesting.gitbook.io/qa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://qatesting.gitbook.io/qa/accessibility-testing/wcag-principles.md).

# WCAG Principles

### The Web Content Accessibility Guidelines Principles <a href="#t-1634613869088" id="t-1634613869088"></a>

<div data-full-width="true"><figure><img src="https://userpeek.com/wp-content/uploads/2021/10/WCAG-POUR-Principles.png" alt=""><figcaption></figcaption></figure></div>

There are 4 principles of WCAG 2.0, and to remember them quickly, you can think of this acronym, **POUR**.&#x20;

## The 4 principles are: <a href="#t-1634613869089" id="t-1634613869089"></a>

### Perceivable <a href="#t-1634613869090" id="t-1634613869090"></a>

This web principle is about processing web content by seeing, heating, or touching it. If there is one sense missing, the information should be perceivable through another sense.  &#x20;

<div data-full-width="true"><figure><img src="https://images.unsplash.com/photo-1530707114297-4af4b3cafe16?crop=entropy&#x26;cs=srgb&#x26;fm=jpg&#x26;ixid=M3wxOTcwMjR8MHwxfHNlYXJjaHw0fHxleWV8ZW58MHx8fHwxNjg5NjI3OTM5fDA&#x26;ixlib=rb-4.0.3&#x26;q=85" alt=""><figcaption></figcaption></figure></div>

### Operable <a href="#t-1634613869091" id="t-1634613869091"></a>

In general, web content must have the ability to operate with both a keyboard and a mouse. However, it also means the ability to operate and correct mistakes through voice or other alternative input devices like switches or a head-controlled mouse.

<div data-full-width="true"><figure><img src="https://images.unsplash.com/photo-1519810410960-332413a4e48f?crop=entropy&#x26;cs=srgb&#x26;fm=jpg&#x26;ixid=M3wxOTcwMjR8MHwxfHNlYXJjaHwyfHxjbGlja3xlbnwwfHx8fDE2ODk2Mjc5ODd8MA&#x26;ixlib=rb-4.0.3&#x26;q=85" alt=""><figcaption></figcaption></figure></div>

### Understandable <a href="#t-1634613869092" id="t-1634613869092"></a>

The principle understandable is where web content is presented in a consistent, predictable, readable form that reduces the chances of making errors and can be understood by different users.&#x20;

<div data-full-width="true"><figure><img src="https://images.unsplash.com/photo-1582213782179-e0d53f98f2ca?crop=entropy&#x26;cs=srgb&#x26;fm=jpg&#x26;ixid=M3wxOTcwMjR8MHwxfHNlYXJjaHwyfHxhZ3JlZW1lbnR8ZW58MHx8fHwxNjg5NjI4MDEzfDA&#x26;ixlib=rb-4.0.3&#x26;q=85" alt=""><figcaption></figcaption></figure></div>

### Robust <a href="#t-1634613869093" id="t-1634613869093"></a>

Robust is a web accessibility principle that adopts standards to function or be understood across a wide range of technologies. It should also allow to continue to function in the future as technologies change and evolve.

<div data-full-width="true"><figure><img src="https://images.unsplash.com/photo-1507146153580-69a1fe6d8aa1?crop=entropy&#x26;cs=srgb&#x26;fm=jpg&#x26;ixid=M3wxOTcwMjR8MHwxfHNlYXJjaHw1fHxyb2JvdHxlbnwwfHx8fDE2ODk2MjgwNDB8MA&#x26;ixlib=rb-4.0.3&#x26;q=85" alt=""><figcaption></figcaption></figure></div>

## What are the 3 levels?

<table data-full-width="true"><thead><tr><th width="151.66666666666669">Level of Conformance</th><th>Description</th><th>Example</th></tr></thead><tbody><tr><td>Level A</td><td>The bare minimum of accessibility.</td><td>Providing alternative text for images.</td></tr><tr><td>Level AA</td><td>Everything in Level A plus a few additional requirements.</td><td>Ensuring that content is navigable using only a keyboard.</td></tr><tr><td>Level AAA</td><td>Everything is in Level A and Level AA plus a few additional requirements.</td><td>Providing sign language interpretation for video content.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://qatesting.gitbook.io/qa/accessibility-testing/wcag-principles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.