Skip to content
IRC-CodingIRC-Coding
WCAGAccessibilityPOURContrastKeyboard NavigationScreen Reader

WCAG Explained: POUR, Levels A/AA/AAA & Accessibility

WCAG guidelines explained: POUR principles, conformance levels, contrast ratios, keyboard navigation, focus management and testing methods.

S

schutzgeist

1 min read
WCAG Explained: POUR, Levels A/AA/AAA & Accessibility

WCAG (Web Content Accessibility Guidelines)

This post is a glossary entry for WCAG, including exam questions, core components, and key terms.

In a Nutshell

WCAG defines testable success criteria for accessibility across four principles:

  • perceivable
  • operable
  • understandable
  • robust

The typical target standard in projects is WCAG AA.

Concise Technical Overview

WCAG (from the W3C) has three conformance levels:

  • A (minimum)
  • AA (practical standard)
  • AAA (enhanced, not always realistic)

The four principles together form the acronym POUR.

Common success criteria include:

  • contrast (AA typically requires 4.5:1 for body text)
  • keyboard operability
  • visible focus indicators
  • clear labels and error messages

Implementation approach:

  • semantic HTML before ARIA
  • logical tab order
  • focus management
  • understandable error handling

Verification: automated scanning plus manual review plus keyboard and screen reader testing.

Exam-Relevant Checklist

  • Explain POUR
  • Distinguish between levels A/AA/AAA
  • State contrast ratios
  • Keyboard navigation and visible focus
  • Testing methods: scanners, manual testing, assistive technology
  • Documentation: checklists, test reports, style guides
  • Connection to EN 301 549 (EU standard)

Core Components

  1. Principles and success criteria
  2. Target level (AA) and scope
  3. Semantic markup and structure
  4. Keyboard operability
  5. Contrast and perceivability
  6. Labels, names, and roles
  7. Error prevention and messaging
  8. Media alternatives
  9. Robust code and correct ARIA usage
  10. QA process and test documentation

Practical Example (Form)

- visible labels with programmatic association
- tab order is linear; focus indicators are visible
- error list links to fields; messages appear near fields
- contrast at least 4.5:1 for text
- accessibility checklist and test report in repository

Typical Exam Questions (with Brief Answers)

  1. What does POUR stand for? Perceivable, Operable, Understandable, Robust.
  2. What is the AA contrast ratio for body text? At least 4.5:1.
  3. How do you test efficiently? Automated scanning plus manual review plus keyboard and screen reader testing.

Key Resources

  1. https://www.w3.org/WAI/standards-guidelines/wcag/
  2. https://www.w3.org/WAI/WCAG22/quickref/
Back to Blog
Share:

Nächster Artikel in Software Ergonomics

Weiterlesen
Expectancy Conformity (ISO 9241-110) Explained

Related Posts