Skip to main content

WCAG Documents

WCAG is short for Web Content Accessibility Guidelines. These guidelines explain how to make web content more accessible to people with various abilities and disabilities. People involved in web development should know and follow these guidelines. They are especially important for designers, developers, content creators, and people who test websites. Following these guidelines makes sure websites meet the minimum accessibility standards.

We encourage you to visit the official WCAG overview to learn more.

Our simplified WCAG documents explain the information from the official guidelines more briefly. Learn the essential information to get a basic understanding of the guidelines.

WCAG documents are a supportive study material of the web accessibility topic.

note

WCAG Documents are not trying to re-create WCAG, nor to improve it. The project aims to introduce WCAG for people who want to get the basic knowledge first and then study it in detail at the official guidelines. We also want to help those who are better auditory and visual learners to learn from videos.

There are also videos to explain the guidelines. We are working on creating more content and videos, so stay tuned for updates.

Check the following video that gives you an introduction to the project.

Web Content Accessibility Guidelines​

WCAG includes four main principles that explain what web content should be:

  1. Perceivable
  2. Operable
  3. Understandable
  4. Robust

Each principle is then divided into different guidelines. The purpose of guidelines is to group and understand the success criteria.

Success criteria are what determine conformance to WCAG. This means that to meet WCAG, the content needs to meet the success criteria. They describe how to make the web content more accessible.

The success criteria have three levels of conformance to meet. Each with increasing difficulty: Level A, level AA, and level AAA.

Level A criteria are essential for all websites. If a website does not meet level A standards, it may have serious accessibility issues. These issues make it difficult or impossible for users with disabilities to use the website.

Level AA criteria are recommended as a minimum to meet. Websites that meet the level AA are accessible to a wider range of users.

Level AAA criteria represent the highest WCAG conformance level. Not all websites may be able to achieve these standards because they would often need a lot of resources to meet them. But some of them can be affordable even for regular websites.

1 - Perceivable​

Information and user interface components must be presentable to users in ways they can perceive.

1.1 - Text Alternatives​

Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols, or simpler language.

1.2 - Time-based Media​

Provide alternatives for time-based media.

1.3 - Adaptable​

Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

1.4 - Distinguishable​

Make it easier for users to see and hear content including separating foreground from background.

2 - Operable​

User interface components and navigation must be operable.

2.1 - Keyboard Accessible​

Make all functionality available from a keyboard.

  • 2.1.1 - Keyboard (future link)
  • 2.1.2 - No Keyboard Trap (future link)
  • 2.1.3 - Keyboard (No Exception) (future link)
  • 2.1.4 - Character Key Shortcuts (future link)

2.2 - Enough Time​

Provide users enough time to read and use content.

  • 2.2.1 - Timing Adjustable (future link)
  • 2.2.2 - Pause, Stop, Hide (future link)
  • 2.2.3 - No Timing (future link)
  • 2.2.4 - Interruptions (future link)
  • 2.2.5 - Re-authenticating (future link)
  • 2.2.6 - Timeouts (future link)

2.3 - Seizures and Physical Reactions​

Do not design content in a way that is known to cause seizures or physical reactions.

  • 2.3.1 - Three Flashes or Below Threshold (future link)
  • 2.3.2 - Three Flashes (future link)
  • 2.3.3 - Animation from Interactions (future link)

2.4 - Navigable​

Provide ways to help users navigate, find content, and determine where they are.

  • 2.4.1 - Bypass Blocks (future link)
  • 2.4.2 - Page Titled (future link)
  • 2.4.3 - Focus Order (future link)
  • 2.4.4 - Link Purpose (In Context) (future link)
  • 2.4.5 - Multiple Ways (future link)
  • 2.4.6 - Headings and Labels (future link)
  • 2.4.7 - Focus Visible (future link)
  • 2.4.8 - Location (future link)
  • 2.4.9 - Link Purpose (Link Only) (future link)
  • 2.4.10 - Section Headings (future link)

2.5 - Input Modalities​

Make it easier for users to operate functionality through various inputs beyond keyboard.

  • 2.5.1 - Pointer Gestures (future link)
  • 2.5.2 - Pointer Cancellation (future link)
  • 2.5.3 - Label in Name (future link)
  • 2.5.4 - Motion Actuation (future link)
  • 2.5.5 - Target Size (future link)
  • 2.5.6 - Concurrent Input Mechanisms (future link)

3 - Understandable​

Information and the operation of the user interface must be understandable.

3.1 - Readable​

Make text content readable and understandable.

  • 3.1.1 - Language of Page (future link)
  • 3.1.2 - Language of Parts (future link)
  • 3.1.3 - Unusual Words (future link)
  • 3.1.4 - Abbreviations (future link)
  • 3.1.5 - Reading Level (future link)
  • 3.1.6 - Pronunciation (future link)

3.2 - Predictable​

Make Web pages appear and operate in predictable ways.

  • 3.2.1 - On Focus (future link)
  • 3.2.2 - On Input (future link)
  • 3.2.3 - Consistent Navigation (future link)
  • 3.2.4 - Consistent Identification (future link)
  • 3.2.5 - Change on Request (future link)

3.3 - Input Assistance​

Help users avoid and correct mistakes.

  • 3.3.1 - Error Identification (future link)
  • 3.3.2 - Labels or Instructions (future link)
  • 3.3.3 - Error Suggestion (future link)
  • 3.3.4 - Error Prevention (Legal, Financial, Data) (future link)
  • 3.3.5 - Help (future link)
  • 3.3.6 - Error Prevention (All) (future link)

4 - Robust​

Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.

4.1 - Compatible​

Maximize compatibility with current and future user agents, including assistive technologies.

  • 4.1.1 - Parsing (future link)
  • 4.1.2 - Name, Role, Value (future link)
  • 4.1.3 - Status Messages (future link)